...
Fleshing out APIs
- Mobile friendly site
- Terminology subsetter
- sort files
- take initial concepts
- load relationships.
- find all concepts on "other side" of rels and all paths to root
- find all metadata concepts involved (and all paths to root)
- Content service rest
- Implement getConcept, getDescriptor, getCode, getLexicalClass, and getStringClass
- Implement findConceptsForQuery (ignore branching for now) and related methods.
- Implement rest client as well
- Implement methods for accessing subsets as well
- Begin developing integration tests to validate the data (could start with content service tests)
- 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)
- Add property chains (to metadata)
- TreePosition (and tree position computer) - childCt
- Handle single-level branching (no sub-branching).
- (branch = :branch OR branchedTo not like :branchMatch)
- Semantic search (via search criteria)
- DONE: UserPreferences - tty list
- Websocket (for a WebsocketWorkflowListener)
- "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 additional 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
- escg (expression grammar - research)
- DONE: Startup routines should verify the presence of "DEFAULT" handlers when they are needed to exist
- DONE: ContentServiceJpa/Rest
- graph resolver doesn't resolve relationships
- rest call for geting the relationships of a concept/descriptor/etc
Testing
- Model objects (content)
- List objects
- Helpers
- Metadata service integration test
- Content service integration test
...