Page Comparison

...

• DONE (BC): Fix long error header - attach icon not showing, where it displays error is not in the error area.
• PG: Need to index atoms as lowercase string, punctuation replaced by whitespace, no trailing, duplicate, or leading whitespace.
  
  • Create a new tokenizer factory for this and define in @AnalyzerDefs in AbstractAtomClass
• PG: redo header/footer - controllers. (like refset tool)
• PG:  Implement Diagramming
  
  • model transformation
  • Show ONLY for "description logic terminology"
  • Enhancements to RRF preferred name computer
  • support multiple UMLS's - e.g. have a high-level terminology/version
  • reuse the same default precedence list.
• PG: Use directives for reports
  • Move all http calls to services.
• Use route params to dynamically load a "report" (and be able to bookmark URLs)
  • 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
• 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/report/cui/SNOMEDCT/2015_01_31/12738006
• 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"
• DSS: Model
  • Mapping, MapRecord, MapEntry (each with attributes) - 
    • similar to Subset, SubsetMember except with one more layer.
  • MapSet extends ComponentHasAttributes
    • name (String)
    • type (String)
    • fromTerminology/Version: String
    • toTerminology/Version: String
    • to/fromComplexity (String)
    • to/fromExhaustive (String)
    • get/setMappings -> use mappedFrom in @OneToMany
  • Mapping extends ComponentHasAttributes
    • fromTerminologyId, fromIdType
    • toTerminologyId, toIdType
    • mapSet
    • relationshipType, additionalRelationshipType
    • subsetId => group
    • rank
    • rule
    • restriction -> rename to 'advice'
    • In Jpa class
      • Add  @XmlTransient methods with @Field
      • getFromTermionlogy(), getFromVersion() - call getMapSet().getXXX
      • getToTermionlogy(), getToVersion() - call getMapSet().getXXX
  • Remove MapObject
  • ContentService - Jpa
    • add/remove/update MapSet/Mapping
    • getMapping(Long id)
    • getMapping(String terminologyid, terminology, version, branch)
    • findMappingsForMapSet(Long mapSetId, query, pfs)
    • findMappingsForConcept(Long conceptId, query, pfs)
      • call getConcept(conceptId).
      • then perform a "from" search based on the terminologyId, terminology, version, and idType (e.g. CONCEPT)
    • findMappingsForCode(Long codetId, query, pfs)
    • findMappingsForDescriptor(Long descriptorId, query, pfs)
  • REST layer
  • Integration tests
  • Loaders
    • Then implement this for RRF loader
    • Then implement this for RF2 loader (snapshot)
    • Then implement this for RF2 loader (delta)
  • Show mappings in UI.
• 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")

...