Map visualization for entity pages (from 1873)

[gigamorph]

Problem Description: Map visualizations is a desired feature to be added into LUX entity pages, specifically for the Related Locations data in the: People, Work, Places, Events and Concept pages.

LUX has a requirement for visualizations. The existing/original wireframes show this: https://nj46vq.axshare.com/#id=63klng&p=entity_-_person_group&g=1. BUT both wireframes and requirements will need to be updated. ~We also need requirements and designs for visualizations.~

Expected Behavior/Solution:

• Render locations using a visualization and improve the list view for places.
• Breaking out list view to https://git.yale.edu/lux-its/lux-web/issues/1872
• Map visualization feature will be offered for the data/relationships listed in the Related Location accordion found in the People, Work, Places, Events and Concept pages.
• Drop down options for the selection of the related location, relationship, work/object/any type will be available for the features.
• Map visualization will populate/appear after the selection for each drop down options are submitted.

Requirements: On Entity Pages

• Separate box for the Related locations/Map visualization will appear on applicable g&p, events, concepts and places pages.
• ~The button "Show on Map" will be available on the Related Location's accordion.~
• Map feature will display warning text, and drop down options for selection of 1) locations, 2) relationships, and 3) objects/works/any

Map Feature

• Will live within it's own space within the pages ~Related Locations accordion.~ (TBD)
• Title, warning text, and drop down options will be visible.
• Map visualization will appear once a user has selected the submit button.
• Title will display in black font at the top right corner as "Visualize maps with..." (TBD)
• Warning text will display underneath the title as: Not all combinations of data available for each drop down can be plotted on the map. (TBD)
• 3 Drop down options will display under the warning text such as:
  • ~Have Related locations and~ Have Relationship and Are Categorized As (similar to Advanced Search)
  • each drop down option will have all values available for the entity page a user is in.
  • a user will be able to select more than one relationship/ more than one are categorized as (TBD based on interactions. How important is it for a user to see more than one relationship?)
• A submit button will be available at the end. (View on Map)

Map Visualization

• Will display colored dots over the locations selected which signify the relationships/categorized as selected by the user.
• Selection of Color will unhighlight/highlight the dots within the map. (Need to discuss with Kam if possible. TBD - can only toggle on or toggle off. Possibly? )

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
• [ ] Are new regression tests required for QA - Amy
• [ ] Questions
• List of questions for discussions. Answers should be documented within the issue.

UAT/LUX Examples:

• Person Example: https://lux-front-tst.collections.yale.edu/view/person/c225d5e4-8767-4a25-802b-af054d5e8f52
• Example with no mapping/tile information: https://lux-front-tst.collections.yale.edu/view/place/50fb5e2c-082a-4121-884d-9ca4a763f8b8

Dependencies/Blocks: N/A

Related Github Issues: N/A

Related links:

• original requirements and wires for mapping in LUX: https://docs.google.com/document/d/1EWZXuEE3QGKY9ygDEZ1limYwC7V6mF4VY2r59jv6yO4/edit
• meeting notes 08/13: https://docs.google.com/document/d/1v2C_UDnxUfA0RD3SkPtDS1emiAjVw87Ua_vemOlQ8BM/edit

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

[kamerynB]

I'd really like to know if this is still wanted and if so, I would like to have the following questions discussed.

1. What is the goal of this?
2. Are the original wires still valid?
3. How will the user interact with the map? a. How will the user be shown search links? b. How do we handle polygon coordinates?

I'd also love to revisit the What We Have visualization. We have that data rendered as Object Types and Work Types accordions at the moment. At least that is how I remember it. With Recharts, the library being used for the timeline graph, I'm confident this can be implemented pretty easily.

@prowns @jffcamp @roamye

[prowns]

Next steps:

• define data/UX requirements (where are the situations in the data where a map aggregating multiple data points would be valuable. Multiple relationships; multiple places). What would it look like given the data we have.
• wires
• feasibility

[roamye]

(UAT meeting 5/29) @kamerynB

2. Are the original wires still valid? Answer: No, we would need to create new wires and figure out the use cases of where this map would appear/what kind of data is useful for users.

@miketullo95 - Based on SP comment above, we would need new UX requirements.

[prowns]

Update: plan is for @roamye to start compiling requirements with Heather/Mike/Team

[roamye]

Map Visualization Meeting:

• Amy to write up req's for above and @dcheather to create mockups for the initial proposal of the map feature. | Notes

IT Team Meeting 8/16: Discussed feasibility issues. Pagination is the main concern if we want to show data all at once. Leaflet can handle what we need but may be very costly. Possible solutions: Could build a related list that builds the relationship that exists when a user selects. The pagination concern can be better addressed once we see / have some kind of demo.

[roamye]

@dcheather - I added the requirements above. Let me know if you have any questions.

[kamerynB]

I would actually vote for Related Locations to become its own component, much like the timeline or hierarchy.

@roamye @dcheather