| ITI57 | ITI57-001 | reviewed | Testable |
1
|
1
| | An Update Document Set Request message is an ebRS SubmitObjectsRequest containing ebRIM formatted metadata | 19 | Section 3.57.4.1.2 | 8/28/19 11:51:09 AM by ycadoret |
|
| ITI57 | ITI57-002 | reviewed | Testable |
1
|
1
| | ITI TF-3: Table 4.3.1-3 details the requirements on metadata attributes for each actor submitting metadata | 19 | Section 3.57.4.1.2 | 8/28/19 11:53:20 AM by ycadoret |
|
| ITI57 | ITI57-003 | reviewed | Testable |
1
|
1
| | The receiving actor shall be able to manage the following attributes on DocumentEntry, Folder, and Association objects: logicalID version availabilityStatus, which require special handling dictated by metadata update | 20 | Section 3.57.4.1.3 | 9/17/19 11:30:06 AM by aeschlimann |
|
| ITI57 | ITI57-004 | reviewed | Testable |
1
|
1
| | The receiving actor SHALL be capable of storing multiple versions of DocumentEntry and Folder metadata objects | 20 | Section 3.57.4.1.3 | 8/28/19 5:31:50 PM by ycadoret |
|
| ITI57 | ITI57-005 | reviewed | Testable |
1
|
1
| | A Document Registry then it shall make stored versions of DocumentEntry and Folder metadata objects available through the Registry Stored Query [ITI-18] transaction | 20 | Section 3.57.4.1.3 | 9/17/19 11:29:59 AM by aeschlimann |
|
| ITI57 | ITI57-006 | reviewed | Testable |
1
|
1
| | An Update Document Set [ITI-57] request SHALL include a SubmissionSet object | 20 | Section 3.57.4.1.3.1 | 8/28/19 11:53:32 AM by ycadoret |
|
| ITI57 | ITI57-007 | reviewed | Testable |
1
|
1
| | An Update Document Set request [ITI-57] shall not include initial versions of DocumentEntry or Folder objects. In a request, initial versions are recognized by having entryUUID = logicalID or logicalID missing | 20 | Section 3.57.4.1.3.1 | 8/28/19 11:53:40 AM by ycadoret |
|
| ITI57 | ITI57-008 | reviewed | Testable |
1
|
1
| | An updated version of a DocumentEntry object, when included in an Update Document Set request [ITI-57], SHALL be a complete DocumentEntry object. Individual attributes cannot be submitted alone | 21 | Section 3.57.4.1.3.1 | 8/28/19 11:53:59 AM by ycadoret |
|
| ITI57 | ITI57-009 | reviewed | Testable |
1
|
1
| | An updated version of a Folder object, when included in an Update Document Set request [ITI-57], shall be a complete Folder object. Individual attributes cannot be submitted alone | 21 | Section 3.57.4.1.3.1 | 8/28/19 11:54:07 AM by ycadoret |
|
| ITI57 | ITI57-010 | reviewed | Testable |
1
|
1
| | All metadata objects in an Update Document Set Request [ITI-57] message shall have an entryUUID (id) attribute | 21 | Section 3.57.4.1.3.1 | 8/28/19 11:54:12 AM by ycadoret |
|
| ITI57 | ITI57-011 | reviewed | Testable |
1
|
1
| | Metadata objects entryUUID (id) attribute MAY be coded as a UUID or symbolic nam | 21 | Section 3.57.4.1.3.1 | 8/28/19 11:54:28 AM by ycadoret |
|
| ITI57 | ITI57-012 | reviewed | Testable |
1
|
1
| | Metadata objects entryUUID (id) attribute SHALL be used by the receiving actor when reporting errors | 21 | Section 3.57.4.1.3.1 | 8/28/19 5:29:07 PM by ycadoret |
|
| ITI57 | ITI57-013 | reviewed | Testable |
1
|
1
| | The submission of metadata objects: DocumentEntries, Folders, Associations; in the support of metadata versioning follows the same rules as defined for the Register Document Set-b [ITI-42] transaction or Provide and Register Document Set-b [ITI-41] transaction. These rules are defined in ITI TF-3: 4.2 and 4.3 | 21 | Section 3.57.4.1.3.1 | 8/28/19 5:32:19 PM by ycadoret |
|
| ITI57 | ITI57-014 | reviewed | Testable |
1
|
1
| | A single Update Document Set transaction MAY contain both an Update DocumentEntry Metadata operation and an Update DocumentEntry Status operation targeting the same logical DocumentEntry. | 21 | Section 3.57.4.1.3.1 | 8/28/19 11:55:15 AM by ycadoret |
|
| ITI57 | ITI57-015 | reviewed | Testable |
1
|
1
| | When a single Update Document Set transaction contains both an Update DocumentEntry Metadata operation and an Update DocumentEntry Status operation targeting the same logical DocumentEntry, the Document Registry or Document Recipient SHALL create the new DocumentEntry version and then apply the new availablityStatus value to this new version. The previous version, the one present before the processing of this transaction began, SHALL not be modified | 21 | Section 3.57.4.1.3.1 | 8/28/19 5:28:48 PM by ycadoret |
|
| ITI57 | ITI57-016 | reviewed | Testable |
1
|
1
| | A single Update Document Set transaction MAY contain both an Update Folder Metadata operation and an Update Folder Status operation targeting the same logical Folder | 21 | Section 3.57.4.1.3.1 | 8/28/19 11:55:33 AM by ycadoret |
|
| ITI57 | ITI57-017 | reviewed | Testable |
1
|
1
| | When a single Update Document Set transaction contains both an Update Folder Metadata operation and an Update Folder Status operation targeting the same logical Folder, the Document Registry or Document Recipient SHALL create the new Folder version and apply the new availablityStatus value to this new version | 21 | Section 3.57.4.1.3.1 | 8/28/19 5:25:46 PM by ycadoret |
|
| ITI57 | ITI57-018 | reviewed | Testable |
1
|
1
| | A single Update Document Set transaction SHALL not contain multiple Update (DocumentEntry or Folder) Metadata operations targeting the same logical object | 21 | Section 3.57.4.1.3.1 | 8/28/19 11:56:03 AM by ycadoret |
|
| ITI57 | ITI57-019 | reviewed | Testable |
1
|
1
| | A single Update Document Set transaction SHALL not contain multiple Update (DocumentEntry or Folder or Association) Status operations targeting the same logical object | 21 | Section 3.57.4.1.3.1 | 8/28/19 11:56:13 AM by ycadoret |
|
| ITI57 | ITI57-020 | reviewed | Testable |
1
|
1
| | At any point in time there SHALL be at most one version of a logical DocumentEntry object with status Approved in the registry/recipient. If this version exists it shall always be the most recent version | 21 | Section 3.57.4.1.3.1 | 9/17/19 11:29:47 AM by aeschlimann |
|