Add support for caused_by data point

[kamerynB]

Problem Description: The data contains a property called caused_by that is not being rendered.

Expected Behavior/Solution: Add support for the caused_by data point.

Requirements:

• [ ] Add a function in the event parser for extracting the data with its corresponding classified_as data point as its label
• [ ] Add react component for rendering

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

• [x] Wireframe/Mockup - Kam
• [x] ~Committee discussions - Sarah~
• [x] ~Feasibility/Team discussion - Sarah~
• [x] ~Backend requirements - TBD~
• [x] Frontend requirements - Kam
• [ ] Are new regression tests required for QA - Amy
• [x] ~Questions~

UAT/LUX Examples:

• https://lux-byunit1.collections.yale.edu/view/visual/1fb5f518-043c-4718-a19d-e341a2312a47

Dependencies/Blocks: N/A

Related Github Issues:

• FE: https://github.com/project-lux/lux-frontend/issues/324

Related links:

• Bugherd: https://www.bugherd.com/projects/284041/tasks/2402

Wireframe/Mockup: Current:

Expected:

[roamye]

• Mockup should not say contributor, it should have another label such as "Caused By".
• The title also does not make sense for what is written in the problem/expected behavior. Title says carried_out and problem says caused_by.
• need a better UAT example that is not from YCBA exhibitions. Such as: https://lux-front-tst.collections.yale.edu/view/text/614f2504-a240-4720-8e2a-d87d9bf7eb5f

Brewer's example: https://lux.collections.yale.edu/data/text/614f2504-a240-4720-8e2a-d87d9bf7eb5f

Needs to be updated. @kamerynB

[kamerynB]

After discussion in the 8/7 team meeting, the label should be "Caused By", not "Contributors".

[prowns]

UAT: Blocked. Need to update labeling recommendation and mockup from 8/22 Data mtg. Share with YUL/Data members to confirm, then proceed with work.

Notes from Data meeting:

• The creation of this work was caused primarily by this event, but the work was also caused by (additionally caused by) this event.

• These are neither creator nor contributor roles; they are causative. And there is a priority to this.

@roamye - can you create a new mockup for https://lux.collections.yale.edu/view/text/614f2504-a240-4720-8e2a-d87d9bf7eb5f that includes the following new section?

Creation Caused By | Events | Brewers' Industrial Exhibition (1876 : Philadelphia) ........................................ | Additional Events | Centennial Newspaper Exhibition (1876 : Philadelphia, Pa.)

[azaroth42]

Could we also try: Creation Resulted from Event: Additional Events:

Thanks!

[roamye]

@prowns -

@azaroth42 -

Was unsure of the placement so I put it under Language for now. This was made from the record: https://lux.collections.yale.edu/view/text/614f2504-a240-4720-8e2a-d87d9bf7eb5f

[prowns]

@kamerynB - do you know whhere this will be placed?

[azaroth42]

Sarah's version doesn't work because there could be additional information about people, places and times.

It would need to be:

Creation
                      Caused by Event:     Brewers
                      Additional Events:   Centennial

[roamye]

@prowns & @azaroth42 - do we know which version we would want to do? If it is Sarah's I can re-update it. If not, I can just leave the screenshots above as is for now.

[prowns]

@roamye - please use Rob's version.

[kamerynB]

@azaroth42 Your example in the comment here isn't feasible with how the data is returned. What property is the frontend looking for to determine the labels? Or is it just based on the order they are parsed? The classified_as properties do not clarify this either.

[azaroth42]

classified_as -- creator = the first one, contributor = the others

[kamerynB]

@azaroth42 As we are not using data constants anymore and to prevent the frontend from requiring an extra API call, the corresponding /classified_as should have a nested equivalent with the appropriate AAT values. In this example, there are no AATs for each /part[index]/classified_as.

[roamye]

A data pipeline issue will need to be created as it is blocking this ticket. Will have to move it to the next milestone (not 09-09).

Promoting as blocked and rob's mockups can replace the ones above.

[kamerynB]

Thank you all!