Resource identifiers must be unique within a scheme and enforced by the hub.
Alpha comments: Duplicate checking on identifiers e.g. transferID is a requirement of the specification. Checks must be made by the hub on all incoming client chosen resource identifiers to ensure no duplicates are introduced to schemes. This has to be since the beginning of scheme time.
Beta comments: Some code comments added but no concrete implementation since alpha.
Acceptance Criteria
The hub must implement duplicate checking on all incoming client-chosen resource identifiers, such as transferID, as per the specification.
Duplicate checking must be implemented from the beginning of scheme time, ensuring that all historical and future resource identifiers are checked for duplicates.
Any duplicate resource identifiers found during the checking process must be flagged and appropriately handled according to the system's error handling procedures.
The system must log all instances of duplicate resource identifiers detected during the checking process for audit and troubleshooting purposes.
The system should provide feedback to clients when a duplicate resource identifier is detected, indicating the reason for rejection and any corrective actions required.
Background
Resource identifiers must be unique within a scheme and enforced by the hub.
Alpha comments: Duplicate checking on identifiers e.g. transferID is a requirement of the specification. Checks must be made by the hub on all incoming client chosen resource identifiers to ensure no duplicates are introduced to schemes. This has to be since the beginning of scheme time. Beta comments: Some code comments added but no concrete implementation since alpha.
Acceptance Criteria