<html><body><div id="zimbraEditorContainer" style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000" class="4"><div><style><!--
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></div><div>Hi Christina,</div><div><br data-mce-bogus="1"></div><div>What if you make each map drawer its own top container, and assign the folders accordingly? We have tried various solutions for our share box(/drawer) problems and I would be interested to hear what other people are doing...</div><div><br data-mce-bogus="1"></div><div>Thanks,</div><div>Ali</div><div><br data-mce-bogus="1"></div><div><br></div><div data-marker="__SIG_PRE__">Alissa Zawoyski<br>Collection Management Specialist<br>Eberly Family Special Collections Library<br>Penn State University Libraries<br>814-867-0294<br>ajz12@psu.edu</div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Luers, Christina" <crluers@wm.edu><br><b>To: </b>"Archivesspace Users Group" <archivesspace_users_group@lyralists.lyrasis.org><br><b>Sent: </b>Wednesday, January 3, 2018 2:03:12 PM<br><b>Subject: </b>[Archivesspace_Users_Group] Top Containers and Item Level Descriptions<br></div><div><br></div><div data-marker="__QUOTED_TEXT__">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;" data-mce-style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;">Hello all,</span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;" data-mce-style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;"> I am hoping to find out if some of you would be willing to share how you manage your top containers for collections that have description at the item level.
</span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;" data-mce-style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;"> We have quite a few legacy collections that were processed dozens of years ago and were done at the item level for most, if not all, of the collection. While
we would not dream of processing collections to this level now, we also do not want to lose all of the metadata of some of those item level descriptions.
</span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;" data-mce-style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;"> In creating box and folder containers, we decided on a repository level that, since we pull at the box level, even for collections that share boxes, top containers
would be box level only. The only exception to this are the folders that reside in map cabinets.
</span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;" data-mce-style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;"> Our problem is this, when describing at the item level, we are having trouble getting more than one item into a folder without the folder being the top container.
This is something we certainly do not want to do. We can try to list the items in the folder scope and contents, but some of our legacy collections are in need of re-housing (ie One box has a total of four burrito type folders that each contain at least 40
or more items) but re-housing those collections is a far off task. We are looking for a much more easily accomplished task of fixing these legacy collections until we can devote the much needed time to them.
</span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;" data-mce-style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;"> </span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;" data-mce-style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;">Any suggestions on how to capture item level description for these legacy collections without making the folder the top container?</span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;" data-mce-style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;"> </span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;" data-mce-style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;">Many thanks for your time and offers of assistance.</span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;" data-mce-style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;"> </span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;" data-mce-style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;">Christina R. Luers</span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;" data-mce-style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;"> </span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;" data-mce-style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;">Archives Collections Specialist</span></p>
<p class="MsoNormal"><span style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;" data-mce-style="font-size: 11.0pt; font-family: 'Calibri',sans-serif; color: #1f497d;">College of William and Mary</span></p>
<div>
<div>
<div>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
<br>_______________________________________________<br>Archivesspace_Users_Group mailing list<br>Archivesspace_Users_Group@lyralists.lyrasis.org<br>http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<br></div></div></body></html>