Add Facets for Concept Class Data Type

[roamye]

Problem Description: A facet to filter for Concept data types in Simple Search or Advanced Search does not currently exist.

Expected Behavior/Solution: Create facet/results for the Concept scope and all its values in both Simple and Advanced Search. These results will pull from the "Type" listed in each JSON concept record.

Example of record with Currency Type:

{
"id": "https://lux-front-tst.collections.yale.edu/data/concept/7ecf94c6-ab59-4814-a16d-d7fd6776f1b8",
"type": "Currency",
"_label": "shilling",
"broader": 

Requirements: The following values will pull from the Type listed in the JSON concept record.

• Value: Measurement Unit - 'Measurement Unit' (units such as cm, inches, etc)
• value: Language - 'Language'
• value: Material - 'Material'
• value: Currency - 'Currency'
• value: General Concept - 'Type' (Looks at all other concepts which do not fall under the other four values)
• When a user selects any value in Simple or Advanced Search the appropriate search results will appear under the Concept tab.
• Help Text will be added for the selection of each Concept class value:
  • Concept Class: Search for records categorized as either a "Measurement Unit", "Language", "Material", "Currency" or a "Genera Concept".
  • Measurement Unit: Search for Concepts that are used as the unit of a measurement, such as inches, seconds, kilograms or bytes.
  • Language: Search for Concepts that represent human-spoken languages, such as English, Spanish or Latin.
  • Material: Search for Concepts that represent a class of physical material, such as bronze, paper, or agate.
  • Currency: Search for Concepts that represent monetary currencies, such as dollars, euros, or francs.
  • General Concept: Search for Concepts that represent more general ideas or subjects, which excludes the more specific classes of Measurement Unit, Language, Material, and Currency

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

• ~[ ] Wireframe/Mockup - Mike~
• [x] Committee discussions - Sarah
• [x] Feasibility/Team discussion - Sarah
• [x] Backend requirements - TBD
• ~[ ] Frontend requirements- TBD~
• [x] ~Are new regression tests required for QA - Amy | Yes~
• [x] Questions
• List of questions for discussions. Answers should be documented within the issue.

UAT/LUX Examples:

• Please see FE ticket for UAT examples. | https://github.com/project-lux/lux-frontend/issues/176

Dependencies/Blocks:

• Blocking/Dependent On: https://github.com/project-lux/lux-frontend/issues/176

Related Github Issues:

Related links:

~Wireframe/Mockup:~ ~Place wireframe/mockup for the proposed solution at end of ticket.~

[clarkepeterf]

@prowns @roamye @jffcamp This is what I have for Advanced Search field name and help text:

field name: Concept Class help text: Search for Concepts only of a certain class

Is this right?

[roamye]

Concept class help text has been added into the ticket above with the same format as discussed in 6/21 it meeting. @clarkepeterf

[roamye]

@clarkepeterf - is there another way to test these tickets? the FE tickets are not a part of this milestones and that is listed as our current UAT.

[roamye]

Approved by UAT - however this tix will be closed on the 07/08 cycle when the FE can be tested.