| Requirement | Notes |
|---|
| Each content request task, generated through CRS, will be associated to one authoring task. | This will be done via staff assigning a CRS request to an authoring task through CRS or possible JIRA to start with |
| Each authoring task may be associated with many requests and have multiple SCT content changes | An authoring task may not be associated to a content request as well. |
| Reports should be able to show what has changed within an authoring task once it has been promoted | Any content which is changed should be logged on each status change in a traceability datasource using (at a minimum): - changeactivity id (system generated id)
- sct id
- task id
- author id
- date modified
See the technical design below |
| When a project is promoted, the information all the authoring tasks being promoted, along with the content changed on each task, should be available for reporting | Linked to the above... this would be a status change |
| At each status change of an authoring task, any associated CRS task should be updated appropriately | This is linked to the requirement from CRS below & | Jira |
|---|
| showSummary | false |
|---|
| server | jira.ihtsdotools.org JIRA |
|---|
| serverId | b202d822-d767-33be-b234-fec5accd5d8c |
|---|
| key | CRS-23 |
|---|
|
|
| By having a track of content being worked on in authoring tasks, authors should be able to see if content they wish to edit/maintain is already being worked on by another author | This will likely end up in a screen (somewhere) which queries the 'traceability' db against a given SCT ID |
| If a request | |