NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 7

changes.mady.by.user Unknown User (endlecm)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (endlecm)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Sprint Status

Current Sprint - Sprint 15 (October 15, 2015 - October 28, 2015)

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

Sprint Planning

Issue Prioritization

Recent LexEVS Related Bugs and Features (within last week)

Jira
serverNCI Tracker
columnskey,summary,type,created,reporter,priority,status,versions,fixversions
maximumIssues20
jqlQueryproject = LEXEVS AND (TYPE = bug or TYPE = "new feature" or TYPE ="Improvement" or TYPE ="Inquiry") AND created >= 2015-10-14 AND created <= 2015-10-21
serverId7954a81f-12da-3366-a0ef-97c806660e7c

 

Recent CTS2 Service Related Issues (within last week)

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = LEXEVSCTS2 AND created >= 2015-10-14 AND created <= 2015-10-21
serverId7954a81f-12da-3366-a0ef-97c806660e7c

 

Issue Grooming

Prioritize JIRA issues (fix version 6.4)

Jira
serverNCI Tracker
columnskey,summary,type,created,reporter,priority,status,labels
maximumIssues20
jqlQueryproject = LEXEVS and fixVersion=6.4 AND issuetype = Bug AND (status = Open or status = "Reopened")
serverId7954a81f-12da-3366-a0ef-97c806660e7c

 

 

Sprint Deliverables - Updates

  • 6.3.x
  • Lucene
Lucene build - Cleanup script is broke. 
Build practice is out of date, discuss single jar vs zip file

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 how 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.  They 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.

Horizontal Coding Scheme searchesTODO: Craig will add this to the Face to Face topics.
Face-Face Planning

December 8 - 10 on-site.

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 Face to Face meetings.

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

  • Update
Unless Scott noted that unless you set the resolve flag in the query, it does not go to the DB.

LEXEVS- 970

  • OWL2 Issue breakdown update

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

TODO: Schedule Scott to work with Gilberto a time to 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
LexEVS Meeting next week (2015.10.28)

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

Questions around how NCI uses sorting mechanisms

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.

MedDRA 18.1

If the CUI is left blank will it cause a problem?  We don't think so.

...