NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 1

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.

...

NameRolePresent
Wright, Larry NIH/NCI   x
Fragoso, Gilberto NIH/NCI     x

De Coronado, Sherri    

NIH/NCI    x

Safran, Tracy

NIH/NCI [C] x
Ong, Kim L
IS x
Lucas, Jason R
IS x
Bauer, Scott  Mayo x
Stancl, Craig
Mayo x
Endle,  CoryMayo x
Wynne, Robert    NIH/NCI [C] x
Tran, Tin    NIH/NCI [C]  x
Carlsen, Brian NIH/NCI [C] 
Wong, Joanne NIH/NCI [C] 

Kuntipuram, Kumar

NIH/NCI [C] 

...

This discussion is to touch base with three different groups to bring everyone up to speed on the latest developments: Northrup Grummond, Mayo, and Gilberto.

Jason - Now has a "customer managed" VM set up.  Still need to move the existing triple store to this VM.

Jason's team also looked at NCBO OWL converter.  They had an issue with NCI OWL being converted (RRF to turtle).

Scott asked what is the use case for the triple store? NCI suggested the following:

  • To expose NCI thesaurus
  • Expose a SPARQL endpoint
  • Anything that will help the browser to display relationships

Another use case would be for a triple store over the Metathesaurus.

Gilberto suggested two use cases:

  • In general, a SPARQL endpoint could be used for better semantic web integration.  To facilitate queries across systems (federated queries) for the NCI thesaurus.
  • Specific for LexEVS,  it should either support a general endpoint or integrate the functionality within our codebase.

Scott suggested that if a SPARQL endpoint is behind LexEVS, our hierarchy API (isA relationships) would call the endpoint instead of the underlying DB now.

  • Larry mentioned that the endpoint may be used for other relationships than just the hierarchy API mentioned above.

Graph DB vs. Triple store - there hasn't been a decision to go with one or the other.  If a graph DB works better for LexEVs, than this would be an option.

Gilberto mentioned that the paper review is complete.  They will be getting demos from vendors:

  • Alegro Graph
  • Stardog
    • Virtuoso
    Sprint Status

    Current Sprint - Sprint 22 ( January 21, 2016 – February 03, 2016 )

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

    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 >= 2016-01-20 AND created <= 2016-01-27
    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 >= 2016-01-20 AND created <= 2016-01-27
    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

     

    CTRP Planning

    • Update from Larry

    No updates from Sherri. 

    Gilberto was at CTRP's demo on Monday for their requirements.  He mentioned that there were no LexEVS requirements at this time.

    Sherri was wondering if there are any requirements for LexEVS.  Larry commented that there were no requirements for us at this time.

    Larry will send a note to Jose to see if they have any requirements for LexEVS

    		Triple-Store/SPARQL Discussion

    CTRP Planning

    • Update from Larry
    		No Update

    .

    Value Set Resolution

    Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVS-1516

    		Tracy has a ticket to update the group to lexevsdb.  Jason has implemented the change.  If the problem still persists, we will need to debug this issue.

    The properties file for the browser was missing the cache and max value properties.  This properties file needs to be propagated from from DATA_QA to PROD to fix this issues.

    Rob will update the this JIRA issue with this information.

    6.4 Performance testingTree Extension Issue

    Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVS-1528

    Scott reviewed this issue and this will need further investigation.  Depending on how critical this is, it may need to be looked at during the next Sprint.

    Jason mentioned this is critical for the next release of the browser - release 2.8. 

    The scenario is when you pull up a tree, and click on the "..." it freezes the whole tree.

    Jason said they are planning to deploy in April.  We will need to prioritize this issue to be completed before then.  Larry suggested that we work on this right after the lucene issues are fixed.

    1527

    Ability to get and load all of the value sets

    Tracy put the NCI value sets out on the SFTP site for Scott. 

    Scott will load these value sets on our DEV system.

    Scott will be using Java JMH performance harness for performance testing of reading all of these value sets.

    This will show the difference between the multi index performance and the single index performance.

    Search Extension Testing Requirements

    This what is used for text searching. 

    We will want to focus our testing on the text searching performance.

    Jason mentioned they will test the 6.4 artifacts with the browser scripts.

    Nexxus TestingScott will be testing the Nexxus upgrade on the Wednesday, 2016.02.03.

    Production Remote Service not accessible

    • Tracy

    Scott is waiting to get the PROD logs to investigate further.

    Tracy will send the logs to Scott.

    6.4 Artifacts

    We have sprint 21 artifacts available for 6.4. 

    This release has the search extension features working.

    Scott/Cory will install this on the NCI DEV system.

    6.3.0.2 Testing UpdateNCI will test and let us know their findings

    Search Extension Testing

    The search extension API is now complete.  We would like to understand the use cases from the NCI team. 

    We will need to test 6.3 and 6.4 in a test harness to determine any performance issues.

    In 6.3, search (query across a large number of systems) could take a long time (timeout after 5 minutes).
    LexEVS External UsersNo updates.

    Namespace Navigation between coding schemes

    • Review how this works

    Gilberto wanted to review way this namespace navigation works between coding schemes.

    The way it is implemented, we can go across coding schemes.  Scott mentioned that there are limitations based on the namespaces.

    If there are two coding schemes with the same namespace, this is not supported.

    If there are multiple versions of the coding scheme, it will go to the PRODUCTION version.

    Scott suggested that Gilberto should come up with a scenario and then we can create a manifest to show how it can be supported.

    Gilberto suggested that they will test with OBI and NBO

    		Nexxus TestingScott is able to log into Ant Hill Pro.  He should be able to test the build/deploy when the new Nexxus system is deployed on Saturday 2016.01.30

    .

    JIRA Issues

    Recent LexEVS Related Bugs and Features (within last week)

    ...