Should we index and display <archref> ?

[marlo-longley]

archref

Duke has some formatting / code for reference -- is this solution applicable to core?

This ticket is broken out from #898

[seanaery]

We would be happy to PR our Duke solution for archref elements if applicable/agreeable to the community. See format_archrefs:

https://gitlab.oit.duke.edu/dul-its/dul-arclight/-/blob/main/app/helpers/ead_format_helpers.rb#L35
https://gitlab.oit.duke.edu/dul-its/dul-arclight/-/blob/main/app/helpers/ead_format_helpers.rb#L42-65

As @mmmmcode noted, we commonly use <archref> to wrap references to other finding aids, especially within <relatedmaterial>, whether at Duke or elsewhere. Within the tag, there can be additional EAD formatting like <extref> with URLs (see related ticket #1449 ).

<archref>s can technically appear a lot of places -- e.g., one might be isolated within a random note field on a component or there might be several listed consecutively, especially in a collection's <relatedmaterial> section.

Examples in action:
https://archives.lib.duke.edu/catalog/harrisrencher#related
https://archives.lib.duke.edu/catalog/bingham#related
https://archives.lib.duke.edu/catalog/behindtheveil#related