Content Comparison

...

• DONE PG: redo header/footer - controllers. (like refset tool)
• PG:  Implement Diagramming
  
  • model transformation
  • Show ONLY for "description logic terminology"
• PG DONE 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")
  • REMAINING: Update integration tests with actual filter values (currently only tests null values)
• Enhancements to RRF preferred name computer
  • support multiple UMLS's - e.g. have a high-level terminology/version
  • reuse the same default precedence list.
• DONE PG: Use directives for reports
  • DONE Component Report
    • treeComponent
    • semanticTypes
    • definitions
    • atoms
    • attributes
    • subsets
    • relationships
    • deep relationships
      • TODO Relationships and deep relationships are not using callback functions, fix this
  • DONE Search Result Tree directive
• DONE PG Fixed Infinite cycle digest errors on uib-tooltip-html for refset labels in tree search results (extension highlighting)
• DSS; Project/User/UserPrefs stuff
  • User
    • Application role
    • user preferences
    • projectRoleMap (e.g. and project role map adapter)
  • Project
    • Remove "leads", "authors", "administrators"
    • remove "scope" stuff
    • Remove actionWorkflowStatusValues
    • userRoleMap (and userRoleMapAdapter)
  • Bring over UserRole from Refset -> replace term server stuff
  • Align Security Service Rest (and Jpa)
    • Bring over methods from refset that are missing
    • Reconcile differences in the implementation methods.
  • ProjectService Rest (and Jpa)
    • Remove the scope concept calculation
    • Add stuff about user/project (assign,unassign,find...)
  • next step: add an "Admin" tab.
    • basically borrow from refset and make work for this project.
• PG Use route params to dynamically load a "report" (and be able to bookmark URLs)
  
  • DONE EXCEPT SERVER CONFIG Implement routing for terminologyId/terminology/version/type so we can preserve URLs.  can even include ?query=... for the query
    • Also clean up the way routes work first so we have
      • https://umls.terminology.tools/content
      • instead of
        • https://umls.terminology.tools/#/content
      • This is likely related to the starting URL redirected to https://umls.terminology.tools/#/
      • See http://stackoverflow.com/questions/14319967/angularjs-routing-without-the-hash
      • e.g. https://umls.terminology.tools/content/CUI/SNOMEDCT/2015_01_31/12738006
• DONE Support opening a concept in a new window (e.g. there's a pointing off arrow icon that opens a new window with a routing URL that  shows exactly that concept - then drag/drop between windows can be editing mechanism).
  • https://umls.terminology.tools/content/simple/cui/SNOMEDCT/2015_01_31/12738006
  • Improvement: Fix header offset in simple report
• User Preferences stuff
  • Bring over model from Refset tool.
  • Add "last query" (e.g. "brain" and whether it's "list" or "tree" mode).
  • Add "last report" (e.g. type/ui/terminology/version)
• Remove "void addXXX" and "void removeXXX" methods from model objects. Use getObjects().add/remove(...) only
  • e.g. AtomClass doesn't need addAtom or removeAtom
  • Rewire any uses of them  
  • "addXXX" -> "getXXX().add"
  • "removeXXX" -> "getXXX().remove"
  • same if there is "clear"
• DONE Show concept and atom-level subset information (e.g. language refset entires in SNOMED. may require a change to the graph resolver).
  • DefaultGraphResolver now resolves subset members for both Atom and Concept
  • Confirm that Descriptor and Code are not intended to have subset members
  • Needs testing to confirm UI display ok

...

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

...