...
- Support multiple, simultaneous editing of the same concepts for dual independent review, conflict identification, and conflict resolution.
- REST API for batch changes.
- Default export/release process for performing identifier assignment and generating releases in supported input formats.
- Support for subset (e.g. refset/value set) maintenance.
- Simple user interfaces for basic authoring tasks (adding synonyms, creating concepts, etc).
- Basic messaging/alert system for users to inform users of upcoming deadlines or release and the need to progress on work in certain ways (driven by automated criteria, or driven by management messages).
- Support for "simplified" editing, including insertion/maintenance/export processes for code systems including basic editing needs like adding/removing concepts, editing synonyms (or translations) and preferred names for concepts, and reconciling changes as underlying code systems are updated.
- Support attachments (at the project level).
- Support downloadable copies of the release file.
- Support simplified mappings between terminologies (either by relationship or by Mapping).
- Support note "attachments".
Future Development
- Support branch-and-merge "project" based editing to isolate, modularize, and package sets of work.
- Support for “dynamic” refset definitions and data.
- Support for sharding and a synchronization service (to support shadowing or distributed editing). Such a mechanism could also be used to synchronize IHTSDO editing changes with an extension-editing environment.
- Internationalization of error messages and labels. There’s a standard approach to this that will be undertaken once MVP is ready.
- Support for post coordinated expression maintenance and resusability.
- Support for template-based authoring.