ArchivesSpace re-org and committer groups proposal
How to Report a Bug
How to Request a New Feature
How to Contribute Code or Documentation
How to Participate in Community Release Testing (forthcoming)
Creating User Screencasts
Are you working on an integration with ArchivesSpace? If so, please fill out our ArchivesSpace Integrations Information form so that we can learn more about it. Once submitted, the Integrations sub-team of the Technical Advisory Committee will discuss your work during one of our monthly calls and get it on this page.
A functional coupling between ArchivesSpace and another software application to act as a coordinated whole. Regardless of the complexity of a particular integration (see Tiers), a defining characteristic of all integrations is communication, or seamless data flow--without a manual, intermediary step--between systems. For our purposes, an integration should also be generalizable for the ArchivesSpace community.
The highest level of integration, this level of integration includes data flowing into and out of the integrated systems and would require changes to the ArchivesSpace core code to work, a change in the ArchivesSpace data model, or significant migration of legacy data existing in the system. Currently there are no examples of tier 1 integrations.
The is middle level of an integration. This level may require adding and initializing a plugin in your local ArchivesSpace repository, but no changes to the core code or database. Some examples of this level of integration include the Bentley’s work with Archivematica, the Rockefeller Archive Center’s work with Archivematica, and the current Preservica-ArchivesSpace integration. These integrations involve leveraging the ArchivesSpace API to allow another system to create description in ArchivesSpace, and data flows both into and out of the system. For example, you can view ArchivesSpace components in Archivematica and then use Archivematica to write to ArchivesSpace.
This level merely pulls information for possible inclusion into ArchivesSpace or another system. No data model changes are necessary, and generally no new description is created in ArchivesSpace. In this tier 3, data is either pushed or pulled from one system only, and no writing to either system happens. An example of this would be the ArchivesSpace to Drupal integration created by the American Academy in Rome.
ArchivesSpace-Archivematica-DSpace Workflow Integration
|Bentley Historical Library||On Github||Coming soon!|
|Rockefeller Archive Center||On Github||Coming soon!||In-progress||2|
|Yale University||Proprietary||Coming soon!||In-progress|
|American Academy in Rome||Coming soon!||Coming soon!||In-progress||3|
|Hillel Arnold||On Github||On Github||In-progress||3|
|Litchfield Historical Society||Coming soon!||Coming soon!||In-progress||3|
|Caltech Archives Integration Tools||Caltech Library||On Github||On Github||In-progress||Other Community Projects|
|EADChecker||Harvard Library||Allows archivists to check whether there are issues with their finding aid that would prevent it from ingesting correctly into ArchivesSpace.||On Github||On Github||Completed!||Other Community Projects|
|ArchivesSpace Preprocessor||Harvard Library||A preprocessor which can run over a large corpus, find and track problems in EAD, and produce amended EAD files to be ingested into ArchivesSpace.||On Github||On Github||In-progress||Other Community Projects|