[Archivesspace_Users_Group] Request for community input: ANW-380

[Kottman, Miloche]

Cory,

Am I correct in assuming that the display in the Public Interface will look the same regardless of if the data is in just in the Begin Date Expression or in both begin and end date expression?  In other words:

Date subrecord
Begin Date Expression: circa 1950
Begin Date Standardized: 1950
End Date Expression: 1960
End Date Standardized: 1960
Certainty: Approximate

PUBLIC INTERFACE:   circa 1950-1960

and

Date subrecord
Begin Date Expression: circa 1950-1960
Begin Date Standardized: 1950
End Date Expression:
End Date Standardized: 1960
Certainty: Approximate

PUBLIC INTERFACE:  circa 1950-1960

--Miloche

******************************
Miloche Kottman
Head of Cataloging and Archival Processing
University of Kansas Libraries
Lawrence, KS 66045
mkottman at ku.edu<mailto:mkottman at ku.edu>
785-864-3916



From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Cory Nimer
Sent: Thursday, June 14, 2018 1:49 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>; ArchivesSpace <archivesspace at googlegroups.com>
Subject: [Archivesspace_Users_Group] Request for community input: ANW-380

Colleagues,

The Development Prioritization Team is seeking community input on a feature request for revisions to the Date subrecord in ArchivesSpace (ANW-380; https://archivesspace.atlassian.net/browse/ANW-380). The Date subrecord is used in multiple ArchivesSpace modules, including those for Accession, Resource, and Digital Object records. Changes to the Date subrecord to support the EAC-CPF <dateRange> model were previously included in the Agents revision project specifications (ANW-429; https://archivesspace.atlassian.net/browse/ANW-429), and the new model would support either EAD2002/EAD3 <unitdate> or EAD3 <unitdatestructured> exports.

The primary change planned is the separation of begin and end date expressions in the application. For example, currently a single date expression is used with separate normalized begin and end date entries for date spans:

Date subrecord
Date Expression: circa 1950-1960
...
Begin: 1950
End: 1960
Certainty: Approximate

The revised model would include a separate date expression field entry for each part of the date span:

Date subrecord
Begin Date Expression: circa 1950
...
Begin Date Standardized: 1950

End Date Expression: 1960
...
End Date Standardized: 1960
...
Certainty: Approximate

The concern has been raised that institutions may not have sufficiently consistent data entry practices to allow a single migration script to parse existing Date Expression values into separate Begin and End date expression fields. One proposed path has been to move the entire existing Date Expression value to the new Begin Date Expression, while moving the normalized dates to their appropriate standardized value fields. This would appear as:

Date subrecord
Begin Date Expression: circa 1950-1960
...
Begin Date Standardized: 1950

End Date Expression:
...
End Date Standardized: 1960
...
Certainty: Approximate

The Development Prioritization Team would like to obtain feedback from the community regarding preferences for migrating existing Date subrecord content, or other concerns. Comments may be submitted through JIRA on the ticket for ANW-380 (https://archivesspace.atlassian.net/browse/ANW-380).

Sincerely,

Cory Nimer
University Archivist
Brigham Young University
801-422-6091
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20180614/decc51e7/attachment.html>