[Archivesspace_Users_Group] LCNAF plugin

Wed Apr 12 15:30:52 EDT 2017

This is really wonderful work and discussion. Thank you all for these efforts!

I wanted to mention a few things related to ongoing ArchivesSpace development and a few of the points in the discussion.

·         There are several related JIRA issues related to the Dates/Dates of Existence issue specifically: https://archivesspace.atlassian.net/browse/AR-1322, https://archivesspace.atlassian.net/browse/AR-1339, and https://archivesspace.atlassian.net/browse/AR-1344.

·         The Dates field is the Agent record is no longer deprecated. This decision was made awhile back, but the tooltip and documentation are just catching up with the 2.0.0 version. The short version of why this is the case is that in the current application, the Dates field is needed for alignment with MARC while the Dates of Existence fields align better with EAC-CPF and allow for more precise use of dates. Currently what is in the Dates field is also what is put into the display string for an Agent, on both the staff interface and the public interface. While it is certainly not the most satisfying answer, the current solution is to either use both sets of dates, or to choose the one that most reflects your intended output.

·         As Francis suggests, a more robust Agents module is in the planning stages. Cory Nimer and Brad Westbrook have been working on specification for a substantial reworking of the Agents module, along with fuller support for EAC-CPF. I believe this specification will be ready for wider community review soon. In addition to providing the potential for recording additional types of information about people, families, and corporate bodies, reworking the Agents module could potentially come up with a solution for this date redundancy problem, though from this discussion it sounds like there are use cases for maintaining both ways to record dates.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Cyndi Shein
Sent: Wednesday, April 12, 2017 2:12 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] LCNAF plugin

Hello all,
Just to weigh in on this conversation, local practice here at UNLV supports Francis' statement:
Dates that appear in the name form (and part of the access point) aren’t necessarily the same as those that represent dates of existence. We may sometimes want to record dates of existence even if dates are not included in the access point. So we need both data elements.

We find that the dates of existence field permits us to include information absent from the authorized heading... not all headings have dates, and death dates are not often added in a timely manner.

We're excited about all the developments!

Cyndi Shein
Head, Special Collections Technical Services
University Libraries, University of Nevada, Las Vegas
cyndi.shein at unlv.edu<mailto:cyndi.shein at unlv.edu>             (702) 895-2223
[cid:image002.jpg at 01D2B3A1.73D87D80]

On Wed, Apr 12, 2017 at 10:52 AM, Lapka, Francis <francis.lapka at yale.edu<mailto:francis.lapka at yale.edu>> wrote:
Thanks Karen. My comments are below.

Francis

--

Karen Miller k-miller3 at northwestern.edu <mailto:archivesspace_users_group%40lyralists.lyrasis.org?Subject=Re%3A%20%5BArchivesspace_Users_Group%5D%20LCNAF%20plugin&In-Reply-To=%3C82e30afaa16f4ea2b07386fea46a98c4%40evcspmbx05.ads.northwestern.edu%3E>
Tue Apr 11 12:57:21 EDT 2017

Francis, this is great news and I'm very excited by the prospect of getting an updated plug-in! We're doing a lot of editing when using it now, and the changes you have planned will eliminate a lot of that work for us at Northwestern.

-          FL: Excellent! Yes, our goal is that authorities imported via the plugin will require no (or minimal) manipulation after import.

I only have two comments on the mappings.

1.       I'd rather see contents of the 100$d, 110$d, and 111$d go into the Dates of Existence sub-record instead of Name Forms\Date, since the latter is deprecated. I have mixed feelings about this, though - on the one hand, if there is a 046 present, it may include a more granular date than is in the $d, and it would be a shame to lose that. On the other hand, for many records there is no 046 and only a $d. In these cases, it might be possible to extract appropriate date fields from the $d; Gary Strawn (our former authorities librarian, but still at NUL working archival processing), has written some code that was used to create 046 fields from $d when Library of Congress started automatically converting selected records from AACR2 into RDA. He mentioned that he'd be happy to share it, if it's of interest.

-          FL: There is an implicit suggestion in this mapping that deprecation of Name-Forms\Date isn’t the correct approach. Here’s our thinking: The components of an AS name form are all sub-parts of the access point. If an access point has dates, those dates need to appear in the name form section. Dates that appear in the name form (and part of the access point) aren’t necessarily the same as those that represent dates of existence. We may sometimes want to record dates of existence even if dates are not included in the access point. So we need both data elements. This approach parallels what he have in LCNAF, where dates in 1xx $d exist in parallel to dates in 046 – because they mean different things. There is an argument for deriving dates of existence from the dates in the name form (upon import), but our Yale group has opted (so far at least) not to take that option.

2.       I'd also prefer not to strip the terminal periods from 100$, 110$c or 111$c. Although this is listed in your mapping spreadsheet, it does not appear to have been done in the example for the Brown (Family : 1910-1956 : Me.), where the $c is mapped to the Qualifier field as "Me." with the terminal period retained.

-          FL: Yeah, I see the arguments for not stripping those periods. Doing so causes problems with headings such as “$a Seuss, $c Dr.” We’ll review this.

Finally - and this is just a *thought*, not a suggestion! - at some point in time, it would be wonderful to see the ArchivesSpace Agent record model expanded to accommodate some of the fields that are now being added to name authority records under RDA, such as Fields of Activity, Occupations, Associated Places (including place of birth, place of death, country of residence, headquarters, etc.), Associated Groups, Gender, and Associated Languages. I know this is way, way out of scope for your project, but I thought it might be useful to get it out there and have people start thinking about it. I work in a NACO library where we add loads of information like this to authority record in hopes that it will be used by a discovery system at some point in our lifetimes!

-          FL: I agree! It’s my understanding that the AS person model will be modified (before long?) to be compliant with EAC-CPF, providing a richer set of fields, such as those you mention.

FL: In my mind, AS might also benefit by reconsidering its treatment of preferred titles. I’d like to see an AS model that recognizes WEMI entities as a separate category of related entity. For the moment, preferred titles without an author can be mapped well enough to AS Subject, of type “preferred title” – though the AS subdivisions for subjects don’t work particularly well for titles. For related works that do have an author, I’m not sure what to do. Smoosh them in to an AS subject too (preferred title)? Otherwise, when linking to a work (as subject), we are left to enter the name as a controlled entry in a resource description, with the title dangling as an uncontrolled subdivision (of type “preferred title”)– by which practice we lose benefits of treating the whole name/title as a related entity/authority.

Best regards,

Karen

Karen D. Miller

Monographic Cataloger/Metadata Specialist

Northwestern University Libraries

Northwestern University

1970 Campus Drive

Evanston, IL 60208

www.library.northwestern.edu<http://www.library.northwestern.edu>

k-miller3 at northwestern.edu<http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>

874.467.3462

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>] On Behalf Of Lapka, Francis

Sent: Thursday, April 06, 2017 3:23 PM

To: archivesspace_users_group at lyralists.lyrasis.org<http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>

Subject: [Archivesspace_Users_Group] LCNAF plugin

As part of a larger project concerning agent and subject records in ArchivesSpace, a group at Yale has drafted changes we'd like to see in the LCNAF plugin (to be coded by a vendor for use at Yale). The spec is outlined here:

https://drive.google.com/open?id=1_Jt0_5_9uuu-YexjfIdzTQEuJo2GjQ88no8WxHBXPlI<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-3Fid-3D1-5FJt0-5F5-5F9uuu-2DYexjfIdzTQEuJo2GjQ88no8WxHBXPlI&d=DwMFAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=P54V6LrXJP5Ddzc8ZItBdqB1Kr3elvFIQ04P7n0UCbQ&m=zS5homH5OTG72slKBPW59J87PR6_v4APDiUa9YxTyeU&s=JHEsLLF3jpBuJNnrqJ39FTpy_1fhcb0fXh0vcM9WOrU&e=<https://drive.google.com/open?id=1_Jt0_5_9uuu-YexjfIdzTQEuJo2GjQ88no8WxHBXPlI%3Chttps://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-3Fid-3D1-5FJt0-5F5-5F9uuu-2DYexjfIdzTQEuJo2GjQ88no8WxHBXPlI&d=DwMFAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=P54V6LrXJP5Ddzc8ZItBdqB1Kr3elvFIQ04P7n0UCbQ&m=zS5homH5OTG72slKBPW59J87PR6_v4APDiUa9YxTyeU&s=JHEsLLF3jpBuJNnrqJ39FTpy_1fhcb0fXh0vcM9WOrU&e=>>

There are three tabs. Text in red indicates changes to existing performance of the plugin (except for the third tab - where we propose an entirely new mapping for lcgft).

Some of what we propose may not be universally desired (e.g., using the LC authority URI as AS AuthorityID). Other changes probably ought to be incorporated in the LCNAF plugin for all (e.g., don't create separate AS subject *records* for each variant form in an LCSH record).

We welcome your corrections, suggestions, or other thoughts.

Thanks,

Francis

Francis Lapka  *  Catalog Librarian

Dept. of Rare Books and Manuscripts

Yale Center for British Art

203.432.9672<tel:%28203%29%20432-9672>  *  francis.lapka at yale.edu<http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group><mailto:francis.lapka at yale.edu<http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>>

Francis Lapka  ·  Catalog Librarian
Dept. of Rare Books and Manuscripts
Yale Center for British Art
203.432.9672<tel:%28203%29%20432-9672>  ·  francis.lapka at yale.edu<mailto:francis.lapka at yale.edu>

_______________________________________________
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170412/a6b41279/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 4144 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170412/a6b41279/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 1497 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170412/a6b41279/attachment-0001.jpg>