Data Constant Issue for Item Type Icons (from 1175)

[gigamorph]

Problem Description: The frontend wants to add icons for different item types. We need a list of AATs for Item Type to identify which icons should be used.

May be affect by our new way of handling data constants:

54

Expected Behavior/Solution: Data constant is created for new Item Types.

Requirements/UAT Links: From the AAT values , Icons will match to the correct Item Types and When the ticket is complete, data constants will exist for the following types:

UAT Links Collections Software & Electronic Media Textual Works Scores and Notation Object Record Cartography Numismatics Specimens Audio Video Visual Works Clothing Journals & Newspapers Furniture record Photographs

Needed for promotion: If an item on the list is not needed, it should be crossed off but not removed.

- [ ] Wireframe/Mockup - Heather

• [x] Committee discussions - Sarah
• [x] Feasibility/Team discussion - Sarah
• [x] Backend requirements - TBD
• [x] Frontend requirements- TBD
• [x] Questions
• List of questions for discussions. Answers should be documented within the issue.

~UAT/LUX Examples:~

• ~Example endpoints from LUX to use for development and testing, if applicable.~

Dependencies/Blocks:

• Blocking: https://github.com/project-lux/lux-frontend/issues/40
• ~Blocked by: new data set~ No longer blocked as of 4/11

Related Github Issues:

• https://git.yale.edu/lux-its/lux-web/issues/1776
• https://github.com/project-lux/lux-marklogic/issues/59 (Dupe)

Related links:

[ar2674]

Added all info from #59 into this ticket. @clarkepeterf @prowns

[roamye]

there will be a new data set soon where we will no longer use the data constants but instead AATs. The issue will need to be re-formatted. It will be blocked until the new data set is available.

[roamye]

No longer blocked by new data set

[roamye]

need to clarify this with @clarkepeterf.

[roamye]

Musical notation: https://lux-front-sbx.collections.yale.edu/data/object/18e97a66-9b83-46d8-a79d-9d0fa063e311

[prowns]

@clarkepeterf and @clarkepeterf - the suggestion is to close this in favor of #54 . Can you please confirm that?

@roamye - once this ticket it closed, I believe 54 is no longer blocked.

[prowns]

Ok to close per team meeting 4/18.