<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p><br>
</p>
<p>Does anyone have an ArchivesSpace solution for non-agent non-subject "added entries" such as uniform titles in ArchivesSpace?</p>
<p><br>
</p>
<p>In other words do you have any experience expressing the analog of MARC 130, MARC 830 in ArchivesSpace? If so, what have you done? If you have encountered this problem and found no solution, what do you think the ideal solution would be?</p>
<p><br>
</p>
<p>Excitedly awaiting the collective wisdom!</p>
<p><br>
</p>
<p>Kate<br>
</p>
<div id="Signature">
<div name="divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<br>
Kate Bowers<br>
Collections Services Archivist for Metadata, Systems, and Standards<br>
Harvard University Archives<br>
Cambridge, Massachusetts, USA<br>
voice: (617) 384-7787<br>
fax: (617) 495-8011<br>
kate_bowers@harvard.edu<br>
<br>
<br>
<br>
</div>
</div>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Sally Vermaaten
<sally.vermaaten@nyu.edu><br>
<b>Sent:</b> Tuesday, January 19, 2016 12:15 PM<br>
<b>To:</b> archivesspace@googlegroups.com<br>
<b>Cc:</b> archivesspace_users_group@lyralists.lyrasis.org<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] [archivesspace] Planned enhancements to ArchivesSpace location management</font>
<div> </div>
</div>
<div>
<div dir="ltr"><font face="arial, helvetica, sans-serif">Hi Maureen, </font>
<div><font face="arial, helvetica, sans-serif"><br>
</font></div>
<div>
<p class="MsoNormal"><font face="arial, helvetica, sans-serif"><span style="color:rgb(33,34,36)">We've checked in with the consultant we plan to work with and I'm happy to report they were two steps ahead of us on permissions. They were already assuming that
the addition of location profiles would entail creating of a new permission category and had already factored this into their work estimates. We will therefore clarify in the spec that there will a new permission category for managing location profiles.</span></font></p>
<p class="MsoNormal"><span style="color:rgb(33,34,36)"><font face="arial, helvetica, sans-serif"><br>
</font></span></p>
</div>
<div><font face="arial, helvetica, sans-serif">Thanks again for your review!</font></div>
<div><font face="arial, helvetica, sans-serif">Sally</font></div>
<div><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Jan 15, 2016 at 12:06 PM, Callahan, Maureen <span dir="ltr">
<<a href="mailto:maureen.callahan@yale.edu" target="_blank">maureen.callahan@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 style="word-wrap:break-word">Maybe this is something that the community (and eventually the product owner group) can weigh in on, but it seems important to me that any new functionality follow the patterns of the application generally. Since it’s been
the case that when there’s a new record type that a user can interact with, there’s always a permission type that goes with it, I’d definitely like to see new development follow this pattern.
<div><br>
</div>
<div>MC</div>
<div>
<div class="h5">
<div><br>
<div>
<blockquote type="cite">
<div>On Jan 15, 2016, at 11:56 AM, Sally Vermaaten <<a href="mailto:sally.vermaaten@nyu.edu" target="_blank">sally.vermaaten@nyu.edu</a>> wrote:</div>
<br>
<div>
<div dir="ltr">
<p>Hi Maureen,</p>
<p>We're open to creating a new, specific permission category for managing location profiles and we agree that would be the most flexible approach.</p>
<p>In designating admins as the users who can manage and assign location profiles, our thinking was that it would be fine to just use the existing admin permission given how infrequently physical locations change. A repository may start using a new type of
box or other container several times a month or year so there's a strong need for a specific permission for container profile assignment. Location profiles on the other hand will only need to be updated when a repository has replaced or added shelving, cases,
etc. or when they get new stack space. For most repositories, this would probably occur only once a year or every few years so it seemed reasonable to limit this activity to admins.</p>
<p>This is something we're happy to get feedback on from the community. We can discuss how difficult it would be to create a specific permission category for managing location profiles with the consultants we plan to work with, though our suspicion is this
will likely need to go on the list of potential future functionality.</p>
<p>Thanks,</p>
<p>Sally</p>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Jan 15, 2016 at 8:25 AM, Callahan, Maureen <span dir="ltr">
<<a href="mailto:maureen.callahan@yale.edu" target="_blank">maureen.callahan@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 style="word-wrap:break-word">
<div>Hi Sally,</div>
<div><br>
</div>
<div>Would you consider creating a user permission category for managing location profiles, in the same way that there is one for managing container profiles? This way, the admin will have access to it anyway, but it gives folks flexibility to give someone
this access without making her an admin.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Maureen</div>
<br>
<div>
<blockquote type="cite">
<div>
<div>
<div>On Jan 14, 2016, at 5:38 PM, Sally Vermaaten <<a href="mailto:sally.vermaaten@nyu.edu" target="_blank">sally.vermaaten@nyu.edu</a>> wrote:</div>
<br>
</div>
</div>
<div>
<div>
<div>
<div dir="ltr"><span>
<div style="line-height:1.38; margin-top:0pt; margin-bottom:0pt"><span style="vertical-align:baseline; white-space:pre-wrap"><font face="arial, helvetica, sans-serif">Dear colleagues,</font></span></div>
<p dir="ltr" style="line-height:1.38; margin-top:0pt; margin-bottom:0pt"><span style="vertical-align:baseline; white-space:pre-wrap"><font face="arial, helvetica, sans-serif"></font></span></p>
<div style="line-height:1.38; margin-top:0pt; margin-bottom:0pt"><span style="vertical-align:baseline; white-space:pre-wrap"><font face="arial, helvetica, sans-serif">We would like to share NYU's plans to contribute several enhancements to ArchivesSpace's location
management functionality. We have attached a specification document which describes each of the 6 features we will be contributing to the core code. We believe these enhancements will benefit many - if not most - institutions by making the application an even
more effective tool for managing physical collections.</font></span></div>
<font face="arial, helvetica, sans-serif"><br>
</font>
<div style="line-height:1.38; margin-top:0pt; margin-bottom:0pt"><span style="vertical-align:baseline; white-space:pre-wrap"><font face="arial, helvetica, sans-serif">The new features are specifically aimed at making it easier to assign locations, identify
spaces where materials can be shelved and plan for collection growth. The features are optional, and existing functionality and the existing data model will be retained. If your institution chooses not to use the new features, you can carry on using ArchivesSpace
the way you were using it before these additions. </font></span></div>
<p dir="ltr" style="line-height:1.38; margin-top:0pt; margin-bottom:0pt"><span style="vertical-align:baseline; white-space:pre-wrap"><font face="arial, helvetica, sans-serif"></font></span></p>
<div style="line-height:1.38; margin-top:0pt; margin-bottom:0pt"><span style="vertical-align:baseline; white-space:pre-wrap"><font face="arial, helvetica, sans-serif">Two key parts of the new functionality are the ability to create a Location Profiles and the
ability, by using Location Profile and Container Profile information, to identify empty spaces in your stacks. The updates will also allow users to download 2 types of 'shelf lists' and to bulk assign multiple Containers to multiple Locations. We plan to work
with consultants with expertise in ArchivesSpace development to build these features during Northern Hemisphere winter to spring.
</font></span></div>
<font face="arial, helvetica, sans-serif"><br>
</font>
<div style="line-height:1.38; margin-top:0pt; margin-bottom:0pt"><span style="vertical-align:baseline; white-space:pre-wrap"><font face="arial, helvetica, sans-serif">We welcome any questions you may have. We would also be delighted to hear your ideas about
how these features could be built upon in the future (e.g. visualizations of stack spaces, even more efficient location identification, etc.). We will compile any suggestions received into an 'Ideas for future Locations Management features' document and share
with the community in the hope that other institutions will be inspired to run with great ideas captured there.
</font></span></div>
<font face="arial, helvetica, sans-serif"><br>
</font>
<div style="line-height:1.38; margin-top:0pt; margin-bottom:0pt"><span style="vertical-align:baseline; white-space:pre-wrap"><font face="arial, helvetica, sans-serif">Best,</font></span></div>
<div style="line-height:1.38; margin-top:0pt; margin-bottom:0pt"><span style="vertical-align:baseline; white-space:pre-wrap"><font face="arial, helvetica, sans-serif">Sally, Rachel and Chela</font></span></div>
<br>
</span>
<div><br>
</div>
-- <br>
<div>
<div dir="ltr">
<div>
<div dir="ltr">Sally Vermaaten<br>
Project Manager, Archival Systems<br>
New York University Libraries</div>
<div dir="ltr"><a href="tel:1-212-992-6259" value="+12129926259" target="_blank">1-212-992-6259</a><br>
</div>
</div>
</div>
</div>
</div>
<div><br>
</div>
</div>
</div>
<span><font color="#888888">-- <br>
You received this message because you are subscribed to the Google Groups "ArchivesSpace" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to
<a href="mailto:archivesspace+unsubscribe@googlegroups.com" target="_blank">archivesspace+unsubscribe@googlegroups.com</a>.<br>
For more options, visit <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=6xNuYlyuyUhr37cqKMhbO-TgXCvoUGEYQ-2s0S0mOzU&s=NWKRee4wbP4epvFX-V3rrnWqI0q0g5Qp1hDawP8jXaw&e=" target="_blank">
https://groups.google.com/d/optout</a>.<br>
<span><archivesspce_location_management_enhancements.pdf></span></font></span></div>
<span><font color="#888888"></font></span></blockquote>
<span><font color="#888888"></font></span></div>
<span><font color="#888888"><br>
</font></span></div>
<span><font color="#888888">
<div><br>
</div>
-- <br>
You received this message because you are subscribed to the Google Groups "ArchivesSpace" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to
<a href="mailto:archivesspace+unsubscribe@googlegroups.com" target="_blank">archivesspace+unsubscribe@googlegroups.com</a>.<br>
For more options, visit <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=ZM-ShDZ69dw4gwbeFtp-SLskv9YDbJueRFp6P0pmMdc&s=Z4tx5tOhxb_2OKzLDcTdJ4XPBja4AwADYTk4phox8H4&e=" target="_blank">
https://groups.google.com/d/optout</a>.<br>
</font></span></blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>
<div dir="ltr">
<div>
<div dir="ltr">Sally Vermaaten<br>
Project Manager, Archival Systems<br>
New York University Libraries</div>
<div dir="ltr"><a href="tel:1-212-992-6259" value="+12129926259" target="_blank">1-212-992-6259</a><br>
</div>
</div>
</div>
</div>
</div>
</div>
<div><br>
</div>
-- <br>
You received this message because you are subscribed to the Google Groups "ArchivesSpace" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to
<a href="mailto:archivesspace+unsubscribe@googlegroups.com" target="_blank">archivesspace+unsubscribe@googlegroups.com</a>.<br>
For more options, visit <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=ZM-ShDZ69dw4gwbeFtp-SLskv9YDbJueRFp6P0pmMdc&s=Z4tx5tOhxb_2OKzLDcTdJ4XPBja4AwADYTk4phox8H4&e=" target="_blank">
https://groups.google.com/d/optout</a>.<br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
<div class="HOEnZb">
<div class="h5">
<p></p>
-- <br>
You received this message because you are subscribed to the Google Groups "ArchivesSpace" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to
<a href="mailto:archivesspace+unsubscribe@googlegroups.com" target="_blank">archivesspace+unsubscribe@googlegroups.com</a>.<br>
For more options, visit <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout&d=CwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=f_NWew417JD7yXkgA_xIqliEzbCfeCIwk6OA9IBM0dE&s=kplKXzkXBIc1UzhoVpcIrgrdaqm28Dav82hJkVfeZvw&e=" target="_blank">
https://groups.google.com/d/optout</a>.<br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">Sally Vermaaten<br>
Project Manager, Archival Systems<br>
New York University Libraries</div>
<div dir="ltr">1-212-992-6259<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>