Page Comparison

...

Core Application Enhancement - P2

• Release criteria integration tests
  • Verify no *java classes have System.out.println
  • Verify no *java classes have TODO
  • ...
• PG: Support RF2 "atom association refset members" as atom relationships.
  • * REMAINING: Need to decide how to handle non-concept association reference refset members (e.g. descriptions)
  Enable glass pane while switching tabs (between content/metadata)
• Bring "source data file" and "source data" over from transformer application, along with other things.
  • Put the objects into the package structure of terminology server (e.g. put with Project and User)
  • Need to update transformer too so it continues to work.
  • Leave mojos behind. 
• Add features for "deep" relationships when browsing UMLS.    
  
  • it is definitely only for "concept" and for "metathesaurus" content
  • Add new section to concept report (e.g. "Deep relationships")
• Advanced search
  • LATER: Expression. - e..g. "Search Criteria" - for "descriptionLogicTerminology"  only
    • descendants of
    • has relationship -> xx
• Show "atom" subset information in the report.  Only concept (or component) subset (or refset) information is being shown.  this may involve a change in the graph resolver to return the data.  i.e. for Snomed you should be able to tell what is just british.

Editing Features

• Basic metathesaurus editing
  • Add/remove STY
  • Add/remove atom
  • Move atom
  • Split atoms from concept
  • Merge concepts
  • Add/remove concept relationship
• Publication Process
  • RRF
• Project
  • Figure out how to capture "project scope" for SNOMED and for UMLS in a generalized way.  Update project objects to be able to properly capture (and compute) project scope.  NOTE: the scope definition may involve concepts/terminologies/semantic types.  IN that event, the scope computer gets a little bit more complicated.
• Test loading a DB with envers auditing disabled and then making changes in a DB while it is enabled. Does it properly create audit entries?
  • for the old edition of the component?
  • for the new edition?
• Metathesaurus editing actions
  • MetathesaurusContentEditingRest
    • methods for each "edit action"
    • Create a RestImpl
    • Create a client
    • Create integration tests to run against a "stock" dev  database
  • Add a semantic type component, Remove a semantic type component
    • Have a pencil icon by  the STYs section
    • clicking gives you a list of available STYs assigned, in tree order with a filter box for typing characters of the STY you want.
      • See the metadata "semantic type" option
    • User may want to choose multiple ones (so have a "finished" button)
    • Dont allow user to choose STYs already assigned to the concept.
    • Final action is to call "contentService.addSemanticTypeComponent"
    • Consider what happens to workflow status
    • Consider how to show "NEEDS_REVIEW" content in the browser
    • Consider how to support "Undo". - perhaps an action log (atomic/molecular) is a good idea still for that
  • Implement this completely including testing before moving on to other actions (each which requires a UI enhancement)
    • Approve a concept (e.g. set workflow status values).
    • Add an atom (e.g. MTH/PN - that needs to be generalized somehow)
    • Merge two concepts (consider the "workflow status "when this happens).
    • Move an atom (or atoms) from one concept to another
    • Split an atom (or atoms) out of a concept and specify a relationship type between the two concept
• Terminology Editing (first use case)
  • Add a concept (as a child of an existing concept) with one or more atoms and a PAR/CHD relationship.
  • Run the classifier
  • Show classifier results (e.g. new inferred relationships, etc)
  • NOTE: this only works with a description logic based source that tracks inferred relationships.
  • PREREQ: SNOMEDCT RF2 loader.

...