kvuppala
commented
9 years ago The feature is rolled out in the June release, below is the screenshot of error message when the same identifier is used.
The unique identifier check is done in the agency/organization where the dataset is created, if any sub agencies are configured check is made across all sub agencies as well, however when a dataset is created in a sub agency the check doesnt include parent and other sibling agencies (for example Agency "A" has two Sub agencies with name "B" and "C", when a dataset is created in A the unique check in the UI is done across A, B and C, but the datasets created in agency B doesnt check against A & C, this is avoided as it could lead to slowness and multiple linking). But when the PDL/EDI json file is created, uniqueness check is done for all parent/child agencies configured, so if any missed during the UI will be caught at the json creation.
On the "Add Dataset" & "Update Dataset" (Manage/Edit Metadata) pages "Identifier" field should be verified for uniqueness across the agency datasets and all of its sub-agencies configured under the main agency, the check should be based on ajax approach without affecting the data entry of other fields.
On click of the "Next: Add Data" / "Update Dataset" button, an error message should be displayed that same Identifier can not be used for more than one dataset with in the agency and sub agencies configured, message should also have the dataset URL where the identifier is already being used.