Problem Description:
There is a request to be able to link directly to an object page in LUX based on a unit-provided identifier. In this way, a unit will be able to construct a link to the item without knowing the LUX URI. (request from YUAG)
[ ] Create an index of only accession numbers (will be needed for YPM and other subsequent uses anyway)
[ ] Expose new field to advanced search (say identifier-accession)
[ ] Extend above query to use new field and AND with the unit to avoid identifier collisions
[ ] Create a little API that takes the accession number and code for the unit, calls the query, and redirects the caller to the object web page. e.g. lux.collections.yale.edu/api/object-redirect?identifier=1941.380&unit=yuag
gives a 302 redirect to https://lux.collections.yale.edu/view/object/2dbabf81-dd18-4794-9998-a883c1f6ae91
[ ] Then the units can embed: This object in LUX without knowing the UUID for it, and have the browser just do the right thing
Requirements:
Needed for promotion:
If an item on the list is not needed, it should be crossed off but not removed.
[ ] ~Wireframe/Mockup - Heather~
[ ] ~Committee discussions - Sarah~
[ ] ~Feasibility/Team discussion - Sarah~
[ ] Backend requirements - TBD
[ ] ~Frontend requirements- TBD~
[ ] Questions
List of questions for discussions. Answers should be documented within the issue.
Dependencies/Blocks:
Related Github Issues:
UAT/LUX Examples:
UAT is up to units when they implement.
Problem Description: There is a request to be able to link directly to an object page in LUX based on a unit-provided identifier. In this way, a unit will be able to construct a link to the item without knowing the LUX URI. (request from YUAG)
Example: Rather than using this link: https://lux-front-prd.collections.yale.edu/view/object/72c1ebe6-d0b4-4ac1-8632-19d854b2bcd9 A unit could call an API, pass unit code (YUAG) and Record Identifier/cmsid (126776), or whatever else would make it a unique call, and return that specific object page.
Expected Behavior/Solution:
Requirements:
Needed for promotion: If an item on the list is not needed, it should be crossed off but not removed.
Dependencies/Blocks:
Related Github Issues:
UAT/LUX Examples: UAT is up to units when they implement.