[Archivesspace_Users_Group] Spawning resources
ltang5 at lib.msu.edu
Fri Aug 25 10:49:15 EDT 2017
Yes, it would be something for the Staff Interface Enhancement Working Group! Currently, we are still in the early stages of the group, but would be very interested in working with you both (and anyone else), in identifying what can be improved and making recommendations on how it can be improved.
This is currently a brainstorm document on new capabilities we’d like to see in the Staff Interface. In there is currently in a very basic form some ideas about treating the default presets for Resources/Accessions as selectable/merge-able templates. You all are welcome to add your ideas or create a JIRA ticket. If you go with the JIRA route, please be sure to tag it with “staff_interface” Thanks!
Dr. Lydia Tang, CA, DMA, MLIS
Special Collections Archivist-Librarian
Philosophy, Aesthetics, and Ethics Bibliographer
Michigan State University Libraries
From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Michelson, Daniel" <michelsd at union.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Friday, August 25, 2017 at 10:19 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Spawning resources
We've run into some of the same issues here at Union College. Another example is that resource records spawned from accessions ignore defaults for new resource records.
Presumably some of these have to do with the difficulty of predicting user desires. To use one of your examples, should the Provenance field in the Accessions Module map to the Custodial History Note or the Immediate Source of Acquisition Note?
I'm wondering if this type of issue is something within the purview of the new Staff Interface Working Group.
Historical Records Project Archivist
On Fri, Aug 25, 2017 at 10:03 AM, Christie Peterson <cpeterson at smith.edu<mailto:cpeterson at smith.edu>> wrote:
Here at Smith we're currently diving head-first into using ASpace for our accessioning and description workflows, and we're going to be making healthy use of the spawn resource feature.
There are some things that do not happen in the spawning process that we would like -- carrying over things like provenance information, machine-actionable restrictions, etc.
I searched Jira and didn't see these as open issues. It feels to me like rather than reporting issues one-at-a-time, it might be worthwhile to consider a re-examination of the mapping and spawning, and maybe funding some work to improve this process.
Is anyone else already treading this path? Would any organizations like to start thinking and possibly working on this as a community?
Head of Technical Services for Special Collections
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
More information about the Archivesspace_Users_Group