Validate and enforce the uniqueness of accession identifiers
|Category:||Accessions||Estimated time:||10.00 hours|
|Target version:||Release 2.4.0|
|Google Code Legacy ID:||Tested version:|
To ensure unique values are maintained even when a user manually edits the accession number or disables the mask and uses a number of their choosing, we will validate the data against accession IDs already in use, prior to saving. If a number is found not to be unique, the user will be given a notification, and any data entered into the edit page will be preserved, so the user can modify the accession number until an acceptable, unique value has been entered. This will involve:
- If the value is not unique, stay on the edit page so no other data is lost, and inform the user
#7 Updated by Jesús García Crespo about 4 years ago
- Status changed from New to QA/Review
- Assignee changed from Mike Cantelon to Dan Gillean
#8 Updated by Dan Gillean about 4 years ago
- File accession-number.png added
- Status changed from QA/Review to Feedback
- Assignee changed from Dan Gillean to Mike Cantelon
Testing this on qa/2.4.x branch....
See attached image - was never given any warning about using the exact same accession number. In the UI, was able to create identical ones... however, I noticed that internally (at least, going by the slug), it actually bumped me ahead to the next available accession number... but I was never warned. Record saved immediately.
#9 Updated by Dan Gillean about 4 years ago
HMMMMMMM very weird. I tried to repeat this one more time, and THEN I saw the JS warning in action. I appreciated that the create button was disabled as well. so..... it works? But i'm still confused why i was able to create a duplicate the first time around.
First time I had the accession mask setting turned on, but still edited the value. Second time, I had it turned off. Going to test a bit more and see if that's it, tomorrow.
#12 Updated by Dan Gillean almost 3 years ago
- Assignee deleted (
- Requires documentation deleted (
Documentation updated in 2.4 branch in https://github.com/artefactual/atom-docs/commit/05c3e11ae9db1328ee916e3dfbb5e29d0be36120