[Archivesspace_Users_Group] Collection management - processing status disappeared...

Bowers, Kate A. kate_bowers at harvard.edu
Tue Nov 17 16:08:49 EST 2015

I am very confused.  Can you explain how this is would work? How is an archivist supposed to understand an accession’s status from one or more associated “events” rather than from a straightforward status?  I can also see how this would make reporting out backlogs really difficult.

The reason I ask is that I can see how an event can lead to a status, but it is entirely possible that a status may have no associated event.  Furthermore, the same type of event may lead to different statuses.

In brief, status is not the same as “event”.  I can think of a couple of examples to illustrate this:

·        “Unknown” can be a status, but it has no associated event

·        “Partially processed” can be both a status an event.  However, if one “partially processes” an accession once, then the accession remains partially processed.  If one “partially processes” again, it could be that the processing has been completed and the accession’s status is now “processed” or it could be that the accession is still only “partially processed” and that additional processing events will be necessary to reach a “processed” status.



Kate Bowers
Collections Services Archivist for Metadata, Systems, and Standards
Harvard University Archives
kate_bowers at harvard.edu<mailto:megan_sniffin-marinoff at harvard.edu>
voice: (617) 384-7787
fax: (617) 495-8011
web: http://nrs.harvard.edu/urn-3:hul.eresource:archives
Twitter: @k8_bowers

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Noah Huffman
Sent: Tuesday, November 17, 2015 3:01 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Collection management - processing status disappeared...

Hi Kelly,

During a previous release (v1.3), I think Processing Status was moved from the collection management subrecord to an Event record.  Here is a JIRA issue describing this change: https://archivesspace.atlassian.net/browse/AR-827<https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D827&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=KjdPV61xIn7OR7Ks9cg6HRC91WufUrZNTXFAT4skW8w&s=AZTgid9lXUTh7glUns7pyqqX7w28sAhx7rK3QIIMb8o&e=>

Here are some specifics:
Remove “Processing Status” Collection Management sub-record

If data is present, migrate to Event record with these settings and linked to same record collection management sub-record is linked to:

Type = “Processing [Value in Collection Management Record for Processing Status]”

Date/Time Specifier = “Time stamp for last modification of Collection Management record”

Label= Agent relationship



Agent=ID of agent last modifying the collection management sub-record

So, if you previously had processing status in a collection management subrecord, you might try browsing your event records to see if you can locate that data.

Hope this helps,


Noah Huffman
Archivist for Metadata, Systems, and Digital Records
David M. Rubenstein Rare Book & Manuscript Library
Duke University | 919-660-5982

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 Kelly Spring
Sent: Tuesday, November 17, 2015 2:40 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Collection management - processing status disappeared...


Our Processing Status field is visible when using the Manage Controlled Value Lists feature; but is not present when actually working within a collection management sub-record in an accession or resource. Any tips or advice out there?

Thank you and have a great day!

Kelly Spring
Archivist for Special Collections
University of California, Irvine Libraries
(949) 824-6573

[icon-twitter]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_UCI-5Farchives&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=KjdPV61xIn7OR7Ks9cg6HRC91WufUrZNTXFAT4skW8w&s=BlzeQSNZ7E-drsWq3sdaT3Qa7YlB1ShPfnsRCyot_DA&e=>  [icon-lib] <https://urldefense.proofpoint.com/v2/url?u=http-3A__sites.uci.edu_ucisca_&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=KjdPV61xIn7OR7Ks9cg6HRC91WufUrZNTXFAT4skW8w&s=rIxUTv0PbQbig86o_cCCApbo-5kS25j0b4plxLDQpI4&e=>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151117/027db3fa/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 6032 bytes
Desc: image001.gif
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151117/027db3fa/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 806 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151117/027db3fa/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1360 bytes
Desc: image003.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151117/027db3fa/attachment-0001.png>

More information about the Archivesspace_Users_Group mailing list