Page Comparison

ArchivesSpace is “an open source archives information management application for managing and providing web access to archives, manuscripts and digital objects”.

Hosting information

In August 2022 we switched from hosting our own ASpace server on EC2 to a third-party-hosted instance at LibraryHost. Hosting and support costs are paid out of Project 1520 - Born Digital. Our annual plan renews in September. Our original contract was for a Light Plan with our database on a shared server, however from August 2022 until August 2023 our instance is was hosted on a standalone server. This was due to physical memory issues in August 2022 which brought down the entire database and required an emergency move from the Light Plan (our shared ) server to Standard (a dedicated ) server. The Light Plan pricing is was locked in through the end of the ‘22-’23 annual contract, but in September 2023 we switched to a Plus Plan.

Support: support@libraryhost.com

...

API: https://sciencehistory-api.libraryhost.com/   

IP: 50.116.19.60

Our wildcard SSL certificates expire annually in October.

...

We store digital descriptions of our archival collections in the following places:

Workflow

• For newly processed collections, finding aids can be first written up as Word documents ultimately stored at Shared/P/Othmer Library/Archives/Collections Inventories/Archival Finding Aids and Box Lists. Finding aids/resource records may also be entered directly into ArchivesSpace or created using the bulk ingest spreadsheet for box and folder inventories or digital objects.

• For legacy finding aids (finding aids created before ArchivesSpace was in use at SHI), the Word document is revised and the revised finding aid data is entered into ArchivesSpace as a resource record. A list of legacy finding aids may be found at P:\Othmer Library\Archives\Legacy Finding Aid Docs

• Processing archivist enters the data into ArchivesSpace. If this data is from a legacy finding aid, the Word document finding aid is revised in the process.

• Once the collections are described in ArchivesSpace as resource records:

  • Our EAD export app in Heroku (see EAD export app ) retrieves public EAD files from ArchivesSpace’s API and posts them to the Science History Institute EAD bucket where they are harvested by PACSCL and CHSTM (see below).

  • If the processing archivist entered data directly into ArchivesSpace (there is no Word doc version), then a PDF is exported from the SUI and saved to the finding aid folder on the P:\ drive.

    • Note: the PDF or the Word doc has to be manually updated every time the resource record in ArchivesSpace changes.

  • The processing archivist exports a MARC XML version of the resource record and sends it to a cataloging librarian (usually Caroline), who creates a record in OCLC and the OPAC. The OPAC also points to a PUI URL at https://archives.sciencehistory.org/ .

    • Alternately, the cataloging librarian could use an ASpace account to export the MARC XML themselves.

    • Previously, there was a PDF version of the finding aid attached to the OPAC record. This practice has been discontinued with the launch of the ASpace PUI in Summer 2022.

  • Certain works in the Digital Collections also point to the PUI. Example: https://digital.sciencehistory.org/works/81jkowj.

• Finally, the exported EAD files in the Science History Institute EAD bucket are ingested by University of Penn Libraries Special Collections and the Center for the History of Science, Technology, and Medicine (CHSTM).

  • Penn, in turn, processes these EAD files on a nightly basis and adds them to the Philadelphia Area Archives search portal, a service funded by PACSCL.

    • Example: https://findingaids.library.upenn.edu/records/SCIHIST_2015.003

  • Likewise, CHSTM ingests these EADs and makes them searchable at its search portal.

    • Example: https://www.chstm.org/collections/search?text=Carbogel

...

The ArchivesSpace EADs are harvested by:

Both institutions harvest the EADs athttp://ead.sciencehistory.org/.

...