| Feature Category | Criterion | AtoM | ArchivesSpace | |||
| Meta | Open Source | Yes | Yes | |||
| User Support | Yes- user base in google groups: | Membership allows access to technical support. | ||||
| Training & consultation | It doesn't offer training, but it allows consultations via e-mail or google groups | Yes, with membership | Training||||
| Technical documentation | Membership allows access to technical support. | |||||
| System Requirements | ||||||
| Backup/ restore utility | ||||||
| Hosting Available? | Yes, with fee | Yes, by Lyrasis, with fee: http://www.lyrasis.org/LYRASIS%20Digital/Pages/ArchivesSpace.aspx | ||||
| Demo/ Sandbox Available? | Yes | Yeshttp://demo.accesstomemory.org/ | ||||
| Migration support? | Yes, with fee | Membership provides migration tools from AT and Archon. Does membership would also support other migration sources? | ||||
| Importing/ Exporting Metadata | Exports MARC | No. Possible future release, but nothing official.No | Yes (MARC xml). Bugs reported that need to be fixed. | |||
| Exports EAD | Yes. Bugs identified when tested, also will have to be customized to our TARO EAD template | Yes. Bugs reported that need to be fixed. Also, it will need to be customized to our TARO EAD template | ||||
| Exports Dublin Core | Provides the functionality (not tested) | No | ||||
| Exports MODS | If the administrator has set the default archival description template to MODS, this will also appear as an export option (not tested) | No | ||||
| Exports METS | Exports MADS | No | Short-term development target: Extend METS exports to include file, rights, and event metadata | |||
| Exports MADS | No | No | ||||
| Exports EAC | Yes (not tested) | Yes (not tested) | ||||
| Exports SKOS | From the subjects and places modules (not tested) | No | ||||
| Batch Exports EAD | No documentation found | No documentation found | ||||
| Batch Exports MARC | No | No documentation found | ||||
| Batch Export Tab Delimited Files | No documentation found | No documentation found | ||||
| Imports EAD | Yes. Tested and there isn't a one to one match between our EAD template and AtoM fields. Would need to be customized | Yes, but bugs reported that need to be fixed. EAD import/export map: http://www.archivesspace.org/importexport | ||||
| Imports MARC | No | Yes (not tested) MARCXML import/export map: http://www.archivesspace.org/importexport | ||||
| Imports Tab Delimited Files/ CSV | Yes. AtoM provides a csv template for the import, but didn't work correctly when tested | Yes (not tested) | ||||
| Imports Digital Image Files | Yes; Digital Objects get embeded on the hyerarchical structure; formats supported: https://www.accesstomemory.org/en/docs/2.1/user-manual/import-export/upload-digital-object/#file-formats | Yes (not tested) Digital Object CSV map and template: http://www.archivesspace.org/importexport | ||||
| Import Accession Data | Yes. AtoM provides a csv template for the import, but didn't work correctly when tested | Yes, CSV only. Short-term development target: Create XML import for accession data Accession CSV map and template: http://www.archivesspace.org/importexport | ||||
| Batch Import EAD | Yes (not tested) | Yes (not tested) | ||||
| Batch Import MARC | No | No documentation found | ||||
| Batch Import CSV | Yes (not tested) | Yes (not tested) | ||||
| Collection Management | Appraisals | |||||
| Accessions | Managed on their own module | Managed on their own module | ||||
| Create Deeds of Gift | No documentation found | No documentation found | ||||
| Prioritize Processing Order | Yes, and also indicate the processing status | Yes, and also indicate the processing status | ||||
| Track Donors | Donors are managed on their own module | No documentation found | ||||
| Project Management | Some fields for project management on Accessions module | Looks like it can be done from the Accessions module and the Resource module | ||||
| Record Condition | No specific area | On the accessions module | ||||
| Manage Locations | Physical storage managed on its own module | Yale is developing new features on the locations module, will have to see if it meets our needs | ||||
| Manage Restricted Materials | No documentation found | Restricted material is marked, and it allows to narrow search | ||||
| Manage Rights | Right holders are managed on its own module | Yes | ||||
| Manage Loans & Exhibits | No documentation found | Yes, from the locations module | ||||
| Separations | Destructions | From the Archival Descriptions and the accession record | "Disposition" field in Accession record, and "Separated material" in Resource record | |||
| Destructions | From the Archival Descriptions and the accession record | |||||
| De-Accessioning | A de-accession can be done directly from the accession record | From the Archival Descriptions and the accession record | ||||
| Reference Support | No documentation found | No documentation found | ||||
| Generate Reports | Reports for file lists, item lists, physical storage locations and box labels | Short term development target: Implement a reporting module that will enable archivists to modify and save default reports, to create new reports, and to share reports Define many default reports, including some replicating and updating reports in the Archivists’ Toolkit and new reports for new modules and functions in ArchivesSpace | ||||
| Track Repository Statistics | No documentation found | No documentation found | ||||
| Resource Description | TARO and OCLC ID# | Yes. Supports multiple unit ID's. | ||||
| Authority Control | Authorities managed on their own module EAC-CPF | Authorities managed on their own module EAC-CPF | ||||
| Controlled vocabulary | Subjects and Places managed on their own module | Subjects (including places) managed on their own module | ||||
| Compliance to Archival Standards | ICA standards, DACS, RAD, Dublin Core, MODS | |||||
| Data Validation | ||||||
| Templating / Default Fields | Yes | Yes | ||||
| Support for Digital Media | ||||||
| Internationalization | Multilingual options | Multilingual? | ||||
| Flexibility of Data Model | Yes | Yes | ||||
| Item-level Description | Yes | Yes | ||||
| Reorganize Hierarchies | Yes. Needs to be done directly from the item level | Yes | ||||
| Dynamically generate EAD finding aids | ||||||
| Publish finding aids online | Yes, with public interface. | Yes, with public interface. | ||||
| TARO EAD preview or internal validation | No. Would still require Oxygen for preview. | Can export unpublished finding aids as pdf from sandbox, though since it doesn't have the TARO style sheet it looks different from a TARO preview. | ||||
| Administrative Functions | User Permissions | |||||
| Support for Harvesting/ Syndication | ||||||
| Customization / Configuration | ||||||
| Spell Check | ||||||
| Bug Reporting | ||||||
| Interoperability with Digital Repository Systems | ||||||
| Multi-repository support? | Yes and no. Some limited functionality. | Yes (not tested) | ||||
| User Interface | Web Publishing | |||||
| Browse | Search | Archival Descriptions, Authorities, Archival Institutions, subjects, places, digital objects and functions | Accessions, Resources, Digital Objects, Subjects, Agents, Locations, Events, Collection, Clasification | |||
| Search | Gobal or by repository | Yes | ||||
| Advanced Search | Yes | Yes | ||||
| Customizable | Yes. In-house or supported with fee | Yes. In-house or supported with fee (only members) | ||||
| Built-in Help | Pop up notes referring to DACS rules; should be customizable to in-house interpretation of the rules | Yes. With membership; also, pop up notes referring to DACS rules; should be customizable to in-house interpretation of the rules | ||||
| Link to Images & Other Files | Yes | |||||
| Easy Data Entry | Interface somewhat clunky for data entry. | Data entry is kind of similar to AtoM. Rapid data entry option does alleviate somewhat. | ||||
| Repositories we have contacted |
Google hangout session: 2014-10-29 Meeting notes ADWG |
|
Page Comparison
Manage space
Manage content
Integrations