Import resources, archival objects, etc. into ArchivesSpace using Excel spreadsheet files
Branch: master
Clone or download
Latest commit 150f462 Jan 30, 2019

README.md

aspace-import-excel

An ArchivesSpace plugin to support the bulk uploading via Excel SpreadSheet of Archival Objects and (optionally) their associated Creator Agents, Top Containers, Subjects, Digital Objects etc.

Also supports the inport of spreadsheets that will allow for the creation of Digital Objects to be associated with already-created Archival Objects for Version 2.2.2 and higher of ArchiveSpace.

Current Version

For versions of ArchivesSpace before v2.2.2: v1.7.8

NOTE: This version does *not* support the creation of Digital Objects to be associated with already-created Archival Objects.

For ArchivesSpace v2.2.2 and higher: v2.1.19

Development

The initial version supports interactive selection of an archival object (or resource) as the starting point of the bulk upload.

Bulk upload/creation of Archival Objects

The Excel template will be found in the templates/ folder as aspace_import_excel_template.xlsx.

The intention is not to completely reproduce a Finding Aid as presented in an EAD XML, or to allow for every permutation of Archival Object creation within ArchivesSpace. We are aiming for the "80% rule"; that is, at least 80% of the work that would be done interactively can be replaced by an excel spreadsheet; additional refinements to individual archival objects (such as addition of agents-as-subjects, assignment of locations to top-level containers, etc.) would take place interactively.

See the user documentation for more information.

Bulk upload/creation of Digital Objects associated with already-created Archival Objects

This functionality is turned on by default See the Installation instructions for turning it off.

The Excel template will be found in the templates/ folder as aspace_import_excel_DO_template.xlsx.

As with the original development, we are not completely reproducing all the functionality of ArchivesSpace: only one Digital Object, which can have either or both of one:

  • File with an Xlink Actuate Attribute of onLoad and an Xlink Show Attribute of embed
  • File with an Xlink Actuate Attribute of onRequest and an Xlink Show Attribute of new

See the user documentation for more information.

Installation

This is a regular ArchivesSpace Plug-in.

To install this plug-in:

  1. Either clone this plugin, or download the latest version:

    • Clone the plug-in from this GitHub repository into the ArchivesSpace /plugins/ directory.
    • Download the zipfile of the appropriate version: see Current Versions for links to the appropriate release download. Unzip the download into the /plugins/ directory. You will probably need to rename the top folder/directory to aspace-import-excel.
  2. (Optional) To turn off the functionality for creating Digital Objects associated with already-created Archival objects, you must edit /plugin/aspace-import-excel/frontend/plugin_init.rb. Change the line

    AppConfig[:hide_do_load] = false

to

    AppConfig[:hide_do_load] = true
  1. IF you are running ArchivesSpace on Windows:

    There currently is a problem with Bundler versioning. Until a new version of ArchivesSpace is released that contains a fix to the initialize-plugin.bat script, copy

archivesspace\aspace-import-excel\extras\modified_initialize-plugin.bat 

to

archivesspace\scripts
  1. Run the initializer script:

    • for Linux, that's
    scripts/initialize-plugin.sh aspace-import-excel
    • for Windows, that's
    scripts\modified_initialize-plugin.bat aspace-import-excel
    
  2. In the common/config/config.rb file, add 'aspace-import-excel' to the AppConfig[:plugins] array.

  3. Stop and restart ArchivesSpace

Why we don't include a Gemfile.lock in this repository

We have found that when we include a Gemfile.lock file in our plugin, some sites have found that, after initializing the plugin and trying to restart ArchivesSpace, they get errors like this:

[!] There was an error parsing Gemfile: You cannot specify the same gem twice with different version requirements.
You specified: rubyzip (~> 1.2.2) and rubyzip (= 1.0.0). Bundler cannot continue.

This problem does not seem to occur when the Gemfile.lock is created through the initialization instead.

User Documentation

User documentation is available

Contributors