LexEVS Meeting Minutes - 2014.12.17

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Scott to work with Gilberto to determine what is needed for OWL 2 requirements

on hold

done

on hold

on hold

open

Gilberto to follow up with NCI security team about the use of NodeJS.

done

done

done

open

Scott: 

OWL2

• Progress made with Gilberto and others.
• Scott has made changes and pushed out those changes for review.
• Need to decide what we are going to include in 6.3 and what will go back to the backlog.
• Meeting scheduled for Wednesday PM to continue this discussion.
• Kim needs to test the namespace fix. 

Planned Lucene discussion on Friday with Kevin.

Cory:  API Documentation, Informatics update

• Installed ioDocs locally on node js.
• Looked at other tools - one possible solution if we cannot use nodejs.
• Discussing the API service with Gilberto.
• Informatics upgrade going to happen on Friday, Dec 19.

Craig: Project Plan for 6.3 and 6.4. 

• Need to get closure on the OWL 2 JIRA items.
• Once all JIRA items identified, can then identify when 6.3 development will be complete.

• Has been previously discussed with Kevin
• Suggested that there would need to be more indicators provided throughout the process
• This could prove to be an fairly involved activity (~ 1 week or more)
• Given the recent enhanced performance, this becomes less of an issue.
• Lower priority, but would like to consider as part of 6.3.

Possible hosting options - host on NCI or on external system (informatics).

One suggestion was to have service on NCI and then point to another server with the content. Only concern would be the cross-site scripting (and associated filters).

Plan - deploy Node js service on NCI and have it appscan'ed. Once confirmed, then we can then move onto providing the content on another server, etc.

Approaching the final steps in deployment. Once data and FW exceptions in place, then start with the browsers. Need to see how 6.2 will run on Shady Grove. Once verified, announce available for testing. Once confirmed, then point to the 6.2 services. Anticipated late December/early January. Once complete, will no longer need to update 6.1 data.

Team will need to update release notes, artifacts. (~ mid-late January).

Public announcement in mid-late January.

Needs to be reflected in the 6.3 project plan. TODO

It was discussed that 6.3 could be deployed over 6.2 deployment. Only concern is column widths.