<div dir="ltr"><div>Hi everyone,</div><div><br></div>I just wanted to chime in to echo Alicia's excitement about most of these changes and express my own concern about AR-1874.<div><br></div><div>It's hard to imagine, from a collections control perspective, the advantage of having free-floating top containers not associated with intellectual information. Even if you have a true "mystery box" in your repository that has indecipherable scrawled sharpie on it (we've all been there, I AM there, I feel you), I think that it would be more valuable to associate this with an accession or resource record that explains that this is a true mystery and where you can record the steps that you've already taken to decipher it. Otherwise, you can't tell whether it's a lost/mystery box or if it was just somehow unlinked from the resource/accession record it belongs to. </div><div><br></div><div>Something I find valuable about ArchivesSpace is that as a system, it forces a minimum of best archival practices -- for instance, a resource record reinforces the DACS single-level minimum element set, top containers won't let you repeat barcodes, etc. I think that those of us who have participated in collection survey / remediation / backlog projects would definitely appreciate a system that forces at least some association between the stuff and where it came from.</div><div><br></div><div>Thanks!</div><div>Maureen</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 5, 2017 at 4:15 PM, Detelich, Alicia <span dir="ltr"><<a href="mailto:alicia.detelich@yale.edu" target="_blank">alicia.detelich@yale.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="m_-234251653066060641WordSection1">
<p class="MsoNormal">Hi Christine,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thank you for sending this. It seems like an exciting project, and many of the listed features are much-needed. I wonder, though, about the advisability of adding the “ability to create top containers independent of specific material records”
- <span style="color:#0563c2"><a href="https://archivesspace.atlassian.net/browse/AR-1874" target="_blank">https://archivesspace.<wbr>atlassian.net/browse/AR-1874</a></span>. You can already do this via the API - in fact, you have to create unlinked top containers before you can
link them to material description records. This is less than ideal, as it adds extra steps to the process - after creating the top containers, you then have to pull those top container URIs and link them to the material descriptions using a different endpoint.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">If the goal is to create top containers in bulk (and then link them to descriptions) via the staff interface, wouldn’t it make more sense, as the JIRA ticket above notes, to add that ability within a material description record or RDE (<a href="https://archivesspace.atlassian.net/browse/AR-1873" target="_blank">https://archivesspace.<wbr>atlassian.net/browse/AR-1873</a>),
rather than to enable the potential proliferation of unlinked containers? It seems like this could lead to all kinds of confusion and messy data in ArchivesSpace, especially if there are multiple unlinked containers with the same container profile, indicator,
etc. I think it might be better to solve the underlying issue rather than write a workaround into the application.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Alicia<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">---<u></u><u></u></p>
<p class="MsoNormal">Alicia Detelich<u></u><u></u></p>
<p class="MsoNormal">Archivist<u></u><u></u></p>
<p class="MsoNormal">Manuscripts and Archives<u></u><u></u></p>
<p class="MsoNormal">Yale University Libraries<u></u><u></u></p>
<p class="MsoNormal"><a href="mailto:alicia.detelich@yale.edu" target="_blank">alicia.detelich@yale.edu</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a> [mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_<wbr>group-bounces@lyralists.<wbr>lyrasis.org</a>]
<b>On Behalf Of </b>Christine Di Bella<br>
<b>Sent:</b> Thursday, October 5, 2017 2:40 PM<br>
<b>To:</b> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@<wbr>lyralists.lyrasis.org</a>>; Archivesspace Member Reps <<a href="mailto:archivesspace_member_reps@lyralists.lyrasis.org" target="_blank">archivesspace_member_reps@<wbr>lyralists.lyrasis.org</a>>; <a href="mailto:archivesspace_tac_uac@lyralists.lyrasis.org" target="_blank">archivesspace_tac_uac@<wbr>lyralists.lyrasis.org</a><br>
<b>Cc:</b> ArchivesSpace Board of Trustees mail list <<a href="mailto:archivesspace_bot_members@lyralists.lyrasis.org" target="_blank">archivesspace_bot_members@<wbr>lyralists.lyrasis.org</a>><br>
<b>Subject:</b> [Archivesspace_Users_Group] RFP for added container management functionality in ArchivesSpace<u></u><u></u></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Hello ArchivesSpace members,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">ArchivesSpace is seeking proposals from individuals or firms interested in providing development for a limited scope project to add functionality to the container management area of the application. We are prioritizing this work for engagement
of an outside contractor based on expressed interest from a number of members, including one that may have funding to pay for it. Please feel free to forward this RFP on to people you think may be interested and qualified to do this work.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">We are asking that people please email proposals to me (<a href="mailto:christine.dibella@lyrasis.org" target="_blank">christine.dibella@lyrasis.org</a><wbr>) by October 27, 2017. Proposals should include a proposed action plan, pricing, timeline, names and
contact information for at least two client references, and examples of relevant work in ArchivesSpace or other applications. If people have questions about the RFP, feel free to send them my way as well. Laney can answer technical questions about the application
and how delivery of code would work.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Issuing RFPs for specific projects is another strategy we are using to diversify our pool of available developers and continue to making substantial forward progress on the application. If you have any questions, or if you have suggestions
for projects that may be particularly appropriate for this type of treatment, please just let us know.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
<p class="MsoNormal">Christine<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#1f497d">Christine Di Bella<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#1f497d">ArchivesSpace Program Manager<u></u><u></u></span></p>
<p class="MsoNormal"><a href="mailto:christine.dibella@lyrasis.org" target="_blank"><span style="font-family:"Arial",sans-serif">christine.dibella@lyrasis.org</span></a><span style="font-family:"Arial",sans-serif;color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#1f497d"><a href="tel:(800)%20999-8558" value="+18009998558" target="_blank">800.999.8558 x2905</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#1f497d"><a href="tel:(678)%20235-2905" value="+16782352905" target="_blank">678-235-2905</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#1f497d">cdibella13 (Skype)</span><span style="color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><img border="0" width="267" height="61" style="width:2.7812in;height:.6354in" id="m_-234251653066060641Picture_x0020_1" src="cid:image002.jpg@01D33DF1.26D8A020" alt="ASpaceOrgHomeMedium"><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div></div></div>
</div>
<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>
<br></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><div dir="ltr"><font face="arial, helvetica, sans-serif" size="2">Maureen Callahan<br>Sophia Smith Collection Archivist<br>Smith College Special Collections<br>Northampton, Massachusetts 01063<br>T. 413 585 2981 C. 215.863.1860<br><a href="mailto:mcallahan@smith.edu" target="_blank">mcallahan@smith.edu</a></font><div><font face="arial, helvetica, sans-serif" size="2"><br></font></div><div><font face="arial, helvetica, sans-serif" size="2">Pronouns: she/her/hers<br></font><br style="font-family:arial,helvetica,sans-serif"><span style="font-family:arial,helvetica,sans-serif;font-size:small">Facebook: </span><a href="https://www.facebook.com/SophiaSmithCollection/" style="font-family:arial,helvetica,sans-serif" target="_blank">https://www.facebook.com/SophiaSmithCollection/</a><br style="font-family:arial,helvetica,sans-serif"><span style="font-family:arial,helvetica,sans-serif;font-size:small">Instagram: </span><a href="https://www.instagram.com/smithlibraries/" style="font-family:arial,helvetica,sans-serif" target="_blank">https://www.instagram.com/smithlibraries/</a><br style="font-family:arial,helvetica,sans-serif"><span style="font-family:arial,helvetica,sans-serif;font-size:small">Twitter: </span><a href="https://twitter.com/archivalagents" style="font-family:arial,helvetica,sans-serif" target="_blank">https://twitter.com/archivalagents</a></div><div><br><span style="font-family:arial,helvetica,sans-serif;font-size:12.8px"><b>Please note</b></span><span style="font-family:arial,helvetica,sans-serif;font-size:12.8px">. </span><span style="font-family:arial,helvetica,sans-serif;font-size:12.8px"><font face="arial, helvetica, sans-serif" size="2"><span style="color:rgb(0,0,0);vertical-align:baseline;white-space:pre-wrap;background-color:transparent">Smith College Special Collections is now housed at <a href="https://www.smith.edu/libraries/about/new-neilson/wheres-my-library" style="color:rgb(17,85,204)" target="_blank">Young Library</a>. Learn more about renovations to Neilson Library <a href="https://www.smith.edu/libraries/about/new-neilson" style="color:rgb(17,85,204)" target="_blank">here</a>. </span></font></span><font face="arial, helvetica, sans-serif" size="2"><br><br></font></div></div></div></div></div></div></div>
</div>