Create tabbed view for openindexmaps

[ewlarson]

Let's flush this idea out more. What would appear on the ItemViewer tab and what would appear on a secondary tab?

[karenmajewicz]

Here is an example to consider: https://geo.btaa.org/catalog/p16022coll247:83

This proposal

For the example item, the first tab would remain as is: a manifest viewer for a multipart atlas. The second tab would say "Index Map" and display the OpenIndexMap.

Current Scenario

Currently, the user can use the parent record to view the images. To see the index map, they would need to scroll down and see the "Derived Record" called "OpenIndexMap for Map of the Mississippi River : from Lake Itasca to the Falls of Saint Anthony"

Other solutions

• Add a "Display Note" to alert user to index map
• Reconfigure where the related records widgets are located on the page.

Other considerations

We have had challenges knowing how to catalog OpenIndexMaps - should the Resource Type be "Maps"? should a user be able to download the Index? Will that be confusing? How do we link them to the parent record? etc. Using a tabbed view might help with this indecision.

[ewlarson]

Other potential uses for tabbed item content/viewers:

• Render data tables from Feature Layers
• Our Metadata modal could be a tab instead
• An "Activity Stream" for accessioned datasets (ex. MN Geo Commons)
• Support for more complex compound objects (ex. IIIF Viewer plus Feature Layer plus Data Table, etc.)

[karenmajewicz]

Potentially, a tab could be "Related Items". This view might just be similar to the widgets for related records. Some of the items have many types of related records and having a dedicated tab might make them easier to visually parse.