Overview
Sprint to continuing to develop core features of the application
Fleshing out APIs
- Domain model
- Have a boolean "hasChild" count associated with concept, descriptor
- do as part of transitive closure computation (as a separate step afterwards to set the field)
- Handle single-level branching (no sub-branching).
- (branch = :branch OR branchedTo not like :branchMatch)
- escg
- UserPreferences
- tty list
- Websocket (for a WebsocketWorkflowListener)
- DONE: Deep copy shoud actually make copies (not just reuse the members) - that's why it's "deep"
- one-to-one and primitive/String collections are simply borrowed
- any nested object collections have individual elements copied (and deep copied).
- Startup routines should verify the presence of "DEFAULT" handlers when they are needed to exist
- ContentServiceJpa/Rest
- graph resolver doesn't resolve relationships
- rest call for geting the relationships of a concept/descriptor/etc
- "smart" RRF loader should support a config file to indicate what level at which definitions should be attached and should handle RXNORM and NCIt concepts.
- Updated UI for UMLS
- add an additoinal picklist for "id type"
- Base view around a Concept Report
- page relationships (and possibly attributes)
- compute/page "contexts" - need to actually compute paths to the root
Unit tests
- Model objects (content)
- List objects
- Helpers
Admin Tools
- RRF Loader
- Finish metadata loading
- Do content loading
- RRF Loader - single source
Future Stuff
- Sub-branching
- Consider tree positions
- Handle mappings - may be not worth it
- Implement an RF2 loader (use DL features)
- Implement a ClaML loader
- Support semantic network (e.g. sty rels, etc). - probably want to wait for a real ontology - and maybe even load it as such.