Goals
- To enhance the current component identifier service
Background and strategic fit
This is needed to provide a scalable service which will provide a single source of truth for SCT component identifiers, accessible by other organisations to be used as part of their existing release processes.
Assumptions
- All of the existing functionality, and any relevant data, will need to be migrated
Requirements
| JIRA Ticket | Notes | |
|---|---|---|
| 1 |
CIS-1 - Getting issue details... STATUS |
A new REST endpoint, and simple web form, is needed to provide a simple and quick way for other systems or users to check the validity of a given SCT ID. |
| 2 |
CIS-2 - Getting issue details... STATUS |
Whilst there is a basic Namespace, an enhancement is to provide a public facing namespace registry, including an anonymous view/page of all namespaces registered in the system. |
| 3 |
CIS-3 - Getting issue details... STATUS |
Use user groups as permissions for access to namespaces instead of usernames. |
Questions
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|---|