Access to Memory (AtoM) is the software. AtoM is an open source web-based application for archival description, arrangement, and access.
Artefactual is a company. We are the lead developers and maintainers of AtoM. Because we give away our software and also license all related resources (like the documentation, etc) under open licenses as well, one of the ways we stay afloat is by offering paid additional services for those who want them - including hosting, training, data migrations, custom theming, and of course application development.
You can read more about the history of the AtoM project, the Artefactual business model, and how we maintain and develop new features for AtoM here:
I will follow-up with you in a separate message to provide more information about Artefactual's services. In the meantime, I will answer your questions about data export here, as they may be useful to the broader community.
AtoM supports the creation of a number of different entities - see:
Most of these entities have their own custom exports. However, many of these entities can be linked together (for example, adding a subject term as an access point to an archival description). When this is done, some of the linked entity may be included in another entity's export. For example, if you export an archival description that has an authority record linked as a creator and a subject term linked as an access point, the archival description export will include:
- The creator's name, and history (from the linked authority record)
- The authorized form of name of the linked subject term
It will not include other information that may be added to these entities directly - for example, the authority record identifier, alternative forms of name, etc. Similarly, any alternative labels, scope notes, or source notes added to the subject term will not be in the archival description export. To get this information, you would need to export the authority record and/or subjects separately.
Here is a list of the export formats currently supported in AtoM:
- Archival descriptions: CSV, EAD 2002 XML, DC XML, MODS XML
- Authority records: CSV, EAC-CPF XML
- Archival institutions: CSV
- Terms: SKOS RDF/XML
It's true that data for an archival description is stored across multiple different tables in the database, but it is all collated together in a consistent format on export. However, there are some entities that might be linked to AtoM that unfortunately do not currently have their own export format, and will not be included in the archival description export. One example would be the Rights module
. Rights can be added to descriptions, but don't currently have a means of being exported. Adding new functionality (such as new export code) requires community support for us to be able to implement - either from development sponsorship for us to do the work, or a community code contribution following our recommended contribution guidelines
The digital objects are also not included in an archival description CSV export - instead, a URL to the master digital object is included in the digitalObjectURI column of the export. I have outlined how you can use this value to get the actual storage path of the object in this previous forum thread:
And in this thread, I describe how objects are stored in AtoM in general:
Currently the only way to get ALL data out of AtoM at once is via a sqldump file, and copying the uploads directory.
As I mentioned, I will send you a separate personal email with more information on Artefactual's paid services.