Links to online finding aids mentioned in mapped 856s should be provided in oai_marc and marc21.xml exports

Description

In both the oai_marc OAI-PMH feed and marc21.xml exports/reports, the records include the following:

<datafield ind1=" " ind2=" " tag="555">
<subfield code="a">Finding aid online:</subfield>
</datafield>

<datafield ind1="4" ind2="2" tag="856">
<subfield code="z">Finding aid online:</subfield>
</datafield>

Shouldn't these include links to the finding aids? Something like https://findingaids.library.utc.edu/resources/4?

A better way to mark up this data might be the following.

<datafield ind1="4" ind2="2" tag="856">
<subfield code="z">Finding aid online:</subfield>
</datafield>
<datafield ind1="4" ind2="2" tag="856">
<subfield code="y">https://findingaids.library.utc.edu/resources/4</subfield>
</datafield>

I'm not a MARC expert, so it would be awesome if a trained cataloger could review this suggestion.

Environment

None

Activity

Show:
Manny Rodriguez
May 1, 2018, 6:17 PM

Cory, that makes sense – I've submitted a pull request exporting notes with type "Other Finding Aids" to a 555.

I've left the 555 export from the "Finding Aid Note" field from the Finding Aids section, but that can be easily removed if necessary.

https://github.com/archivesspace/archivesspace/pull/1230

Cory Nimer
May 2, 2018, 6:33 PM

, thanks for your work on this. Reviewing the comment by , though, I would agree that we should pull the Finding Aid Note field export, and limit the 555 to Other Finding Aids.

Manny Rodriguez
May 10, 2018, 8:43 PM

I've updated the pending pull request (https://github.com/archivesspace/archivesspace/pull/1230) to remove the Finding Aid Note export, so 555 tags are only created for Other Finding Aids.

One thing that came up is that the existing code to process note exports only allows for a single subfield. Changing this would likely require significant effort to refactor this code.

I discussed this with Christine, and she suggested putting the note contents into subfield '3', since 'u' is for URLs and the content in the note might not be a URL.

Cory Nimer
May 10, 2018, 11:13 PM

Since it is only possible to have a single subfield, looking at the pull request I think it would actually be better to not insert the subfield $3 and place the note content in a subfield $a. Subfield $3 in MARC is basically for a label, specifying what portion of a work the note relates to--which doesn't really fit for putting in generalized note content. This will probably result in notes that include a URL, like:

<datafield tag="555" ind1="0" ind2=" "><subfield code="a">File-level index available online. http://files.lib.byu.edu/ead/XML/UA1086.xml</subfield></datafield>

However, if there is no way of transforming in-line tagging into MARC coding on export, then stripping it out and placing the full string in a subfield $a note seems preferable.

Manny Rodriguez
May 17, 2018, 10:12 PM

Cory, I've created a new PR to put the note content in $a rather than $3: https://github.com/archivesspace/archivesspace/pull/1240

Assignee

Manny Rodriguez

Reporter

Carolyn Runyon

Priority

Minor
Configure