Attendees

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
ISx
Lucas, Jason R
ISx
Bauer, Scott  Mayox
Stancl, Craig
Mayox
Endle,  CoryMayox
Solbrig, HaroldMayox
Jiang, GuoqianMayox
Wynne, Robert    NIH/NCI [C] 
Tran, Tin    NIH/NCI [C]  
Carlsen, Brian NIH/NCI [C] 
Wong, Joanne NIH/NCI [C] 

Kuntipuram, Kumar

NIH/NCI [C]

 

Haber, MargaretNIH/NCI  x
Campbell, JohnNIH/NCI  x


Goals

  1. LexEVS and CTS2 are planned to continue as key components of NCI terminology services, but NCI also plans to extend beyond them, notably with RDF triple store SPARQL and REST components.  This raises important design and coordination issues.
  2. REST services need substantial extensions, within and beyond CTS2.  NCI plans to offer REST APIs that can support the requirements of its own and others’ applications, and expects a significant component to be REST services from the RDF triple store.  An obvious test case is ability to support EVS browser functionality (even while these browsers will likely use the Java API for some time to come).
  3. We face some immediate needs from other users, notably CTRP and GDC, so need to clarify design approaches and produce new services based on them in the relatively near term.


Agenda

Review and discuss (Kim's/Jason's) concerns

  • Each of these are to support the browser (via java API)
  1. Handling of metadata
    1. Metadata to be stored as RDF
  2. Supported search algorithms (currently, only exactMatch, startsWith, and contains are available)

    1. CTS2 service - would like to have CTS2 support the full LexEVS Search Extension

    2. Need to confirm that the Lucene algorithm is available.

  3. CTS2 Handling of namespace in read service. Could namespace be included as a parameter in a REST call?

    1. entity read service is able to include namespace.

    2. Need to confirm the responses to determine both namespaces are supported for single concept code
    3. Need to provide ability to return concept with different namespaces.
  4. Search against multiple coding schemes (count, ranking, iterator, pagination)
    1. Required for browser
    2. Currently allows search against all, but not a designated set of coding schemes.
  5. Search against multiple mappings and value sets (count, ranking, iterator, pagination)

    1. Required for browser

    2. Currently allows search against all, but not a designated set of coding schemes, mapping and value set API may require additional public methods

  6. Mapping search (count, ranking, iterator, pagination) - currently iterator and pagination are broken in remote LexEVSAPI)

    1. CTS2 will no longer be running against remote (only local)

    2. Broken iterator no longer issue if running local.

  7. Support for property and relationship search?
    1. Need further notes on this.  Graph implementation should cover relationship search.  Properties are currently restricted to presentations, it may mean an extension to supply better coverage to generic property types.

Review and discuss (Kim's/Jason's) concerns

  • Each of these are to support the browser (via java API)
 
Next Steps

 

  • Review notes from previous F2F.
  • Determine priority for browser support
  • determine requirements that fit into CTS2
  • Determine an architecture to support requirements that do not fit into CTS2
  • Determine integration of LexEVS, CTS2, Triple Store
    • separate rest services? 
    • discussion necessary