Hi Olivia,

I have struggled with “Instance” and have to refer to my cheat note 
occasionally: “Manifestation of intellectual content” – meaning it could be 
physical or digital, so this is where containers enter (for physical objects) 
and also description about format. I’m not handling digital objects at this 
point, either.

The conceptual model takes getting used to in the beginning, but as someone 
else pointed out, once the concepts are more clear, the terminology should be 
less of a “thing.” The other nice thing is that one can mouse over labels in 
Aspace and the application often provides helpful additional information about 
the term.


Joan Curbow
Reference Librarian and Archivist
Buena Vista University Library
Buena Vista University
610 West Fourth Street
Storm Lake, Iowa  50588

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Olivia S Solis
Sent: Friday, April 06, 2018 4:04 PM
To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Lingo Cheat Sheet?

Hi all,

I always seem to post on Friday afternoons.

Throwing this out to the group because training is of immediate and scary 
concern. One of the things that I am acutely aware of is that our staff is 
going to have to get used to new terminology and fast to be able to use ASpace. 
Lingo is going to be a big barrier to access.

What have been some of your conceptual/terminology roadblocks in terms of staff 

Things I know I will have to explain as new terminology/conceptual reframing 
are included as headers below. I'm laying my work bare here, but I'm thinking 
that the crowdsourcing could be useful here. We've got people at varied levels 
of technical proficiency. I was thinking of an informal cheat sheet.

Did you make a cheat sheet for ASpace lingo for staff training? Am I not 
including some conceptual leaps here? Did you have ASpace terminology you had 
to explain in multiple ways?


Agent Record

A record type for a person, family, corporation, or software. A major record 
type in ASpace that can link to Accession Records, Resource Records, Archival 
Object Records, and Event Records in various roles, most often as subjects and 
creators. Every distinct agent has one and only one record.

Archival Object Record

[NOTE we're not using ASpace for digital objects]
A record type for an item in an inventory. If are familiar with EAD, this 
corresponds to a <c##> level. If not, think of this as a tabbed level of an 

ArchivesSpace thinks of hierarchical relationships as "parent"/"child". A 
parent could be the <c01> to a child <c02>, though ASpace would never frame it 
in terms of specific numbered component levels. A parent could also be the box 
that a child reel/folder/box within the parent box

Container Profile

Basically, the type and dimensions of a container. Container profiles are 
consecutively numbered by type. For a description of container types see [this 
link]. For specs/pictures of different container types, see [this link].

Event Record

In DBCAH's implementation, Event Records document specific steps taken in 
archival processing, most comprehensively in Accession Records (e.g. Deeds of 
Gift sent or received). Event Records are bound to specific dates.

Location Profile
Note (resources)
Resource Record

Essentially a finding aid plus some additional collection management 

Space Calculator

Olivia Solis, MSIS
Metadata Coordinator
Dolph Briscoe Center for American History
The University of Texas at Austin
2300 Red River St. Stop D1100
Austin TX, 78712-1426
(512) 232-8013
Archivesspace_Users_Group mailing list

Reply via email to