Skip to first unread message
Lisa Lawlis
Mar 19, 2024, 8:47:29 AMMar 19
to AtoM Users
Hello!
I'm a new AtoM user and working on a project that I need examples of metadata in archival management systems.
I was wondering if anyone knew where I could get an example of a front facing/record description from an OPAC and the corresponding metadata export in XML (or whatever metadata format AtoM uses to display the record metadata on an OPAC)? Happy for any advice!
Thank you,
Lisa Lawlis
Assistant Archivist
Western University
Dan Gillean
Mar 19, 2024, 9:06:19 AMMar 19
to ica-ato...@googlegroups.com
Hi Lisa,
You can grab some XML exports from our public demo site if that will serve.
As an archival management system and not a library catalogue, I am assuming by OPAC you mean AtoM's public-facing front end (which public researchers would use as the catalogue for hosting archives).... if so, you can find that here:
If you want to log in and play around (though that shouldn't be needed to browse and export some XML), the login credentials are listed on the homepage. Be aware that this is a public facing demo site, meaning:
- Other people can and will login and change things - including changing the login credentials
- The site and all its example data resets every hour, so any changes will be undone. Feel free to try out modifications as you see fit, and if for some reason you can't log in with the provided credentials (i.e. someone changed them), just know it will all reset at the top of the hour
- For security purposes, all upload functionality is disabled
Here is an example of a good archival unit with a decent multi-level hierarchy:
Export options for DC XML and EAD 2002 XML are listed in the right-hand sidebar. Here are some direct links to the output:
Note that for Dublin Core, we only provide import/export support for the basic DC Elements (what colloquially sometimes gets called "DC simple"), and DC exports also only export the current record, not the entire hierarchy, as you will find with the EAD export.
You'll find our XML export documentation here:
AtoM also supports CSV export. To export this same fonds as a CSV, you would want to pin it to the clipboard (the paperclip icon in the sidebar), then navigate to the clipboard (click the paperclip icon in the header, select "Go to clipboard", and configure your export from there to include all levels of description. AtoM will generate a download link for you when the CSV is ready (just keep navigating the site and/or reload the page after a moment). More information in our docs:
Finally, if you would like to try this on a live AtoM site being used in production instead of our demo site, you can find a list of publicly accessible example AtoM sites on our wiki, here:
Let us know if you need anything else!
Cheers,
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/936995fa-3b6f-4e47-9d15-ffcec226debfn%40googlegroups.com.
Lisa Lawlis
Mar 23, 2024, 12:57:55 PMMar 23
to AtoM Users
Hi Dan!
Thank you so much for your message - sorry for the late reply!
Yes - OPAC as in the front end/public facing side of AtoM.
Thank you for the link to the demo site - I totally forgot you can download the metadata out of the record (after signing in) that is perfect - thank you!
Thank you for the links to the examples - those help a lot!
Why are the export options EAD and DC (sorry stupid question!) - what metadata talks with records processed by Archivematica/stored by Permafrost? I guess what metadata from AtoM (i.e. is it the EAD metadata) that talks (or does it talk with) Archivematica and/or Permafrost? Just curious how those platforms share metadata!
Thank you so much for your help! Greatly appreciated - I'm totally new to AtoM!
Best,
Lisa
Dan Gillean
Mar 25, 2024, 8:37:19 AMMar 25
to ica-ato...@googlegroups.com
Hi Lisa,
Why are the export options EAD and DC (sorry stupid question!) - what metadata talks with records processed by Archivematica/stored by Permafrost? I guess what metadata from AtoM (i.e. is it the EAD metadata) that talks (or does it talk with) Archivematica and/or Permafrost? Just curious how those platforms share metadata!
At the moment, the amount of descriptive metadata that is shared with AtoM following a DIP upload is rather limited. Right now, uploading a DIP from Archivematica to AtoM will create a target description, and append all digital objects in the DIP as stub child records to that target description. If there is DC XML that has been added to the transfer correctly so it ends up in the METS of the resulting AIP that Archivematica makes, then it will be written to the parent description that is created - there is a mapping as to what fields are supported here:
You can use Archivematica's Appraisal tab to do some arrangement first, potentially defining different levels of description, adding intermediary levels, etc. See:
Otherwise, most of the metadata captured by Archivematica is technical, administrative, and preservation metadata. Some of this technical metadata will be sent to AtoM as well, about the various digital objects included in the DIP - and even information about the original objects from which the DIP objects were derived. These will be displayed in AtoM's existing Digital object metadata area on upload. See:
AtoM administrators can control the visibility of digital object technical metadata to public users via the Visible elements module. See:
As to why EAD and DC for export options?
For XML, EAD is the most comprehensive XML-based metadata exchange standard for archival descriptive metadata, so it's the option that will best capture all your descriptive data on export. DC support is added because EAD, while widely used in the archival profession, is rarely used outside of it - so if users are intending to send / use data in other GLAM institution portals / sites / catalogs / tools (such as a library special collection portal, perhaps), these third-party tools are more likely to support Dublin Core than EAD.
AtoM also supports MODS 3.5 XML, another descriptive XML-based metadata exchange standard used more commonly in libraries and related institutions than archives - here is an example MODS record from the demo site:
It is similar to the DC XML, in that it does not include mappings for all available AtoM description fields, and will only export 1 record at a time (using links to point to parent or child records, but not including them in the export), unlike EAD, which can include an entire archival hierarchy.
MODS and DC were both originally added early on in the project's history, as part of an early attempt to build a sort of distribution of ICA-AToM more useful to llbraries with special collections. IT was the result of a partnership with Canadiana and some other institutions, and was pitched as the "Digital Collections Builder" - but really it was just AtoM with a different theme and some new features added. You can read about the project's history on our wiki, here:
Hope this helps!
Cheers,
he / him
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/fcbb04ce-e71e-4529-b758-2e42c0e1e760n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages