Integrate automatic accession identifiers


I see that Hudson Molongolo already created a plug-in for generating accession identifiers. This would be an extremely helpful tool for my staff but my IT team is reluctant to rely on plug ins to customize the program out of a concern that future updates will break the system. I would like this plug in to be integrated into the main code and show up as a suggested Accession ID which can be overridden (autopopulating 2014-001, which would be deleted and replaced with something else) or a check mark option to implement within the system for Repository Managers.


Jason Loeffler
August 29, 2017, 7:19 PM

DevPri agrees to maintain this as a plugin.

Jason Loeffler
August 10, 2017, 7:32 PM

Kicking over to staff interface working group.

Lydia Tang
July 20, 2017, 5:37 PM

The problem I have is that there's no easy way to tell what accession IDs have already been used. I tend to guess around until something saves, or else open a new window to browse the existing accessions. Instead, currently the accession numbers suggest some of the existing numbers, but not all. What if that could be increased to autosuggest all of the existing numbers, or at least suggest similar numbers as the user types?

Jason Loeffler
June 27, 2017, 7:45 PM

This works pretty well as a plugin and seems like a lower priority. Tabling this for now. Should this be part of the staff user interface project? Perhaps this is something that could go out in a survey. Awaiting input from LT.

Won't Do
Your pinned fields
Click on the next to a field label to start pinning.




Lydia Tang