NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 2

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] x

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
CoryAdd link to Maven Opts for end users2016.12.21  

Open

...

Sprint Status

 

Current Sprint -  Sprint 47 Sprint 48 (January 519, 2017 – January 18– February 1, 2017)

16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint47Sprint48

LexEVS Java 1.8 & MySQL 5.6 Environment

  • Status update: Jason

Discussion Points:

  • During our morning meeting, Jacob asked if we wanted to use CentOS 7 or RedHat 7. 
  • We suggested CentOS 7 as that is part of the tech stack that will be used in production. 
  • Jacob mentioned that they were waiting for the DB specialist. 
  • He is anticipating this to be completed next week.

Decision Points:

  • We requested to go with CentOS 7 as this is what will be used in production.

6.4.1.3 Snapshot build update

Discussion Points:

Decision Points:
  • We will build a snapshot by this Friday for Rob to use for another load on Monday.

Decision Points:

  • Mayo will build another 6.4.1.3.SNAPSHOT by this Friday for Rob to use for another load on Monday.
  • Mayo team will notify NCI dev team when this is complete.

NCI Nexus Server Migration Update

Discussion Points:

  • LexEVS Build Configurations and Status 
  • Cory has now been able to publish to the NCI Nexus server with the Ant scriptwill test the encrypted user id and pw when the SCM provides the encrypted information.

Decision Points:

Value Set Architecture Update

Discussion Points:

  • The Mayo dev team will be meeting with Kim tomorrow to continue gathering requirements.

Decision Points:

Transitive OWL Discussion

  • Blank Nodes
  • Implementation Considerations

Discussion Points:

  • Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVS-25851157
  • Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVS-2651
  • Scott has been researching how blank nodes are handled with respect to transitive closure in OWL.
  • Larry mentioned that role group is being lost in the LexEVS model.
  • 2670
     
  • After three different meetings, we came up with some value set requirements.
  • The two main requirements are:
    • Better logging to help determine if there were any failures for resolving the 760+ value sets.
    • Resolving all 760+ value sets should be quicker.
  • Scott has come up with a potential solution through the work in the above two JIRA items.  He created scripts to do the following:
    • Load value set definitions
    • Load resolved value set coding scheme
    • Removal tools for the above
  • Rob and Tracy requested to allow to provide tags for coding schemes and to log the names of the value sets.  This has added some database calls and slows it down someWe can remove the anonymous nodes in transitive closure.  They will still be available in the API to the browser.

Decision Points:

  • Scott will create JIRA issues to remove anonymous nodes from transitive closure.
  • Better understand role group and any use cases associated with it.
  • run against all of the value sets to test performance locally.  He will get the list from Rob or Tracy.
  • We will create a snapshot build for Rob to test a load early next week.
eCache issue updateechache issue

Discussion Points:

  • This was an outside user that accessed the NCIT through a search and the page didn't load.
  • Others tested this and it worked fine. 
  • However, Larry saw it happen again today searching on the term browser.
  • This failed initially on Chrome (was also seen in IE, FF, and Chrome).
  • Scott mentioned that there may have been some invalid text in the history API.
  • Kim suggested that this didn't have anything to do with the history API.
  • This was seen on the PROD server.
  • This issue was seen on the NCIT.

Decision Points:

  • Rob to request the container to be restarted.
caCORE follow up

Discussion Points:

  • We followed up with Bob Kline and mentioned that the CTS2 service returns the same data but in a different format.
  • The lexevs API URL can be modified so it doesn't change.

Decision Points:

CTRP Thread Issue

  • Cory to update

Discussion Points:

  • This issue has been resolved.
  • The fix has been put into the 6.4.2 branch.

Decision Points:

  • happens when a user clicks on links in the search results from the browser.
  • We will continue to monitor this and investigate when this happens again.

Decision Points:

  • Scott will request access to the browser logs from Jacob for further investigation.

caCORE follow up

  • lexevs API URL
  • Follow up with Bob regarding data services

Discussion Points:

Decision Points:

CTRP Thread Issue

  • Data Services discussion

Discussion Points:

Decision Points:

  • Tracy will contact CTRP to start a conversation about the data services going away in the next release.
LexEVS External Users

Discussion Points:

Decision Points:

CTS2 handshake error

Discussion Points:

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

Decision Points:

  • Mayo team will document this issue on the CTS2 wiki.  There is nothing else to do.
LexEVS External Users

Discussion Points:

Decision Points:
Proposed Backlog Review Items

Discussion Points:

Decision Points:

  • We will come up with a new list of issues to groom for next week.
Team Absences

Mayo Team

  • Cory - Jan 27
  • Scott -
  • Craig -

NCI

  • Tracy
    • Feb 21-24
  • Rob

...