Convert Rights » Statute into an autocomplete field and add new Statute taxonomy to AtoM to store values
|Assignee:||Dan Gillean||% Done:|
|Target version:||Release 2.3.0|
|Google Code Legacy ID:||Tested version:|
This feature is being added to improve the workflow for users adding PREMIS rights statements to archival descriptions. Because statutes are formal legal entities with standardized names, users making use of the PREMIS rights to add statute-based rights statements will often have to repeat the same citation, thereby introducing the risk of input error (typos, accidental variations, etc) as the same statutes are repeated.
This feature proposes to turn the Statute Citation field, in the PREMIS Rights template (visible when Statute has been selected as the Basis) into an autocomplete field, linked to a taxonomy accessible via Manage > Taxonomies. Like most autocompletes in AtoM, users can choose existing terms or add new ones.
We will not pre-populate the taxonomy with existing values, because statutes vary widely based on jurisdiction. We will include a migration script that will convert existing string values to taxonomy terms.
Finally, as part of the work on this feature, we hope to improve the usability of the AtoM autocomplete fields, to make it easier to tell when a new term is created, and more difficult to create accidental duplicate records. While the work on this feature does not cover adding this improved auto-complete everywhere in AtoM, it will allow us to slowly roll it out throughout the application.
#4 Updated by Dan Gillean almost 7 years ago
- Subject changed from Convert Rights » Statute into an autocomplete field to Convert Rights » Statute into an autocomplete field and add new Statute taxonomy to AtoM to store values
Deleted separate issue about the taxonomy, already described in this feature ticket. Edited title to better reflect this.
#11 Updated by Jesús García Crespo almost 7 years ago
I've done some tweaks in autocomplete.js that make creating duplicates harder, but there is still a related issue where a duplicate will be created if you type a new entry that has a match in the database but you finish typing before the server responds with the suggested options. For this particular case I think that we are going to rethink the way that we are adding new values in the server and consider to do all the changes including the submission of the form within one transaction, but that would be a major refactor.