...
- DONE: Double-check that all rest services always close the service (e.g. in "finally")
- Use Lucene SynonymFilter with synonym table
- DONE: SNOMED/RF2 Terminology subsetter
- DONE: Add "is inferred" and "is stated" to relationships, set in the loader
- DONE: Add "fully defined" to concept, set it in the loader.
- Change getSingleConcept -> branc
- DONE: Transitive closure computer - avoid cycles.
- ContentServiceRest
- DONE: findXXX methods for refset members
- find all refset members (by refset id)
- DONE: get all members for a concept/description
- DONE: getInverseRelationships(Concept)
- ***Integration testing for these. - need spreadsheet.
- DONE: findXXX methods for refset members
Handling effective time (new handler)
- Loaders should be allowed to set effective time
- release process should be allowed to set effective time
- want to be able to distinguish between published and unpublished things (perhaps a "published" flag is better)
Semantic search
- Support searching by hierarchy, by relationships, etc.
- Sparql end point? or expression language.
Project metadata service
- For Project (pull out of content service)
- for release info (pull out of history service)
PG Support running all admin tools through REST services
- Add additional rest calls (e.g. to action service or whatever)
- Add corresponding client calls.
- When adding a new project, have REST service set the "lastModifiedBy" to the user who authenticated.
Project-based authorization (e.g. only allow edits on concepts where a user is an author)
- This requires tracking the full concept scope with the project. (what if you add a concept?)
Application metadata service (project stuff?)
- Terminology Metadata service
- DONE Support classifier - root node (done), isa relationship (done), and role root.
- DONE stated/inferred char types should be metadata methods,
- Update TerminologyUtility accordingly to avoid hardcoded values
- new DL features for properties and data properties
- access to "RoleRelationship" objects
Security service - n/a
Content service methods for adding/removing inferred rels in batch.
- Separate read/write services of content service
- SNOMEDCT Editing Service
- HistoryService
- getRevisions (without boolean)
- getReleaseRevision(id, String release) - pick any one with matching release - get first one
- Configuration setting for synchronizing access to write services
- ContentService (and content change service) - have a "deep" delete on concept and description that deletes connected refset data too.
- REST layer
- Implement semantic search
- Implement everything across the board for Concept, Description, Language Refset, Relationship, and AssociationReference (e.g. reason for inactivation)
- Let the demo drive all use cases,
- READ only version of rest service
- Consider reorganizing snapshot loader to load concept-at-a-time.
- Parameterize the "active only" setting of RF2 file copier in the terminologyRf2Sampler.
Integration Testing
Mojo integration testing
Have a setup dev environment mojo
Have a teardown dev environment mojo (calls createdb at the end to clean up after itself, leavign an empty Db ready to go).
...