[Archivesspace_Users_Group] Public Interface development/customization

Mon Mar 30 10:23:22 EDT 2015

Hi, Colleagues,

Instance in ArchivesSpace is indeed a carryover the Archivists’ Toolkit.

It was conceived by a bunch of archivists at an AT meeting in La Jolla, CA, around 2005 as a means to record different instantiations of the same content description without have to create another component.  The instance declaration can then be linked to a container that can then be located within a repository’s storage space.   Here’s a basic example:

Content

Instance

Container

Location

Thomas Jefferson letter

Original

Document case

Vault, etc.

Microfilm

Reel #, Frame #

Microfilm cabinet

PDF

http//…

Thus allowing for:

Component:
Thomas Jefferson letter
                                Original in Document Case located in Vault
                                Microfilm on Reel # at Frame # located in Microfilm Cabinet
                                PDF located on web at http:…

Instead of

Component:
Thomas Jefferson letter in document case in Vault

Component:
Thomas Jefferson letter on reel # at frame# in Microfilm Cabinet

Component:
Thomas Jefferson letter at http:….

The concept of the instance is related to the FRBR data model, and it is replicated in the BibFrame data model where the opposition is “work” and “instance”:

[cid:image001.png at 01D068D1.D9C2CBE0]

In response to Matt’s comment, ‘archival object’ is an accident.  It was devised to refer to all the material description records (accession, resource, resource component, digital object, and digital object component) as a class but it was inadvertently used to describe resource components in the application.  The term is distributed throughout the code, and we have not yet prioritized replacing it.

We used Resources as the term for processed materials instead of collections simply because Resources can be either aggregations or items.  This too is a carryover from the Archivists’ Toolkit.

That all said, we welcome your scrutiny of and suggestions for both the public and staff interfaces.  Enhancing the ArchivesSpace public interface is a major part of the development plans for 2015.  We have identified from various sources 64 issues<https://archivesspace.atlassian.net/browse/AR-1173?jql=labels%3Dpublic_interface%20and%20resolution%3Dunresolved> concerning the public interface.  We intend to contract a UI/UX consultant to assist with this endeavor.   Later this week we will complete the scope of work statement necessary for such a contract.  Last, we will establish a task force of ArchivesSpace members to conduct this work, which will require reviewing, prioritizing, and testing the enhancements.  Mark Custer of Yale University has volunteered to lead the group, and Brian Hoffman, one of the ArchivesSpace developers, will be assigned to the task force.  Mark will be posting a call for volunteers soon, as well as a fuller description of the task force’s objectives.  I am sure this effort will also take into account the ArcLight<https://wiki.duraspace.org/display/hydra/ArcLight> effort that Tom Cramer referenced in his post Saturday.

More on this soon,

Brad W.
Bradley D. Westbrook
Program Manager
brad.westbrook at lyrasis.org<mailto:brad at archivesspace.org>
800.999.8558 x2910
678.235.2910
bradley_d_westbrook (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] On Behalf Of Susan Luftschein
Sent: Friday, March 27, 2015 2:12 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Public Interface development/customization

Not sure about Archon, but AT used “instance”, so I’m assuming it’s a holdover.  It’s a concept I always had problems wrapping my head around, in spite of repeated explanations from Brad Westbrook!

On Mar 27, 2015, at 10:03 AM, Matthew J Gorzalski <mGorzalski at lib.siu.edu<mailto:mGorzalski at lib.siu.edu>> wrote:

I don’t mind chipping in.  I always wondered why professional jargon like box and folder were changed to “instance” and collection was changed to “archival object”

Matt Gorzalski

SIU Carbondale

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 Morecraft, Lindsay M
Sent: Friday, March 27, 2015 11:18 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Public Interface development/customization

I would be very interested on being a part of this conversation. I think there are great opportunities for customizing the public interface.

Lindsay Moen (Morecraft)
Processing Librarian
Special Collections and University Archives
The University of Iowa
319-335-5921

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 Jane A. Callahan
Sent: Friday, March 27, 2015 10:32 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Public Interface development/customization

Hi Friends,

I'm hoping to connect with institutions who are working on customizing the public/patron interface or are planning on it.

I'm particularly interested in brainstorming label jargon changes for terms like components, instances, and record tree etc.

Also, can someone remind me of the development plans and timeline for the public interface?

Thanks!
Jane

----
Jane A. Callahan
Archivist, Wellesley College
Margaret Clapp Library
Wellesley, MA  02481
phone: 781-283-2128
jane.callahan at wellesley.edu<mailto:jane.callahan at wellesley.edu>

*** Many people want your password so they can steal your information. If an email asks you to send your password or directs you to a page that is NOT in the wellesley.edu<http://wellesley.edu/> domain, DO NOT provide your password. LTS will never ask for your passwords -- when in doubt, contact the LTS Computing Help Desk.
_______________________________________________
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

Sue Luftschein
Archival and Metadata Librarian
Special Collections
USC Libraries
luftsche at usc.edu<mailto:luftsche at usc.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150330/0e78ec64/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5883 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150330/0e78ec64/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 7631 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150330/0e78ec64/attachment-0001.png>