NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

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

...

TimeLocationTopicsParticipantsResources
2:00 PM - 3:00 PM  5-W-032
User Group Discussion - FDA and CDISC

User Teams to share how they are using EVS and  discuss requirements/priorities for the future.

  • APIs: Java, REST (CTS2 or 3-store), SPARQL, FTP
  • Backwards compatibility of server/client/data releases
  • Incl: Java/jar file issues and future
  • Incl: New terminology server API/content/other needs.

Editors

Liz, Erin, Brenda

 

Attendees: 

Bron, Lub, Larry Wright, Scott Bauer, Rob Wynn, Jason Lucas, Liz, Gilberto Fragoso, Tracy Safran, Erin Mulbrandt, Lori Whiteman, Margaret Haber, Terry Quinn, Sherri de Coronado, Sana Din

Discussion Points:

  • FDA
    • Report Writer
      • Terry generates 25 files (FDA and others) every month.  Would like to be able to batch command and provide the dates needed for report writer.
      • Files are posted to FTP site.
        • These files contain subsets
      • Changes are indentifed by doing an exact compare of both sets of data (addition, changes, deletions)
      • Rob and Tracy are working on new report writer that should help make this process tolerable.
  • CDISC
    • On the cancer.gov page for CDISC Terminology - as there are alot to scroll through, request for a table of contents to make it more usable.
    • OWL/RDF updates to metadata model for CDISC (Rob, via TopBraid)
    • Request to update the CDISC new term suggestion request form.
      • Update Request type dropdown
      • Update Code List dropdown
      • Possible type-ahead

Decision Points:

  • Action Items
    • Request for a table of contents on the CDISC Terminology page.
    • Request to update the CDISC term suggestion request form.

 

TimeLocationTopicsParticipantsResources

3:00 PM - 4:00 PM

5-W-032
User Group Discussion - CTRP / CTS-API

User Teams to share how they are using EVS and  discuss requirements/priorities for the future.

  • APIs: Java, REST (CTS2 or 3-store), SPARQL, FTP
  • Backwards compatibility of server/client/data releases
  • Incl: Java/jar file issues and future
  • Incl: New terminology server API/content/other needs.
CTRP / CTS-API - managers,  developers, Tiger team (Gisele, Samantha, David, Brian, Peter, Tracy, Jason, others) 

...