search

yalelibrary / YUL-DC

Preliminary issue tracking for Yale University Libraries Digital Collections project
3 stars 0 forks source link

Finding Aid link #1171

Closed mikeapp closed 3 years ago

mikeapp commented 3 years ago

Story

Updates to Metadata Cloud will potentially return multiple Finding Aid links from Voyager records.

Blocked by MC ticket 260

Acceptance

mikeapp commented 3 years ago

Metadata Cloud ticket 260.

martinlovell commented 3 years ago

Some questions:

Should we leave FindingAid as is and add solr fields for RelatedResourceOnline and ResourceVersionOnline from ILS, then make sure those display properly with Titles and Links or just Links?

We still have finding aid as a show field in blacklight, so Aspace and LB records will still have link only finding aids in the standard show page. Aspace will also have the new archival finding aid link with the Collection Name as the text. (Voyager does not map finding aid anymore so it won't have that link).

Does it seem better to parse the two new MC fields on the management side and convert to HTML, a more consistent delimited value, or parallel arrays in Solr so that Blacklight can deal with it more easily? (Or index as is and parse on the Blacklight side?)

mikeapp commented 3 years ago

I would not convert it to HTML. I think indexing as-is and parsing in Blacklight would be fine.

martinlovell commented 3 years ago

Metadata cloud updates related to this ticket:

findingAid is always just a URL without a label. It will be one of more URLs in an array. This is already setup as a show field, but only displays the first URL when there are multiple URLs.

Added fields: relatedResourceOnline resourceVersionOnline

These need to be stored in Solr separately from the finding aid and will be multi-value. Store the values as they come from metadata cloud.

We need a show field for these two in blacklight. The values in the field are | (pipe) separated. The value should be split on "|" into components. After splitting on "|" parse the resulting parts to determine if they are URLs or labels by looking for an "http" prefix.

(Typically it will look like this: relatedResourceOnline: "View Related Resource|http://library.somewhere.com/special_page" )

If there is one link and one label, use the link and label to construct the link in the show field. If there is just one link, use the link only.

If there is more than 2 components after splitting on "|", or there are no link components, it's likely a cataloging error. In this case, should the show field not display?

mikeapp commented 3 years ago

If there is more than 2 components after splitting on "|", or there are no link components, it's likely a cataloging error. In this case, should the show field not display?

I agree.

martinlovell commented 3 years ago

Bib 11040744 does have a value for testing. (Also 2505801)

However, we were having some issues in metadata cloud getting these two fields. This is fixed in MC, but still needs to be deployed for production.

UAT and Test have this fix.

FCRodriguez7 commented 3 years ago

Blacklight PR: https://github.com/yalelibrary/yul-dc-blacklight/pull/614

Management PR: https://github.com/yalelibrary/yul-dc-management/pull/725

martinlovell commented 3 years ago

Using bib id 12244725 is interesting. It has multiple related resources with different labels.

image.png

FCRodriguez7 commented 3 years ago

Released management v2.45.13 Released blacklight v1.44.5