I'm sharing a set of related files that illustrate our desired outcomes (should have included this in the initial posting):
https://drive.google.com/drive/folders/0B6iyjeOLkTS9R2JIUXFleGNnNGM?usp=sharing You'll see that we want the plug-in to supply the "sort name" rather than have AS try to assemble it. This is especially necessary with complex headings. Our goal is to create a "sort name" that is an exact match for the authorized heading (including the form of punctuation); this is easy accomplished when we grab the form directly from the LC MARCXML. Happy to field other comments or questions. (NB. I initially sent this to the list last week, but I think it failed to post.) Best, Francis -- From: Lapka, Francis Sent: Thursday, April 06, 2017 4:23 PM To: '[email protected]' <[email protected]<mailto:[email protected]>> Subject: 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 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 * [email protected]<mailto:[email protected]>
_______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
