<div dir="ltr">I'm a little bit late to the party here - typical - but this is something I've thought about too. Our accessioning workflow involves the creation of both an accession and resource record for new collections. We still use the spawning feature because of the information it does automatically carry over (Title, extent, dates, scope and content note, agents and subjects) but I'd be keen to see some of the specifics you mention, Christie. I think the spawning functionality provides a concrete application for iterative and extensible workflows, and a way to show how we can create archival description at many different points along the way, so I'd like to make the most of that. I'd be happy to talk further about this as well - thanks for raising the issue.<div><br></div><div>Best,</div><div>Rachel</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 25, 2017 at 10:49 AM, Tang, Lydia <span dir="ltr"><<a href="mailto:ltang5@lib.msu.edu" target="_blank">ltang5@lib.msu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
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.<br>
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!<br>
<a href="https://docs.google.com/document/d/1NLTIBOwRrHdztQli2QvcRgr-JAIOXy_5TUXAAR-DRvg/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/<wbr>document/d/<wbr>1NLTIBOwRrHdztQli2QvcRgr-<wbr>JAIOXy_5TUXAAR-DRvg/edit?usp=<wbr>sharing</a><br>
Lydia<br>
--<br>
Dr. Lydia Tang, CA, DMA, MLIS<br>
Special Collections Archivist-Librarian<br>
Philosophy, Aesthetics, and Ethics Bibliographer<br>
Michigan State University Libraries<br>
<br>
From: <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a>> on behalf of "Michelson, Daniel" <<a href="mailto:michelsd@union.edu">michelsd@union.edu</a>><br>
Reply-To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
Date: Friday, August 25, 2017 at 10:19 AM<br>
To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>><br>
<span class="">Subject: Re: [Archivesspace_Users_Group] Spawning resources<br>
<br>
</span><span class="">Hi Christie,<br>
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.<br>
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?<br>
<br>
I'm wondering if this type of issue is something within the purview of the new Staff Interface Working Group.<br>
Regards,<br>
<br>
Dan Michelson<br>
Historical Records Project Archivist<br>
Union College<br>
<br>
</span><span class="">On Fri, Aug 25, 2017 at 10:03 AM, Christie Peterson <<a href="mailto:cpeterson@smith.edu">cpeterson@smith.edu</a><mailto:<a href="mailto:cpeterson@smith.edu">cp<wbr>eterson@smith.edu</a>>> wrote:<br>
Hello everyone,<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
Is anyone else already treading this path? Would any organizations like to start thinking and possibly working on this as a community?<br>
<br>
Thanks all,<br>
<br>
Christie Peterson<br>
Head of Technical Services for Special Collections<br>
Smith College<br>
<br>
______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
</span><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><mailto:<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">A<wbr>rchivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a>><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=nE__W8dFE-shTxStwXtp0A&r=M5PgloWvPMrr8ldOateLlQ&m=IikwWiUDD0nHvGEphQIA-2XSNnaM5GSjFxg8YhAEdnE&s=Ub7nh7aL3qsx32xz1MBX3_bIH7_1P2CsvD4cG434924&e=" rel="noreferrer" target="_blank">http<wbr>s://urldefense.proofpoint.com/<wbr>v2/url?u=http-3A__lyralists.<wbr>lyrasis.org_mailman_listinfo_<wbr>archivesspace-5Fusers-5Fgroup&<wbr>d=DwMFaQ&c=nE__W8dFE-<wbr>shTxStwXtp0A&r=<wbr>M5PgloWvPMrr8ldOateLlQ&m=<wbr>IikwWiUDD0nHvGEphQIA-<wbr>2XSNnaM5GSjFxg8YhAEdnE&s=<wbr>Ub7nh7aL3qsx32xz1MBX3_bIH7_<wbr>1P2CsvD4cG434924&e=</a>><br>
<div class="HOEnZb"><div class="h5"><br>
______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Rachel Searcy<br>Accessioning Archivist, Archival Collections Management<br><div><span style="font-size:12.8000001907349px">New York University Libraries</span><br></div><div><a value="+12129982631">212.998.2539</a> | <a href="mailto:rachel.searcy@nyu.edu" target="_blank">rachel.searcy@nyu.edu</a> <br></div></div></div></div></div></div>
</div>