 |
Page History
...
- Ability to look at data in a graphical way would be important.
- Command Line usage - List Schemes - can return 700+, so prefer to use the UI.
- Usage of the UI for troubleshooting to review the data in the database.
- Minimal ability to look at data would be preferred (fully graphical is not required)
- Administrative tasks not required in the GUI (only in the cmd line tooling)
- Ability to load metadata at the same time as the load.
- Web based tool.
- We need to replace based on functionality used by Browser
- graphical hierarchy representation (tree extension?)
- Optimal or best practice as an alternative
- providing code snippets for end users as options
- Secure any admin code (Loading, changing code systems) on a web based gui is a concern
- Could be potentially be used as a browser for technical users on an NCI Production server (Discussed)
Decision Points:
...
Prioritization and Debrief
- Discuss OWL2, RRF, LexEVS, CTS2, Browser, and all previous topics
- Discuss future architecture
- Determine next steps/road map and priorities
...
- There is a request for admin ability for editing the preferences and manifest.
- Currently, there is no way to view what metadata is loaded.
- Investigate ability to combine data from the metadata and manifest files into one file.
- This would make administration/loading easier.
- Post load options may be an issue.
- History loader creates multiple errors when loading - there is an existing JIRA item.
- May be caused by DB timeout.
- Investigate what is causing.
- LG xml Loader is used to load maps. However, it doesn't take in account of the type of maps (it could). Not sure the rankings can be applied.
- No existing issues, but may find some loading additional maps
- SY relationships and Ranking are provided.
- Monthly changes are applied.
- GUI Performance during x-forwarding noted by Rob.
- File system preferences - lock?
- UI is good for Tagging to Production
- UI is good for Removing a Coding Scheme
- Listing Schemes in CMD - ListSchemes.sh - formatting is limited to column width.
- Default, do not show entire width.
- Minimailly add 10 chars to URL
- Minimally add 5 chars to Versions
- Add option to see full length's of all fields.
- Add option to see minimal information.
Decision Points:
| Time | Location | Topics | Participants |
|---|---|---|---|
| 10:00 AM - 12:00 PM | 1W030 | Prioritization and Debrief
|
Attendees: Kumar, Larry, Jason, Sherri, Rob, Tracy, Cory, Scott, Craig
Discussion Points:
Architecture
- Future considerations.
- Smaller services -
- For example, Coding List listing service as a separate service.
- Concerns around ability to deploy up the tiers
- Current requirements will prohibit how quickly services can be exposed.
- Concerns about tech stack upgrades across services. Micro Services may or may not be impacted by upgrades (some or all).
- If addressed well, we can get rid of silos and duplication.
- Resources are a concern,
- Containers, JETTY, and how to balance.
- Security
- Scanning will take nearly as long as the large service.
- Instead of re-architecting all, focus on new and additional functionality (along side existing LexEVS)
- No longer would need clients to include jars, dependencies.
- Smaller services -
Decision Points:
- Investigate services architecture to support new and additional functionality.
Attendees:
Discussion Points:
...
| Time | Location | Topics | Participants |
|---|---|---|---|
| 1:00 PM - 2:00 PM | 1W030 | Prioritization and Debrief (Continued if needed) |
Attendees:
Discussion Points:
Strategic direction - RESTful services
- Moving to micro architecture in new areas in functionality for LexEVS
- Integrated REST services across LexEVS, Triple Store, Clinical Trials (Integrated REST Services)
- Future MDR redesign effort - areas of service support of terminologies.
- Future CTRP support
Decision Points:
