NIH | National Cancer Institute | NCI Wiki  

WIKI MAINTENANCE NOTICE

Please be advised that NCI Wiki will be undergoing maintenance on Thursday, May 23rd between 1200 ET and 1300 ET.
Wiki will remain available, but users may experience screen refreshes or HTTP 502 errors during the maintenance period. If you encounter these errors, wait 1-2 minutes, then refresh your page.

If you have any questions or concerns, please contact the CBIIT Atlassian Management Team.

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 
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 49 (February 2, 2017 – February 15, 2017)

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

DEV

blade

Server Configurations

  • Planning and usage discussion

Discussion Points:

  • Dev blade for CentOS 7 being created - will be used for java 8, MySQL 5.6 (6.4/5 release)
  • VM (snapshot) server for Mayo (CentOS 6) pointing to MySQL 5.6
    • Mayo team requested remote API, URI resolver, CTS2 service containers on there as well.
  • The Browser team will want to test our Java 8 LexEVS release once we install on the Dev bladeLarry mentioned that Jacob said the DEV blade server is ready.

Decision Points:

  • Validate that Tomcat 8 works with our Java 8 release.

LexEVS Java 1.8 & MySQL 5.6 Environment

  • Status MySQL update: Jason

Discussion Points:

  • Scott's tests on MySQL 5.6 is loaded and ready for use/testingshow that performance is as good (and better in some cases).

Decision Points:Road map to

6.4

.2 release

.1.3 Snapshot build update

  • Creating
  • Update
    • Migrating to
    • 6.4.1.3.
    2
    • FINAL
    		Cory is merging all

    Discussion Points:

  • Migrating to LexEVS 6.4.2
    • Additional loader enhancements/fixes don't need to go into 6.4.1.
    3 changes into the 6.4.2 branch of code. 
  • Larry suggested adding workflows to the migration wiki for migrating the Java API, and REST
  • How does the user know what LexEVS components and versions they are using?
    • We need to provide the user with places to look in their software in order to determine what LexEVS components they are using.
    • Example: If you are using <base URL>/"GetXML" method, then you are using the Data Service that will be going away.
    • We could structure this as a FAQ.
  • How do I know it affects me?
  • How does it affect me?
    • How do I update?
  • The Apache logs may indicate what services are being used (or at least the URLs).

    • Decision Points:

    • Scott to update the document.

    Next LexEVS Release Version

    • 6.4.2 vs 7.0

    Discussion Points:

    • Dropping the legacy Data Services is an API change.
    • The other existing APIs have not changed. 

    Decision Points:

    • Mayo team to determine what new jars were added for the upgrade to Java 8.  Add this to the NCI wiki.
      • Clients may need to update these jars.
    • Larry suggested that we add a section to the migration wiki for Java 8 migration issues that end users will encounter.
      • Include issues that the Mayo team ran into as well as other migration links from Oracle, if applicable.
    • LexEVS 6.4.1.3 will be running in parallel with LexEVS 6.4.2 while clients migrate.
    • Based on our discussions we agreed the version will be 6.4.2.

    6.4.1.3 Snapshot build update

    Discussion Points:

    • LexEVS 6.4.1.3 Release Notes
    • Rob was able to verify LEXEVS-812.
    • Rob wasn't sure how to verify LEXEVS-2585. 
      • Scott suggested there was an example in the JIRA issue.

    Decision Points:

    Value set loads with OWL2 source for NCIT

    Discussion Points:

    • Scott suggested there is not enough support in OWL2 to resolve value sets.
    • Scott will work with OWL2 loads to investigate further.
    • Scott asked when OWL2 will be used in Production (for prioritizing our work).
      • Gilberto mentioned that they will be migrating at the end of March, 2017.
      • The first version of the NCIT in OWL2 will come out the end of April.

    Decision Points:

    • Based on the discussion, Scott will continue his work on these issues in the current sprint.
    • Larry suggested that there should be an announcement that NCIT is transitioning to OWL2.
    MAX_CHILDREN in the TreeService getTree method

    Discussion Points:

    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-2707
    • This is a a tree extension issue.  The JSON is not sorted.
    • Kim has a workaround for this.
    • Kim requested that the tree extension issues should be worked on.  This will help to make the browser more reliable.

    Decision Points:

    URI Resolver over HTTPS

    • Update

    Discussion Points:

    • All tiers have been updated to use the URI Resolver over https.

    Decision Points:

    eCache issue update

    Discussion Points:

    • Jacob sent the links to all of the logs on Prod. This will allow the dev team to review the logs when a user runs into this issue again.

    Decision Points:

    • x. 
    • They can wait until the Java 8 release.
    • The NCI dev team can use the Java 8 release of LexEVS to

    Decision Points:

    Value Set Loading Enhancements

    • Status from Rob

    Discussion Points:

    • The additional fix from Scott will need to go into the 6.4.1.x release.
    • Rob/Tracy mentioned that testing with the Value Set load script from Scott, was done with OWL2 and never completed successfully.

    Decision Points:

    CTS2 RESTful documentation

    Discussion Points:

    • The Mayo dev team will look into the different query requests and see what options there are
    • Calls to return the results - are there limitations?
    • Filter down - use a programming language to parse JSON and make subsequent calls.

    Decision Points:

    • Cory will respond to the team with what is possible with CTS2 REST calls for the given examples.
    CTS2 RESTful API questions

    Discussion Points:

    Decision Points:

    • The Mayo team will investigate tools to auto-generate CTS2 RESTful API
    LexEVS External Users

    Discussion Points:

    • None
    		LexEVS External Users

    Discussion Points:

    • Craig introduced Mary to the correct contacts for her value set usage.

    Decision Points:

    Proposed Backlog Review Items

    Discussion Points:

    Decision Points:

    • Craig will create a list of issues to prioritize and send out a list.
    Team Absences

    Mayo Team

    • Cory - Feb 20
    • Scott - Feb 1013-16
    • Craig - March 6-13

    NCI

    • Tracy
      • Feb 21March 9-2417
    • Rob

      • Feb 17

      • March 20-24

    JIRA Issues

    ...