Harmonize URI entries (full URI vs. ID) in ASpace subjects and agents

[fordmadox]

Example (discrepency):

<subject altrender="topical" authfilenumber="https://id.loc.gov/authorities/subjects/sh00005753" source="lcsh">Fishing</subject>
<subject altrender="topical" authfilenumber="sh85096176" source="lcsh">Outrigger canoes</subject>

To do:

1. We have decided to keep the approach of just storing the "ID", not the full URI in Aspace. Because of that decision, we will (eventually) need to make changes to the LCNAF and SNAC plugins. For LCNAF, we don't want the LCCN number, but instead the normalized LCCN (e.g., no spaces). For SNAC, we don't want the full URIs, but instead the last part of the ID that contains the ID, with a specific source (e.g. SNAC Ark vs. SNAC ID).

• Also compare SNAC plugin vs. LCNAF plugin, etc.
  • Testing Stipe, Michael for SNAC returns full URI including https and ARK (http)
  • Testing Stipe, Michael for LCNAH returns only identifier number, not full URI

2. Update values in database according to scheme determined in step 1
3. If the base URI is kept separate, add those base URIs to the (transparent) transformation pipeline.

For lots of strange errors / inconsistencies to review:

https://aspacetest.si.edu/agents/agent_person/247458 (LCNAF import... check out the issue with the 024 fields!)
https://aspacetest.si.edu/agents/agent_person/247457 (SNAC import, which goes with the full URI).

*06-01-2024: This is likely to be influenced by Amanda's work with URIs in ASpace and Keri's work looking through Women's History Initiative's spreadsheet

Also see ASpace list serve post (from 2025-01-16): https://groups.google.com/a/lyrasislists.org/g/Archivesspace_Users_Group/c/Cllvbfoiywo