[Archivesspace_Users_Group] experience using AS OAI-PMH with discovery layer like Summon?
ltang5 at lib.msu.edu
Wed Apr 4 15:37:40 EDT 2018
We’ve just starting doing this too. We’re also in a weird in-between stage because our web services has been harvesting an HTML scrape for their bento box discovery layer as well. We ran into a snag earlier, because it seemed to be recalling duplicate records via OAI-PMH for our web interface. (I’m hoping upgrading to the latest version will help this).
My criticism so far is that it is so easy for archival objects to get completely buried in comparison to the online articles, books, media, and other content. Usually, I have to specifically scope the results to get “archival materials” when trying to use Summon. I didn’t exclude Agents and Subjects (although perhaps I should), but from my experience, the bigger problem is that I have to dig so deep in the searches to even find ASpace records.
For people who are curious, this is our catalog page:
Summon results happen in the top left box (Once searching for something, click the “See more” for Articles box).
We also create collection-level catalog records, which often show up in the “Books & Media” section, although that doesn’t index keywords that aren’t represented in the catalog record.
We have a more nuanced search function on our Special Collections’ page (hey, that’s me in the picture!): https://lib.msu.edu/spc/index/
It tends to pick up (almost to a fault), everything we have in ArchivesSpace in a dedicated “Archival Collections” box, which often includes a plethora of subjects.
Imperfect, but all for the sake of creating avenues of discovery! If anyone has feedback or other solutions, it would be great to keep sharing on this topic!
From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Cobourn, Alston" <Alston.Cobourn at tamucc.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Wednesday, April 4, 2018 at 2:45 PM
To: "archivesspace_users_group at lyralists.lyrasis.org" <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] experience using AS OAI-PMH with discovery layer like Summon?
I have a dream of making the published resource records and their components in our ASpace instance available in our library’s Summon instance, and my plan is to do so using OAI-PMH. The configuration instructions on GitHub say that “Harvesting the ArchivesSpace OAI-PMH server without specifying a set will yield all published records across all repositories.” Am I correct in thinking that “all published records” would mean published resources, resource components, accessions, digital objects, and agents. Is there a type of “publishable” record that I am forgetting?
At the moment, the only “set” of published information that I’m thinking of having Summon exclude is agents. If you’ve already made these kinds of decisions and you can think of a positive, downside, or implication I may be overlooking, I’d appreciate hearing from you. Obviously, I’m trying to think this through to make sure I don’t have Summon suck in a bunch of stuff we don’t want them to.
Processing and Digital Assets Archivist
Texas A&M-Corpus Christi
Alston.cobourn at tamucc.edu<mailto:Alston.cobourn at tamucc.edu>
More information about the Archivesspace_Users_Group