Re: [Archivesspace_Users_Group] LCNAF plugin

[Jared Hutchens]

Hi Nigel,

We recently resolved an issue with the LCNAF plugin failing to give any
results (running v3.1). In our case it was due to the plugin files being
incomplete, several lines were missing which I added back referencing
Github build. Not sure if that's the issue you're facing but I hope this
helps.

Thanks,
Jared




Jared Hutchens

Library Technology Specialist

Nicholson Library

o: (765) 641-4270

https://library.anderson.edu

This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this email. Please notify the sender
immediately by email if you have received this email by mistake and delete
this email from your system.


On Sun, Dec 4, 2022 at 9:10 PM Nigel Bond  wrote:

> Hi all,
>
> We have recently upgraded to AS 3.3.1, and all seems to working fine apart
> for the Library of Congress LCNAF plugin.
>
> We are not sure whether we still need to use a plugin, or if it is now
> embedded in the new version of AS.
>
> Can anybody please assist us, in advising how we get this to work.
>
>
>
> Thank you in advance.
>
>
>
> Nigel Bond
>
>
>
> *Dr. Nigel Bond (he/him)*
>
> *Team Leader*
>
> Cultural Collections (Special Collections)
>
> Waipapa Taumata Rau, University of Auckland
>
>
>
> *Special Collections: Celebrating 20 years*
>
>
>
>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] LCNAF plugin

[Nigel Bond]

Hi all,
We have recently upgraded to AS 3.3.1, and all seems to working fine apart for 
the Library of Congress LCNAF plugin.
We are not sure whether we still need to use a plugin, or if it is now embedded 
in the new version of AS.
Can anybody please assist us, in advising how we get this to work.

Thank you in advance.

Nigel Bond

Dr. Nigel Bond (he/him)
Team Leader
Cultural Collections (Special Collections)
Waipapa Taumata Rau, University of Auckland

Special Collections: Celebrating 20 years

[cid:image001.png@01D908BB.B40C1EA0]

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] lcnaf plugin

[Tom Hanstra]

Thanks. That helps a lot. I figured history factored in as it always does
with these kinds of things. But coming in cold, it is especially confusing
now that I know there are two versions. I'll assume that the included
version is sufficient until someone here says differently.

It would help if this was documented a bit more. A simple "README" file in
the lcnaf GitHub repository mentioning that it is an even more enhanced
version of the included version and explaining the differences would go a
long way in explaining the situation. I'm not sure who maintains that code,
but it certainly would have helped me.

And thanks for pointing me to the wiki. It looks like I'm going to have to
do some perusing of that in addition to the tech docs in order to really
understand how to support this software.

Tom


On Thu, May 20, 2021 at 3:13 PM Christine Di Bella <
christine.dibe...@lyrasis.org> wrote:

> Hello Tom,
>
>
>
> The LCNAF plugin is a very rare case in that it’s both bundled with the
> standard ArchivesSpace application and, because of its popularity, lives on
> its own in case it needs to be updated between our releases due to changes
> in LC’s service. The program team has discussed doing only one or the other
> because it is undeniably duplicative for code maintainers and confusing for
> users (though, on the users side, most people use the one that comes
> bundled with ArchivesSpace and don’t realize there is a separate one). The
> functionality of both LCNAF plugins is identical. For now we’ve continued
> to keep it the way it is pending some larger discussions.
>
>
>
> Virtually all other plugins only live on our their own, and most plugins
> are authored by and maintained by community members, not the ArchivesSpace
> program. The community-maintained Awesome ArchivesSpace list links to a lot
> of great ones: https://github.com/archivesspace/awesome-archivesspace.
>
>
>
> For some additional context, there’s some information about plugins and
> considerations for turning a plugin into core code at
> https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/916062227/Making+a+Plug-In+part+of+the+Core+Code.
> That document also links to an outline of an evaluation process for
> considering feature contributions, including whether something might best
> be handled as a plugin:
> https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/360546309/ArchivesSpace+Process+for+Evaluating+Potential+Feature+Contributions+to+the+Core+Code
> .
>
>
>
> I hope this helps. If you have other questions, please let us know.
>
>
>
> Christine
>
>
>
> Christine Di Bella
>
> ArchivesSpace Program Manager
>
> christine.dibe...@lyrasis.org
>
> 800.999.8558 x2905
>
> 678-235-2905
>
>
>
>
>
> [image: ASpaceOrgHomeMedium]
>
>
>
>
>
>
>
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> *On Behalf Of *Tom
> Hanstra
> *Sent:* Thursday, May 20, 2021 12:23 PM
> *To:* Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] lcnaf plugin
>
>
>
> Ok, so I did not see that lcnaf was included in ArchivesSpace right from
> the beginning. I thought I had to get the files from GitHub as I would with
> other plugins, but I see that they are there. In fact several are there.
>
>
>
> So I need to revise my overall question to:
>
>
>
> - Why is some code added to the zip file but left as a plugin while other
> code is added to the software?
>
>
>
> In this instance, lcnaf is there but I need to update the config file to
> turn it on. With other plugins, I have to get the files from somewhere else
> and turn them on. And maybe do more than just put them in the directory
> (for instance, oauth needs to be compiled). How is it determined what goes
> where and how it is or is not included?
>
>
>
> Sorry, but this is rather confusing to the newbie.
>
>
>
> Thanks
>
> Tom
>
>
>
> On Thu, May 20, 2021 at 10:51 AM Joshua D. Shaw <
> joshua.d.s...@dartmouth.edu> wrote:
>
> Hi Tom
>
>
>
> To enable any plugin in the /plugins directory, you need to update the
> config file. Specifically, the entry
>
>
>
> AppConfig[:plugins] = []
>
>
>
> The array contents are just the directory names of the plugins that you
> want to enable
>
>
>
> So, to enable just the lcnaf plugin, you would want
>
>
>
> AppConfig[:plugins] = ['lcnaf']
>
>
>
> https://archivesspace.github.io/tech-docs/ is a good resource.
>
>
>
> jds
>
>
> --
>
> 

Re: [Archivesspace_Users_Group] lcnaf plugin

[Christine Di Bella]

Hello Tom,

The LCNAF plugin is a very rare case in that it’s both bundled with the 
standard ArchivesSpace application and, because of its popularity, lives on its 
own in case it needs to be updated between our releases due to changes in LC’s 
service. The program team has discussed doing only one or the other because it 
is undeniably duplicative for code maintainers and confusing for users (though, 
on the users side, most people use the one that comes bundled with 
ArchivesSpace and don’t realize there is a separate one). The functionality of 
both LCNAF plugins is identical. For now we’ve continued to keep it the way it 
is pending some larger discussions.

Virtually all other plugins only live on our their own, and most plugins are 
authored by and maintained by community members, not the ArchivesSpace program. 
The community-maintained Awesome ArchivesSpace list links to a lot of great 
ones: https://github.com/archivesspace/awesome-archivesspace.

For some additional context, there’s some information about plugins and 
considerations for turning a plugin into core code at 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/916062227/Making+a+Plug-In+part+of+the+Core+Code.
 That document also links to an outline of an evaluation process for 
considering feature contributions, including whether something might best be 
handled as a plugin: 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/360546309/ArchivesSpace+Process+for+Evaluating+Potential+Feature+Contributions+to+the+Core+Code.

I hope this helps. If you have other questions, please let us know.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Tom 
Hanstra
Sent: Thursday, May 20, 2021 12:23 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] lcnaf plugin

Ok, so I did not see that lcnaf was included in ArchivesSpace right from the 
beginning. I thought I had to get the files from GitHub as I would with other 
plugins, but I see that they are there. In fact several are there.

So I need to revise my overall question to:

- Why is some code added to the zip file but left as a plugin while other code 
is added to the software?

In this instance, lcnaf is there but I need to update the config file to turn 
it on. With other plugins, I have to get the files from somewhere else and turn 
them on. And maybe do more than just put them in the directory (for instance, 
oauth needs to be compiled). How is it determined what goes where and how it is 
or is not included?

Sorry, but this is rather confusing to the newbie.

Thanks
Tom

On Thu, May 20, 2021 at 10:51 AM Joshua D. Shaw 
mailto:joshua.d.s...@dartmouth.edu>> wrote:
Hi Tom

To enable any plugin in the /plugins directory, you need to update the config 
file. Specifically, the entry

AppConfig[:plugins] = []

The array contents are just the directory names of the plugins that you want to 
enable

So, to enable just the lcnaf plugin, you would want

AppConfig[:plugins] = ['lcnaf']

https://archivesspace.github.io/tech-docs/ is a good resource.

jds


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Tom Hanstra mailto:hans...@nd.edu>>
Sent: Thursday, May 20, 2021 9:09 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] lcnaf plugin

Hi, ArchivesSpace users,

I continue my quest to get our site set up and have been told that I need to 
install the lcnaf plugin. I've got a few questions:

First, where is the documentation on how to install the plugin? The code in 
github does not have so much as a README file to give me information on how to 
install it. Do I just grab the code and plunk it into the plugins directory? Or 
is there more to be done?

Second, how does ArchivesSpace decide what plugins get pulled into code and 
which do not. This one, from what I can tell, has been around for a long time 
and yet continues to be a plugin that is added after the fact. Yet other 
plugins have been added into the code. Just curious how that gets decided.

Thanks,
Tom

--
Tom Hanstra
Sr. Systems Administrator
hans...@nd.edu<mailto:hans...@nd.edu>

[https://docs.google.com/uc?export=download=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org<mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


--
Tom 

Re: [Archivesspace_Users_Group] lcnaf plugin

[Tom Hanstra]

Ok, so I did not see that lcnaf was included in ArchivesSpace right from
the beginning. I thought I had to get the files from GitHub as I would with
other plugins, but I see that they are there. In fact several are there.

So I need to revise my overall question to:

- Why is some code added to the zip file but left as a plugin while other
code is added to the software?

In this instance, lcnaf is there but I need to update the config file to
turn it on. With other plugins, I have to get the files from somewhere else
and turn them on. And maybe do more than just put them in the directory
(for instance, oauth needs to be compiled). How is it determined what goes
where and how it is or is not included?

Sorry, but this is rather confusing to the newbie.

Thanks
Tom

On Thu, May 20, 2021 at 10:51 AM Joshua D. Shaw 
wrote:

> Hi Tom
>
> To enable any plugin in the /plugins directory, you need to update the
> config file. Specifically, the entry
>
> AppConfig[:plugins] = []
>
> The array contents are just the directory names of the plugins that you
> want to enable
>
> So, to enable just the lcnaf plugin, you would want
>
> AppConfig[:plugins] = ['lcnaf']
>
> https://archivesspace.github.io/tech-docs/ is a good resource.
>
> jds
>
> --
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of Tom
> Hanstra 
> *Sent:* Thursday, May 20, 2021 9:09 AM
> *To:* Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> *Subject:* [Archivesspace_Users_Group] lcnaf plugin
>
> Hi, ArchivesSpace users,
>
> I continue my quest to get our site set up and have been told that I need
> to install the lcnaf plugin. I've got a few questions:
>
> First, where is the documentation on how to install the plugin? The code
> in github does not have so much as a README file to give me information on
> how to install it. Do I just grab the code and plunk it into the plugins
> directory? Or is there more to be done?
>
> Second, how does ArchivesSpace decide what plugins get pulled into code
> and which do not. This one, from what I can tell, has been around for a
> long time and yet continues to be a plugin that is added after the fact.
> Yet other plugins have been added into the code. Just curious how that gets
> decided.
>
> Thanks,
> Tom
>
> --
> *Tom Hanstra*
> *Sr. Systems Administrator*
> hans...@nd.edu
>
>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
*Tom Hanstra*
*Sr. Systems Administrator*
hans...@nd.edu
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] lcnaf plugin

[Joshua D. Shaw]

Hi Tom

To enable any plugin in the /plugins directory, you need to update the config 
file. Specifically, the entry

AppConfig[:plugins] = []

The array contents are just the directory names of the plugins that you want to 
enable

So, to enable just the lcnaf plugin, you would want

AppConfig[:plugins] = ['lcnaf']

https://archivesspace.github.io/tech-docs/ is a good resource.

jds


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Tom 
Hanstra 
Sent: Thursday, May 20, 2021 9:09 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] lcnaf plugin

Hi, ArchivesSpace users,

I continue my quest to get our site set up and have been told that I need to 
install the lcnaf plugin. I've got a few questions:

First, where is the documentation on how to install the plugin? The code in 
github does not have so much as a README file to give me information on how to 
install it. Do I just grab the code and plunk it into the plugins directory? Or 
is there more to be done?

Second, how does ArchivesSpace decide what plugins get pulled into code and 
which do not. This one, from what I can tell, has been around for a long time 
and yet continues to be a plugin that is added after the fact. Yet other 
plugins have been added into the code. Just curious how that gets decided.

Thanks,
Tom

--
Tom Hanstra
Sr. Systems Administrator
hans...@nd.edu<mailto:hans...@nd.edu>

[https://docs.google.com/uc?export=download=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] lcnaf plugin

[Hand, Sarit]

Hi Tom,

You can open a Jira Ticket.  Visit this page 
https://archivesspace.org/member-area/technical-support for details.

Cheers,
[cid:image003.png@01D74D5E.7E0D89C0]

Sarit Hand
Digital Archivist
AP Corporate Archives

200 Liberty Street
New York, NY 10281
T 212.621.7035

sh...@ap.org<mailto:sh...@ap.org>
ap.org<http://www.ap.org>
[cid:image004.png@01D74D5E.7E0D89C0]


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Tom 
Hanstra
Sent: Thursday, May 20, 2021 9:09 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] lcnaf plugin


[EXTERNAL]
Hi, ArchivesSpace users,

I continue my quest to get our site set up and have been told that I need to 
install the lcnaf plugin. I've got a few questions:

First, where is the documentation on how to install the plugin? The code in 
github does not have so much as a README file to give me information on how to 
install it. Do I just grab the code and plunk it into the plugins directory? Or 
is there more to be done?

Second, how does ArchivesSpace decide what plugins get pulled into code and 
which do not. This one, from what I can tell, has been around for a long time 
and yet continues to be a plugin that is added after the fact. Yet other 
plugins have been added into the code. Just curious how that gets decided.

Thanks,
Tom

--
Tom Hanstra
Sr. Systems Administrator
hans...@nd.edu<mailto:hans...@nd.edu>

[https://docs.google.com/uc?export=download=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ]
The information contained in this communication is intended for the use of the 
designated recipients named above. If the reader of this communication is not 
the intended recipient, you are hereby notified that you have received this 
communication in error, and that any review, dissemination, distribution or 
copying of this communication is strictly prohibited. If you have received this 
communication in error, please notify The Associated Press immediately by 
telephone at +1-212-621-1500 and delete this email. Thank you.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] lcnaf plugin

[Tom Hanstra]

Hi, ArchivesSpace users,

I continue my quest to get our site set up and have been told that I need
to install the lcnaf plugin. I've got a few questions:

First, where is the documentation on how to install the plugin? The code in
github does not have so much as a README file to give me information on how
to install it. Do I just grab the code and plunk it into the plugins
directory? Or is there more to be done?

Second, how does ArchivesSpace decide what plugins get pulled into code and
which do not. This one, from what I can tell, has been around for a long
time and yet continues to be a plugin that is added after the fact. Yet
other plugins have been added into the code. Just curious how that gets
decided.

Thanks,
Tom

-- 
*Tom Hanstra*
*Sr. Systems Administrator*
hans...@nd.edu
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] LCNAF plugin

[Karen Miller]

Francis,

We also have the problem of preferred titles that do have an author. For now, 
we've treated them by smooshing them into an Agent record, but I could see 
smooshing them into a Subject instead.

I see your point about mapping the 046 field to the Dates of Existence record; 
sometimes these differ in granularity from what's in the $d. Sometimes there is 
a 046 but no $d, and sometimes there is a $d but no 046so we really can't 
assume a one-to-one relationship.

Karen

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Lapka, Francis
Sent: Wednesday, April 12, 2017 12:52 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] LCNAF plugin

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=%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 tit

Re: [Archivesspace_Users_Group] LCNAF plugin

[Christine Di Bella]

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.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Cyndi Shein
Sent: Wednesday, April 12, 2017 2:12 PM
To: Archivesspace Users Group <archivesspace_users_group@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.sh...@unlv.edu<mailto:cyndi.sh...@unlv.edu> (702) 895-2223
[cid:image002.jpg@01D2B3A1.73D87D80]

On Wed, Apr 12, 2017 at 10:52 AM, Lapka, Francis 
<francis.la...@yale.edu<mailto:francis.la...@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=%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,

Re: [Archivesspace_Users_Group] LCNAF plugin

[Karen Miller]

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.

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.


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.



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!



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
k-mill...@northwestern.edu
874.467.3462




From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Lapka, Francis
Sent: Thursday, April 06, 2017 3:23 PM
To: archivesspace_users_group@lyralists.lyrasis.org
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=DwMFAg=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws=P54V6LrXJP5Ddzc8ZItBdqB1Kr3elvFIQ04P7n0UCbQ=zS5homH5OTG72slKBPW59J87PR6_v4APDiUa9YxTyeU=JHEsLLF3jpBuJNnrqJ39FTpy_1fhcb0fXh0vcM9WOrU=>

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  *  francis.la...@yale.edu<mailto:francis.la...@yale.edu>


___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] LCNAF plugin

[Lapka, Francis]

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  *  francis.la...@yale.edu


___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group