<occupation encodinganalog=”656″ source=”aat”>Dancers.</occupation>
<occupation encodinganalog=”656″ source=”lcsh”>Dance teachers.</occupation>
<c01 level=”file”><did><container type=”box-folder” label=”Box “>1 : 1</container>
<unittitle>Biographical and academic materials</unittitle></did>
<c02 level=”file”><did><container type=”box-folder” label=”Box “>FB-21 : 1</container>
<unittitle>Boston Girls’ High School, commencement program</unittitle>
(It is a testament to my graduate school professors and me that I can actually understand that pretty well.) You can now see why, in fact, AT’s interface was the height of 2009 fashion when it debuted:
Human-readable! No angled brackets in sight. We had a couple of options to replace AT as its usefulness waned, but its closest relative is the system we went with, ArchivesSpace (ASpace). Like AT, ASpace is an open-source application, though it is funded through a membership model that will hopefully encourage a longer lifespan that AT had. It’s also a web-based application, meaning it’s more Pandora than Napster. And its interface is contemporary, full of with smooth sans-serif fonts:
While the data migration from one system to another was smooth thanks to work by Web Services Kevin Gilbertson, Archives Assistant Finley Turner, me, and our vendor Atlas Systems: now we have to look under the hood and figure out how this thing works! I’ve noticed that takes more clicks to get around, and more noticably, the locations of certain fields and the language used has changed. We’re no longer dealing with “Names”; they are now “Agents.” Numerical identifiers are now separated with hyphens instead of periods, which is just weird to my eye.
I won’t bore you with a list of all the differences between the systems, but with these changes big and small, I have to determine how we will use ASpace. Will our procedures shift wildly? No, thankfully. And plenty of other organizations are using ASpace, so there is documentation to read and colleagues to call with questions.
But in order to make sure that everyone in SCA is using the system as similarly as possible, I have to codify which information goes into each field, which fields we won’t use, what other tools we will add in to make our lives a little better (hopefully!). And then everyone else needs to get comfortable with ASpace, too, since it’s our main tool for serving up materials for people seeking informaiton and coming through our Research Room. During the school year, student workers use it every day as well. Basically, now that we’ve got a new kind of oven, we’ve got to figure out practical, efficient ways for us, together, to bake bread and make nachos – or process and provide access to collections – in it. Wish us luck!