[Archivesspace_Users_Group] Spawning resources

[Hilton, Adrien]

Hi Christie/Dan,

I noticed the same thing with spawning accession records, our default resource record template with pre-populated fields was ignored. Given the relatively little amount of data that transfers over, it’s more efficient for us to create a new resource record (from said template) and then link to the accession record.

Agreed, a thorough analysis would be nice!

Best,
Adrien

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Michelson, Daniel
Sent: Friday, August 25, 2017 10:20 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Spawning resources

Hi Christie,
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.
Regards,

Dan Michelson
Historical Records Project Archivist
Union College

On Fri, Aug 25, 2017 at 10:03 AM, Christie Peterson <cpeterson at smith.edu<mailto:cpeterson at smith.edu>> wrote:
Hello everyone,

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?

Thanks all,

Christie Peterson
Head of Technical Services for Special Collections
Smith College

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=o7OoY1I5SGwJOY4qFC1JgmA4MQwVJOWSxO2IqPX0FiU&m=aeXM3FBiMkvpBDDSEv7iRF9ODuux2tuQ-z_AO5vjTvQ&s=vFiU6R9NzAsv1XLuI2qOENoPXm_hrjJEKnx8GahwvUc&e=>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170825/bc069fda/attachment.html>