...
- Add features for "deep" relationships when browsing UMLS.
- Need a generalized way to know when to use this
- it is definitely only for "concept"
- It may be that if any "atoms" of the concept don't match the terminology, then we show it.
- Reimplement the component report as a directive (with service callbacks for history and other features)
- 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?query=.....
- Also clean up the way routes work first so we have
- 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).
- DONE: Websocket (for a WebsocketWorkflowListener)
- test it
- What to do with it??
- Expression-based searching?
- Consider adding "LABELFOR" all subsets and making the star pop up a picklist of the things to highlight (ordered by type with extensions first, subsets later)
- RECURRING: Mobile-friendly and other style issues
...