...
Sprint to extend some of the "read only" APIs, to finalize unit/integration testing for existing functionality, to extend the interface, to develop additional loaders, and to begin developing editing capabilities.
Priority things
- Video tutorial - 5 min walk through (e.g. "vet" - one for each - make a consistent script - put all on youtube and link back)
- User Preferences - borrow from refset - don't need anything specific yet, just infrastructure.
- Move "authorize" methods over from refset
- Borrow error handling from refset
- expand to use refset dailog directives for "errors" and warnings -requires a container
- For "semantic type" mechanism - if there are tree numbers, order by that and indent"
- BAC: OWL - NCIt
- BAC: remove "void addXXX" and "void removeXXX" methods from model objects. Use getObjects().add/remove(...) only
- Model
- Remove the "name" attributes on @XmlElement annotations and fix the javascript to properly handle the return values of services. TEST
- Mapping, MapRecord, MapEntry (each with attributes) - similar to Subset, SubsetMember except with one more layer.
- Then implement this for RRF loader
- Then implement this for RF2 loader (snapshot)
- Then implement this for RF2 loader (delta)
- User Interface
- Enable glass pane while switching tabs - need to say increment in tab controller and decrement at the end of the controller.
- Integration Tests - Jpa/REST - get them tested again
- For @IndexedEmbedded, make sure to use targetElement, also make sure that addXXX and setYYY are called ,and the service.addXXX and service.updateYYY calls are always made. Important for indexing to work properly.
Marketing/SEO
- Create a video demo of the site (camtasia) and post as a link on the header (video glyphicon if there is one)
- Verify all entry pages for applications are officially mobile friendly
- Consider advertising SNOMED/UMLS/ICD browsers on google adwords.
- Training Video for UMLS browser (need 10 min)
- Training Video for SNOMED browser (simple 5 min)
User Interface Enhancements
- Implement Diagramming
- 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
- instead of
- 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).
- Do something useful with websocket
- Expression-based searching (get harold's parser?)
- 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
...