[Archivesspace_Users_Group] archival object vs. instance?

Tue May 19 15:51:14 EDT 2015

Yes, the rapid data entry is a nice tool.  My nit-picky preference though would for it to be vertical rather than horizontal.  But the ability to hide fields is definitely helpful.

Matt

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella
Sent: Friday, May 15, 2015 3:13 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] archival object vs. instance?

Hi Matt,

Have you tried using the Rapid Data Entry tool in ArchivesSpace for entering this kind of data? It aims to make it easier to do data entry for straightforward contents lists and it’s available from any level within a resource record. We’re in the process of updating the instructions for the manual, but if you click the Rapid Data Entry button on any resource record you’ll see what it looks like and how you can customize it to just show the fields you want. You can also make field values “sticky” so that you don’t have to enter Box or folder (or anything else that gets repeated) every single time.

Best,
Christine

Christine Di Bella
Community Outreach and Support Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)
[cid:image003.png at 01CE734E.FD759D30]

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Matthew J Gorzalski
Sent: Friday, May 15, 2015 3:44 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] archival object vs. instance?

Thanks for clarifying Maureen.  I don’t think I’d ever seen archival object or instance used before in description and it was throwing me off.  I was also confused between the Archon’s container list interface and the way ASpace separates instantiation and description.   But I thought it might be a design improvement if the Archival Object’s “basic information,” “dates” and “instances” menus could be designed into one menu at the top where you could designate your level, instance, and descriptive information.

matt

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Callahan, Maureen
Sent: Friday, May 15, 2015 1:12 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] archival object vs. instance?

Hi Maura,

That’s right. I would consider your example to be not terribly useful description, and would also say that there are better ways of letting people know where to find stuff in boxes. You can think of archival objects as a guide to meaningful information about the collection – we’re here to explain the content and context of objects in our care, to make sense of it. Instances, then, are just a relationship between that description and where you can find the darn stuff. Description is important, containers are not.

I’ve written about this before here: https://icantiemyownshoes.wordpress.com/2014/04/04/the-value-of-archival-description-considered/

And here: https://icantiemyownshoes.wordpress.com/2014/12/15/on-containers/

Maureen

Maureen Callahan
Archivist, Metadata Specialist
Manuscripts & Archives
Yale University Library
maureen.callahan at yale.edu<mailto:maureen.callahan at yale.edu>
203.432.3627

Webpage: web.library.yale.edu/mssa
Collections: drs.library.yale.edu

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maura Carbone
Sent: Friday, May 15, 2015 2:06 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] archival object vs. instance?

Hi Maureen,
To follow up on that (as a non-archivist), would you recommend then not doing something like a nested Box1-> items in box1 etc.? Something like this:

[cid:image001.png at 01D08F18.788CB9E0]

I don't actually create finding aids, but I am now curious!

-Maura

On Fri, May 15, 2015 at 1:55 PM, Callahan, Maureen <maureen.callahan at yale.edu<mailto:maureen.callahan at yale.edu>> wrote:
Hi Matt,

I would encourage you to think about encoding differently.

An archival object is similar to what’s considered a unit of description in DACS and a component in EAD. “Level” is an attribute that tells you something about that unit of description — it is associated with levels of granularity in recordkeeping, and has NOTHING to do with boxes and folders. Setting level=‘box’ or level=‘folder’ would be an error, and an unfortunate conflation of groups of records and the physical wrappers that contain them. Please don’t do this.

When you create an archival object, you’re creating a description of evidence from the past, regardless of its physicality. This is why you can associate a digital OR physical instance of it. Indeed, the same archival object may be just digital, physical across different instances, or digital and physical. I like that ArchivesSpace has separated description from instantiation.

Maureen

On May 15, 2015, at 12:18 PM, Matthew J Gorzalski <mGorzalski at lib.siu.edu<mailto:mGorzalski at lib.siu.edu>> wrote:

This is difficult to explain in an email but here it goes…

I’m having trouble understanding the relationship between archival object and “instance” as it pertains to creating a finding aid content list.  The confusion stems from my familiarity with Archon’s straightforward parent-child relationship hierarchy, which uses established arrangement terminology.  Depending on the collection, creating a series, box, folder, etc. is simply a matter of selecting that option in Archon’s Level/Container menu and adjusting the parent-child relationships from there.

In ASpace, as I understand it, I first need to create an archival object and select the level of description.  If it is just a box list, I select “file” for box, title the box, and make the Component Unique Identifier “Box 1.”  But then I need to go to the “instance” menu and here is where I actually designate the container type as box, but I’m really just called in Box 1 for a second time in a different menu.  This seems redundant to me, because in the “archival object” data I’ve already called it Box 1 and given it a title.  Perhaps the interface could be simplified if the Archival Object, Instance, and Date menus were redesigned/merged so that you can create your archival object and designate the container type, titles, and dates right up front instead of having to scroll to the bottom for “instance.”  Container type, container title, and dates are the most important fields and the other menus like extent, agents, subjects etc. are added value but not critical in a box/folder list.

MATT GORZALSKI
University Archivist

MORRIS LIBRARY
MAIL CODE 6632
SOUTHERN ILLINOIS UNIVERSITY
605 AGRICULTURE DR
CARBONDALE, IL 62901

mgorzalski at lib.siu.edu<mailto:mgorzalski at lib.siu.edu>
P: 618/453-2225<tel:618%2F453-2225>
F: 618/453-3440<tel:618%2F453-3440>
lib.siu.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__lib.siu.edu_&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=ZubMFDWAu94jDCG27S3K3uw2F037N0osakw7ej3DOsM&s=h9WQmshw_oEC3DPAYgjoTlGXIqU_6_MXNV8fhb8An_Q&e=>

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=VkqdxJi02rh_qW0o2SwVjQrrdG2EViaVOoZOWgbwTb0&s=fw4knVcSXh9Tv6fiX2WZTXL7aT4A7fNsqS_nYFg-wY0&e=

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=ZubMFDWAu94jDCG27S3K3uw2F037N0osakw7ej3DOsM&s=BDmzmmXjr_8HlbYP4VlrSuLQRSQvfJrKctLao8xNprw&e=>

--
Maura Carbone
Digital Initiatives Librarian
Brandeis University
Library and Technology Services
(781) 736-4659
415 South Street, (MS 017/P.O. Box 549110)
Waltham, MA 02454-9110
email: mauraa at brandeis.edu<mailto:mauraa at brandeis.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150519/7efc5c4a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 7645 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150519/7efc5c4a/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 11981 bytes
Desc: image003.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150519/7efc5c4a/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vertical.jpg
Type: image/jpeg
Size: 309996 bytes
Desc: vertical.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150519/7efc5c4a/attachment.jpg>