Update resource_type controlled vocabulary to LOC resource type URIs

[kirkkwang]

Story

The resource_type field currently uses plain-string controlled values from Hyku's default resource_types.yml (e.g. Article, Audio, Image). UTK needs this vocabulary replaced with URIs from the Library of Congress Resource Types vocabulary so that resource types are linked data rather than local strings.

The new vocabulary:

URI	Code
http://id.loc.gov/vocabulary/resourceTypes/art	Artifact
http://id.loc.gov/vocabulary/resourceTypes/aud	Audio
http://id.loc.gov/vocabulary/resourceTypes/car	Cartographic
http://id.loc.gov/vocabulary/resourceTypes/col	Collection
http://id.loc.gov/vocabulary/resourceTypes/dat	Dataset
http://id.loc.gov/vocabulary/resourceTypes/dig	Digital
http://id.loc.gov/vocabulary/resourceTypes/man	Manuscript
http://id.loc.gov/vocabulary/resourceTypes/mix	Mixed material
http://id.loc.gov/vocabulary/resourceTypes/mov	Moving image
http://id.loc.gov/vocabulary/resourceTypes/mul	Multimedia
http://id.loc.gov/vocabulary/resourceTypes/not	Notated music
http://id.loc.gov/vocabulary/resourceTypes/img	Still image
http://id.loc.gov/vocabulary/resourceTypes/tac	Tactile
http://id.loc.gov/vocabulary/resourceTypes/txt	Text

Acceptance Criteria

• User may configure an m3 profile so that metadata fields are clickable URLs (show page and catalogue results page)
  • On click, the user is brought to a faceted search for the selected metadata field term (label or URI, depending on the field configuration), the results of which shall include the work on which the field term was clicked.
• A knapsack-level config/authorities/resource_types.yml overrides Hyku's, containing exactly the 14 LOC URIs above as id values with human-readable term labels
• The m3 profile's resource_type controlled_values source resolves to the new authority
• Dropdown on all work type forms shows the human-readable labels
• Submitted values store the LOC URI, not the label
• Facet and search results display the human-readable label
• Existing records with old string values are addressed (migration plan or mapping documented)

Screenshots / Video

Testing Instructions and Sample Files

Notes

• Current authority lives at hyrax-webapp/config/authorities/resource_types.yml with 21 plain-string entries. The knapsack has no override yet.
• The m3 profile references source resource_types under controlled_values.
• LOC vocabulary base: http://id.loc.gov/vocabulary/resourceTypes/