Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 17 Next »

Overview

Sprint to continuing to develop core features of the application

Fleshing out APIs

  • DONE: Double-check that all rest services always close the service (e.g. in "finally")
  • PG (in progress): Mobile friendly site
  • Lucene enhancements
  • 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)
    • get relationships for a concept
    • autocompletion methods (BAC)
    • treeposition methods
      • TreeList findTreesForConcept/Code/Descriptor(String terminologyId/terminology/version, boolean includeChildren, PfsParameter pfs)
      • findConcept/Code/DescriptorTreesForQuery(String terminology/version, String query, boolean startAtRoot, PfsParameter pfs)
      • getRootConcepts/Codes/Descriptions

    • DONE: Subset services
      • getSubset - by id or terminologyId - NO REST CALL FOR THIS
      • getAtomSubsets - SubsetList
      • getConceptSubsets
      • getSubsetMembersForAtom - takes atom terminology id
      • getSubsetMembersForConcept - takes a concept terminology id
      • findAtomSubsetMembers
      • findConceptSubsetMembers
  • Domain model
    • DONE: Add property chains (to metadata)
    • LexicalClass - set normalized string (needs handler) 
    • 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)
  • "Marked parent refset" - or in this case for subsets - identify the concept ancestors (e.g. of concept subsets) so they can be labelled in a hierarchical display
    • decorate tree position operations when handling browser stuff.
  • 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

 

User Interface Dev

  • Browser with hierarchy

  • Basic concept editing (editable report)

  • Subset management (e.g. “refset” tool)

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