leaving identifier field blank?

39 views
Skip to first unread message

Emily Sommers

unread,
Feb 12, 2020, 3:59:53 PM2/12/20
to AtoM Users
Hi all,

Is it necessary to include an identifier at the top-level or can we leave it blank? Will this affect anything on the back-end in the database?

At my institution, our identifiers stem from accessions, rather than at the fonds level. When we implemented AtoM back in 2015, we were under the impression that we had to include an identifier for each record, so we arbitrarily gave each top-level description a number. But this has led to confusion amongst our users and I'm wondering if we can just go without, and have identifiers solely at lower-levels. We currently have the setting 'Inherit Reference Code' set to yes, because other institutions in our multi-repository instance do things a bit differently and like that setting.

Thanks,
Emily

Dan Gillean

unread,
Feb 12, 2020, 4:16:29 PM2/12/20
to ICA-AtoM Users
Hi Emily, 

You can certainly choose to leave the Identifier field blank if that better serves your local description and arrangement practices. 

AtoM is a very permissive system - we've intentionally made it this way because there are many cases where local practice differs from the exact requirements of international and national standards - often for very good reasons! Rather than making the fields that the relevant marks as Mandatory required, we have instead simply added warnings that appear on the view page for authenticated users when these fields are not populated. These warnings are never visible to public users. 

In fact, you can open a new blank record template in AtoM and hit save without adding any data at all, and AtoM will let you do it! 

A couple considerations as you make these changes: 

First, if your permalink settings are currently set to use the identifier or the reference code options for the slugs created when you save new descriptions, you'll want to reconsider this. Without an identifier to use, AtoM will instead generate a random alphanumeric string to use for the slug. I suggest testing this out with a draft record - remember if you need to manually edit the slug after creating a new record, you can use the Rename module on archival descriptions. See: 
Next, if you are using the sidebar treeview, make sure your sort options (in Admin > Settings > Treeview) are set to manual. The identifier and identifier-title options are buggy and I don't actually recommend that anyone use them until someone wants to sponsor a fix (it's more complicated than a simple bug fix, unfortunately), but the issue itself stems from the code trying to sort on identifier values, and what happens when it encounters records with no identifier. Essentially, your treeview can get caught in a weird loop showing the same handful of records over and over! If that happens, change the setting to manual, and have your IT team clear the application cache and restart services. If it persists, post a message here and I'll provide further suggestions for resolving it. 

Finally, I'm pretty sure that with reference code inheritance, if there is no top-level identifier it will still work, and will just build the reference code without that particular element. However I do suggest you do a quick test and confirm that it works as you need. It works fine in 2.4 and I can't think of anything changed in 2.5 or the upcoming 2.6 release that would alter this, but better to be safe than sorry!

Of course, you could always manually add the accession number as the identifier on your top-level descriptions, but I understand that this may not be desirable - you may want to keep the accession number private for security reasons, and it's more manual work! But just putting it out there as an option, in case the above does not work as you expect. 

Cheers, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056
@accesstomemory
he / him


--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/1ec8fa46-bc73-4e5b-a403-81cedacf1743%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages