Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Current Sprint - Sprint 16 (October 29, 2015 – November 11, 2015)

LexEVS 6.4 S13-500 Agile Development - Sprint StatusStatus#SprintStatus-Sprint16

We reviewed the backlog and discussed how to enter exit criteria for a story/bug.  This will help everyone understand when issues can be considered done.

We also mentioned that we will be grooming the backlog weekly, moving stories to the top based on priority.

Issue Prioritization

Recent LexEVS Related Bugs and Features (within last week)

Recent CTS2 Service Related Issues (within last week)

LEXEVS-1296 - lbGUI cleanup script fails when no metadata is present. 

We should consider working on this issue in the next sprint as well as add exit criteria to the issue.

Issue Grooming

Prioritize JIRA issues (fix version 6.4)

Sprint Deliverables - Updates

• 6.3.x
• Lucene

Review decision regarding the single jar vs. a zip file

Re: Consideration of Build Impacts

We all agreed upon the proposed solution in the above link.

TODO: Mayo to create a JIRA item to capture the solution issue

The build is currently broke.  The artifact built does not run due to the new lucene jars and their manifest files. 

The dev team will need to consider if we need to change the process to create a zip file, rather than a jar.

The dev team is suggesting breaking the build up into multiple jars.

This new multiple jar approach would break current users of the single jar.  Users would need to update their classpath.

TODO: Add two groups to work with on the NCI team to the Face to Face agenda.  How will this affect NCI users?

TODO: Mayo dev team to come up with a proposal on how to migrate to the new jar structure.

VPN and network evaluation

Craig is still waiting to hear back from the Mayo/NCI IT.

TODO: Craig will follow up with IT to get an update.

was able to re-start this discussion between NCI and Mayo IT.  Both sides of IT are exchanging information to continue the discussion.

It was also mentioned that eventually, Mayo will need access to the NCI continuous server

.

There is a wiki link for agenda topics: LexEVS 6.3 and 6.4 Technical Face-To-Face Meetings

TODO:   NCI team to add additional information to the topics for the Mayo will add the following Face to Face meetings.

Search queries - accessing the database opposed to the Lucene index only

• Update

LEXEVS- 970

• OWL2 Issue breakdown update

Scott was able to load the thesaurus locally without any errors.

TODO: Scott to work with Gilberto and review a load with restrictions.

Gilberto noted the following:

• He is not seeing any relationships for biotin (code CHEBI_15956) on his load.
• Role Relationships not displayed for code (OBI_0100061)
• has associated axiom (fol) (IAO_00100000) (the declaration of the property) -
  
  • Do we have this data in LexEVS db? 
  • Once we have this in the DB, can the TERM browser render this properly?
• information content entity - has curation status
• entity - editor note: annotation on annotation name is not rendered

The Mayo team will be out next Wednesday.

The NCI will cancel the meeting.

The Mayo team will end the existing sprint and start the next one

We are re-implementing how we are restricting coded nodes.

We are are seeing some differences in sorting when doing multi coding scheme index searches.

If you do a union query across multiple code systems.  Each code system has it's own index.  Scoring is done on a each index.  This is causing a junit ordering test to fail.

We will need to see how this works with real data.

topics to our list:

• Continuous server discussion
  
  • How Mayo implemented their CI server and what NCI's plan is for their own server.
• Add browser/LexEVS performance to the list of topics.
• Loaders - how to create one from scratch.  Create a simple example of a loader.
• End user approach to LexEVS
  
  • Tutorial on how to query the LexEVS API
  • Review of existing LexEVS documentation.
• REST - CTS2 REST vs additional (extensions) REST calls like bulk download.
  
  • Discuss a REST Framework that includes CTS2 and other calls (extensions).

We requested NCI to fill in any addition notes/priorities on the list of proposed topics.  This will help Mayo prepare for the meeting.

LEXEVS- 970

• OWL2  - prioritize this work

Scott suggested that we create a new story to capture the next set of OWL2 changes.

We discussed the possibility of creating an "epic" for all of the OWL2 issues/features.

TODO: Mayo to create JIRA items for the known OWL2 issues today and then close LEXEVS-970.