<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi folks,
<div class=""><br class="">
</div>
<div class="">Welcome to production! Migrations are done, the database is live, and the first round of trainings has been completed. Here’s a list of things to know (and things we’re working on) to kick off the new tool.</div>
<div class=""><br class="">
</div>
<div class="">0. The basics</div>
<div class="">
<ul class="MailOutline">
<li class="">Archivists’ Toolkit is no longer supported. <b class="">Do not use it.</b></li><li class="">We are now in ArchivesSpace! Do your work here: <a href="https://aspace.library.yale.edu" class="">https://aspace.library.yale.edu</a></li><li class="">If you need a sandbox environment to muck around, experiment, and not worry about mistakes, go here: <a href="https://test-aspace.library.yale.edu" class="">https://test-aspace.library.yale.edu</a></li></ul>
</div>
<div class=""><br class="">
</div>
<div class="">1. Training and more training. </div>
<div class="">Over the last several weeks, we’ve held four introduction to ArchivesSpace training sessions. We understand, though, that it will take much more to make us all power users. To this end, here are some first steps for learning more about the application.</div>
<div class="">
<ul class="MailOutline">
<li class="">Our manual is here: <a href="https://docs.google.com/document/d/1DI_7YNZy-RcjQ9hpMMbxJEkHFpYndzmDoG3ylOc38BY/edit?usp=sharing" class="">https://docs.google.com/document/d/1DI_7YNZy-RcjQ9hpMMbxJEkHFpYndzmDoG3ylOc38BY/edit?usp=sharing</a> . Feel
free to insert a comment on the manual if you see anything that you think should be explained further.</li><li class="">The Lyrasis-hosted manual can be found by clicking the question-mark symbol in the application and registering as a member.</li><li class="">I will be holding ArchivesSpace open office hours every Tuesday, Wednesday and Thursday from 3:30 to 4:30. If you’re in Manuscripts and Archives, wave me over and we can explore and solve problems together. If you’re at another repository, give
me a call (2-3627) and we can either do a screen share or I’ll come on over.</li><li class="">As we catch our breath, it will be good to do more targeted training on how to use advanced features on the application.</li><li class="">Finally, we found that some questions we got during training were less about application use and more about archival practice. We’re eager to collaborate with the Special Collections Steering Committee to provide training opportunities around collections
management, archival description, and accessioning.</li></ul>
<div class=""><br class="">
</div>
</div>
<div class="">2. Performance sucks</div>
<div class="">There’s no getting around the fact that performance on ArchivesSpace is really poor right now. Steve DiSorbo in Library IT is working on some solutions, and I think that we’re all in agreement that this needs to get better and fast.</div>
<div class=""><br class="">
</div>
<div class="">3. Messy data growing pains</div>
<div class="">You may notice that controlled value lists (especially the extent type list) are very, very messy right now. This has to do with a few things — the natural consequences of bringing together four distinct databases, the way AT imported EAD, and
how difficult it is to clean up these values once they’re in ArchivesSpace.</div>
<div class="">Mark Custer and I have blocked off several days in July to work on this, so we can plan to see improvements by the end of the summer. </div>
<div class="">Just to review, the policy on the extent list is to only list space occupied, A/V carrier types, and a handful of values used for accessioning. Other values should go in the container summary field. The idea behind this is to allow for more rigorous
reporting and surveys. This policy is spelled out here: <a href="https://docs.google.com/document/d/1JHBq8FTc9nGrBdNkdD8_44ghQ_CRw5Gud2tMRN3GSOY/edit?usp=sharing" class="">https://docs.google.com/document/d/1JHBq8FTc9nGrBdNkdD8_44ghQ_CRw5Gud2tMRN3GSOY/edit?usp=sharing</a> </div>
<div class=""><br class="">
</div>
<div class="">4. Managing containers</div>
<div class="">As we discussed during training, ArchivesSpace takes a new approach to circulating containers. You can think of a container as its own record in the database (just like a subject or agent record), which is then linked to where appropriate. Since
this is a new process, don’t hesitate to reach out if you have trouble getting the hang of it. To help, I’ve made some screencasts to walk you through this process (scroll halfway down the page to see these). <a href="http://guides.library.yale.edu/ASpaceContainerManagement" class="">http://guides.library.yale.edu/ASpaceContainerManagement</a> </div>
<div class=""><br class="">
</div>
<div class="">Best wishes,</div>
<div class="">Maureen</div>
<div class=""><br class="">
</div>
<div class="">Maureen Callahan<br class="">
Archivist, Metadata Specialist<br class="">
Manuscripts & Archives<br class="">
Yale University Library<br class="">
<a href="mailto:maureen.callahan@yale.edu" class="">maureen.callahan@yale.edu</a><br class="">
203.432.3627<br class="">
<br class="">
Webpage: web.library.yale.edu/mssa<br class="">
Collections: drs.library.yale.edu</div>
</body>
</html>