[Archivesspace_Users_Group] User Defined Fields use cases

Bowers, Kate A. kate_bowers at harvard.edu
Tue Mar 1 13:22:03 EST 2022

Imagine a case where you take in an entire archive, with its own accession data and accession number format, and you wish to create one-to-one accessions in your own system for the accessions that you inherited.

Imagine a case where accession numbers had been assigned in error.

Imagine you have a complicated corporate environment, and the people who send you accessions from a single "agent" are different people with different contact information, so that adding a "contact" to an agent would leave ambiguity as to whom to contact regarding the accession or changing  the contact on the agent would, essentially, change the record of the transfer.

Here are some of the fields you might want:

  *   Former accession number.
  *   Alternate accession number.
  *   Source of accession data and ingest date (for accession data migrated into AS)
  *   Contact information for the accession.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of McLaughlin, Brianna Jean
Sent: Tuesday, March 1, 2022 12:30 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] User Defined Fields use cases

Hi all,

Would anyone mind sharing some uses cases for User Defined Fields on Resource or Accession records?


Bri McLaughlin, she/her/hers
Visiting Metadata Services Librarian
Indiana University

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220301/d769f63b/attachment.html>

More information about the Archivesspace_Users_Group mailing list