Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 .Please keep in mind that we’ve defined integration as:and get it on this page.

Integrations Defined

...

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.

...

.

Tiers

Tier 1

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.

Tier 2

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.

Tier 3

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.

Digital Preservation Integrations

SystemName of IntegrationOrganizationObjective

Additional Information

StatusTier
CodeDocumentationOther

ArchivematicaImage Modified

ArchivesSpace-Archivematica-DSpace Workflow IntegrationBentley Historical Library
  • Introduce functionality into Archivematica that will permit users to review, appraise, deaccession and arrange content in a new "Appraisal and Arrangement" tab in the system dashboard.
  • Load (and create) ArchivesSpace archival object records in the Archivematica "Appraisal and Arrangement" tab and then drag and drop content onto the appropriate archival objects to define Submission Information Packages (SIPs) that will in turn be described as 'digital objects' in ArchivesSpace and deposited as discrete 'items' in DSpace.
  • Create new archival object and digital object records in ArchivesSpace and associate the latter with DSpace handles to provide URIs/'href' values for <dao> elements in exported EADs.
On GithubComing soon!

In-progress

2

ArchivematicaImage Modified

ArchivesSpace-ArchivematicaRockefeller Archive Center
  • Introduce functionality into Archivematica that will let users pair digital objects to ArchivesSpace resources/components and automatically generate Digital Objects in AS based on the digital objects.
  • Create Access/Restrict notes based on PREMIS information entered into Archivematica.
  • Automatically pair digital objects to ArchivesSpace resources/components through matching digital filenames and AS ref_ids.
On GithubComing soon!
In-progress2

PreservicaImage Modified

Preservica-ArchivesSpace IntegrationYale University
  • Introduce functionality into Preservica to manage ingested content according to ArchivesSpace record hierarchies, linked through ArchivesSpace ref_ids.
  • Create linked ArchivesSpace digital records records for materials ingested into Preservica.
  • Enable synchronization of metadata between ArchivesSpace and Preservica for preservation purposes.
ProprietaryComing soon!In-progress

Content Publication Integrations

SystemName of IntegrationOrganizationObjective

Additional Information

StatusTier
CodeDocumentationOther

DrupalImage Modified

ArchivesSpace-to-DrupalAmerican Academy in Rome
  • Using currently available contributed and custom Drupal modules, this project will provide a mechanism to periodically poll the ArchivesSpace REST interface for newly created and changed archival and digital objects. 
  • Currently, the project uses cURL HTTP (chr), Web Service Data (wsdata), and some glue code to pipe ArchivesSpace-provided JSON formatted objects into Drupal entities. These entities can be formatted, manipulated, and indexed via traditional Drupal methods (Views, Solr, Elastic Search, etc.).
  • Future releases will replace cURL HTTP and Web Service Data with custom Guzzle component requests.
  • There are plans to provide a turnkey Drupal distribution and Docker container (possibly bundled with ArchivesSpace) to support the activities of smaller organizations with limited technical staff and funding.

Coming soon!Coming soon!
In-progress3

Image Modified

staticAidHillel Arnold
  • Jekyll static site generator for archival description serialized in JSON, generated via the ArchivesSpace REST API
On GithubOn GithubIn-progress3

Image Modified

ArchivesSpace/CollectionSpace Search/Authorities/TaggingLitchfield Historical Society
  • Create a user friendly public interface that will provide patrons with a single search portal for the society’s instances of ArchivesSpace and CollectionSpace.
  • Integrate social tagging with both databases to enable researchers to add detail to descriptions, as well as create a single external authority file source that will be shared between the databases.
  • Share tools with the open-source community via GitHub; documentation will be made available to facilitate implementation at other institutions using these systems.
Coming soon!Coming soon!
In-progress3

another, dots, menu, more, options, other iconImage Modified

CalTech Archives Integration ToolsCalTech Library
  • cait is a go library wrapping the ArchivesSpace REST API.
  • Includes support for content export, static site generation, indexing and independent search engine and web service.
  • Manage your content in ArchivesSpace but read and search the public content independent of the status of ArchivesSpace itself.
  • Gives you more options for deployment as well as providing a clean separation of concerns for public/admin uses.
On GithubOn Github
In-progressOther Community Projects

Ingest/Export Integrations

SystemName of IntegrationOrganizationObjective

Additional Information

StatusTier
CodeDocumentationOther

another, dots, menu, more, options, other iconImage Modified

EADCheckerHarvard LibraryAllows archivists to check whether there are issues with their finding aid that would prevent it from ingesting correctly into ArchivesSpace.On GithubOn Github
Completed!Other Community Projects

another, dots, menu, more, options, other iconImage Modified

ArchivesSpace PreprocessorHarvard LibraryA 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 GithubOn Github
In-progressOther Community Projects

Reporting Integrations

SystemName of IntegrationOrganizationObjective

Additional Information

StatusTier
CodeDocumentationOther