Page History
...
Attendees: Larry, Jason, Kim, Craig, Scott, Cory, John, Liz, Sima, Rui, Natalia, Tracy, Sana, Tin, Gilberto
Discussion Points:
- caDSR Team represented by Sima, Natalia, Vikram
- caDSR Applications that use EVS
- Sentinel - Alerts for concepts, job that does concept clean up (compares concepts)
- Curation tooling - links to concepts, and search results.
- CDE Browser - Concepts used from search results.
- Semantic integration workbench - concepts used from search results
- CDEs
- Utilize the NCIT, NCI meta,
- Look into NCIT - will use the concept to describe the CDE.
- Organizing concepts to build CDE terminology.
- CDEs are used for forms (permissible values on forms)
- Tooling hasn't changed or been replaced.
- Currently use JARS and put in /lib
- Using Remote API today.
- Recently removed EJB
- Need to consider architecture in the future.
- MDR is planning to architect a solution moving forward.
- Currently searches are restricted to preferred terms.
- Building data element - definitional information, preferred name
- Existing CDE - pull back perferred name.
- Current Tooling Issues
- Need to have a data load completed to PROD.
- Confirmed data load and ready once things move to production.
- Remote API Architecture
- Issues
- Replacement of JARS
- Serialization of objects.
- Issues
- Proposed Architecture?
- REST-ful API
Decision Points:
- caDSR to provide list of what is currently used in the Java API
- EVS team to provide feedback as to how to do things better.
- EVS team to ensure that if REST-ful API is created, functionality to be prioritized.
Time | Location | Topics | Participants |
---|---|---|---|
10:00 AM - 11:00 AM | 4W030 | RESTful API Discussion
|
...