Fix front end and hierarchy rendering issues.

[roamye]

Problem Description:

2. records are not re-rendering so it will show incorrect data under parents/children when going back to a previous record.

3. Show More/Show Less button is showing even when there are only 5 parents

4. ~The explore record renders parent/childrens label when data does not exist.~ (has been moved to 332)
   ~For the Concept record Andy Warhol, 1928-1987 the explore section shows "Parents" but does not list any of it underneath it. This happens in all env.~ ~Additionally, if you click on the component term exhibitions and click return then the original record now lists incorrect information under the explore section. However it still does not list any parent information.~ ~This ticket serves as a research ticket to figure out why this is happening and to propose a potential solution.~

Expected Behavior/Solution:

• Issue 2: have the hierarchy records re-render when going back and forth to different records.
• Issue 3: the Show More/Show Less button will not render when there are 5 or less parents
• ~Issue 1: the explore section should not render information when parent/child data does not exist.~ (moved to 332)

Requirements:

• [x] Issue 2: hierarchy records in the explore section will re-render to show the correct information of a previous record.
• [x] Issue 3: Remove button is parents.length is less than or equal to 5
• [x] ~Issue 1: any record with an explore section will not render parent/child information if it does not exist~ moved to 332

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

• [x] Wireframe/Mockup - Mike
• [x] Committee discussions - Sarah
• [x] Feasibility/Team discussion - Sarah
• [x] Backend requirements - TBD
• [x] Frontend requirements - Kam
• [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: Issue 2:

• View Tepelenë
• Select the parent entity Gjirokastër
• Hit the back button in the browser
• The hierarchy rendered when going back to Tepelenë should be its own and not the hierarchy for Gjirokastër

Issue 3:

• https://lux-front-tst.collections.yale.edu/view/place/9f0772aa-e75e-490c-8f4d-5b2ccd41162a
• • Explore widget doesn't display Show More under Parents
• PRD: https://lux.collections.yale.edu/view/place/9f0772aa-e75e-490c-8f4d-5b2ccd41162a
• • • Explore widget does display Show More under Parents

~Issue 1:~

• ~https://lux-front-dev.collections.yale.edu/view/concept/684a5568-f2fc-42f6-a339-eaa1fa7635b4~ (moved to #332)

Dependencies/Blocks: N/A

Related Github Issues: N/A

Related links:

• Bugherd: https://www.bugherd.com/projects/284041/tasks/2348
• Bugherd: https://www.bugherd.com/projects/284041/tasks/2390
• Bugherd: https://www.bugherd.com/projects/284041/tasks/2436

Wireframe/Mockup: Current Issue 2: Expected Issue 2:

Current when there are 5 parents:

Expected:

[roamye]

There are two different issues happening in this ticket. 1) parent information not rendering 2) explore information rendering on original page when you select a new page and go back to it.

I was unsure if these issues are related to each other so I put them both on here. If you would like them to be separate let me know and I can separate them.

@kamerynB

[kamerynB]

@roamye

1. There is no parent information in the record (found in the /broader property in the JSON). The frontend issue is then that it should not render the hierarchy component if there are no parents and children.
2. That looks like a rendering issue on the frontend. That hierarchy component isn't being re-rendered upon going back.

The 2 issues are unrelated, as fixing one will not impact the other. However, the second one is a simple fix. I just tested it locally and it involves changing one line of code. They can be completed in one GH issue.

[roamye]

These will need to be separated into three issues. 1 important 2/3 critical (8/7 UAT)

[kamerynB]

@roamye These issues can remain as one issue. I will tackle them together. I would mark this issue as Critical if the majority are considered critical.

[roamye]

@kamerynB - I created this ticket: https://github.com/project-lux/lux-frontend/issues/332, it tackles the first issue on 297 and includes its separate UAT.

[roamye]

2. looks good in prod.
3. looks good in prod. Closing.