#29: Identify Duplicate Records
User Story Description:
Duplicate identification is on two levels:
Duplicate records should be identified within a file submission.
Prevent Duplicate form submissions based on a specific “primary key” field or group of fields. Example: An operator will submit the Q2 form. Then another operator from the same site will submit (this could be externalized to custom validation).
Business Rationale:
To ensure data integrity/quality when uploading a file.
Priority (MoSCoW): Could Have
This duplication check could be done at a later stage outside of CHEFS.
Dependencies:
[List potential dependencies with other User Stories or Tasks]
# | Task or User Story | Type of Dependency |
28 | https://bcdevex.atlassian.net/wiki/spaces/CCP/pages/1004863489 | Parent |
|
|
|
|
|
|
|
|
|
Technical Details:
Custom feature.
Acceptance Criteria:
[List the Acceptance Criteria]
# | Description | Notes |
1 |
|
|
2 |
|
|
3 |
|
|
4 |
|
|
5 |
|
|
Prototype/Mockups
Provide high fidelity prototype or mockup
Out of Scope:
Contact(s):
Table of Contents