| Target release | 2.0 |
|---|
| Epic | |
|---|
| Document status | |
|---|
| Document owner | |
|---|
| Designer | Lead designer |
|---|
| Developers | |
|---|
| QA | Lead tester |
|---|
|
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
| JIRA Ticket | Notes |
|---|
| 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. | | 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. | | 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 |
|---|
| (e.g. How we make users more aware of this feature?) | Communicate the decision reached |
Not Doing
- List the features discussed which are out of scope or might be revisited in a later release.