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     

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 
Endle,  CoryMayo x
Sharma, DeepakMayo 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
      

...

Discussion Points:

  • If we give NCI one release with everything, they would have to test the browser and other clients (caDSR) with the upgrade to Java 8.
  • Larry suggested this would be too much of a change for the clients at this time.
  • Scott suggested delivering all of the code that is compiled in Java 1.7.
  • Tracy mentioned that for the browser, they were able to redirect HTTP to HTTPS so end users were not forced to have to change their links.
  • We discussed testing the current LexEVS 6.4 and whether to continue testing or wait until the HTTPS changes are added in.
    • Tin suggested halt testing until the new build is created.
  • Larry suggested to create another build in Java 8. This would enable clients to test connecting to a Java 8 service and determine if their clients are compatible.

Decision Points:

  • There will be no changes to 6.3.
    • This will run http.
    • It may be shutdown at the beginning of 2017.
  • LexEVS 6.4.0 will be the HTTPS fix.
    • This will include the loader updates.
  • LexEVS 6.5 will be the Tech Stack update.
  • Mayo team will update the wiki page to show what changes are required to move to HTTPS.
  • Mayo will rebuild LexEVS 6.4.0 to have the HTTPS and Loader changes. It will be re-tagged as the same 6.4.0.FINAL code base.
    • This will be built in Java 7.
  • The CTS2 and LexEVS Remote API PTEs need to be updated to allow for HTTPS.
  • Tickets need to be created to configure QA/STAGE/PROD for HTTPS.
    • NCI needs to discuss with Systems to determine if they can handle parallel systems: one for HTTP and one for HTTPS.

    Sprint Status

     

    Current Sprint -  Sprint 37 (August 18, 2016 – August 31, 2016)

    LexEVS 6.4 S13-500 Agile Development - Sprint Status

    Main work items that have been completed in sprint 36:

  • Tech stack - Java 8/CentOS7 testing and verification is complete.

    • Status#SprintStatus-Sprint37

    The Mayo team is working on testing features and mavenizing the remote client

    HTTPS updates have been completed and verified

    .

    QA Tier Status

    Test update - Tin

    • AppScan

    Discussion Points:

    • Testing is in progress.
    • Tin requested an AppScan for CTS2.

    Decision Points:

    Release Plan for

      • HTTPS
      • Tech Stack
      • Loaders
    Backlog grooming

    Discussion Points:

    • We asked if NCI had any comments on the backlog and priorities.
    • Tracy suggested looking at the task to convert LexEVS to Maven.

    Decision Points:

    OWL2 Loader Verification

    Discussion Points:

    • No testing has been done.

    Decision Points:

    6.5 Planning

    Discussion Points:

    Decision Points:

    • The remote API appscan had an issue that was fixed by the systems configuration team.
    • The CTS2 appscan didn't really test the REST services. The scan tried to find the WSDL, but that didn't do anything.
      • The appscan would need to know how to construct our REST calls.
      • Larry suggested that the tests didn't find any issues and that should be suffice.

    Decision Points:

    • We decided the appscan is fine and we can move on.

    Release Plan for 6.4.1

      • PTEs updated

    Discussion Points:

    Decision Points:

    • The NCI team will deploy to DEV and test.

    OWL2 Loader Verification

    • Jira
      serverNCI Tracker
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-2245

    Discussion Points:

    • There is concern about the OWL2 loader issue of the Thesaurus.
    • Scott asked if we need to fix this now.
    • Tracy mentioned that we are not loading OWL2 into production.
    • In the future we should be test loading the thesaurus with OWL2

    Decision Points:

    • We will hold off on the OWL2 fix until next sprint before considering it.

    HTTPS document review

    Discussion Points:

    • Remote Client HTTPS Requirements
    • We went over the changes for the remote client as well as for the CTS2 REST client.
    • In order to help clients understand if clients need to make changes, Larry suggested that we add some text to have the end user contact us with their sample code.

    Decision Points:

    • Scott will add a message to the https document that the end users can send the Mayo team a snippet of their code and we can assist in analyzing what changes (if any) they would need to make.

    LexEVS External Users

    • Alexander

    https://github.com/cts2/lexevs-service/issues/2#issuecomment-240205829

    We assisted have responded to the user in configuring lexevs and cts2 and getting it up and running. This user will be loading HL7 next.that the fix has been checked in for the issue he found.

    Team Absences

    Mayo Team

    • Deepak - Sept 1-6?, Sept 5
    • Cory - August 12, Sept Sept 5
    • Scott - August 15, Sept 5
    • Craig - August 24 -29, Sept 5

    NCI

    • Rob Wynne - Sept. 1-5

    ...