Versions Compared

Version Old Version 1 New Version 2
Changes made by

bcarlsen (Unlicensed)

bcarlsen (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Sprint to continuing to develop core features of the application

Fleshing out APIs

  • Content service rest
    • Implement getConcept, getDescriptor, getCode, getLexicalClass, and getStringClass
    • Implement rest client 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)
  • Handle single-level branching (no sub-branching). 
    • (branch = :branch OR branchedTo not like :branchMatch)
  • escgSemantic search (via search criteria)
  • 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 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

 

Unit tests

  • Model objects (content)
  • List objects
  • Helpers

...

  • 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.

...