As a user reading a data story, I would like to explore the dataset more completely, so that I can learn more about the data and how I can use it
Content managers might want to do two different things at the moment:
Send users to the E&A page with the layer, time, and zoom matching what was in the map or map comparison widget
To the dataset overview if the dataset is not available in E&A, or if they'd just like people to get an overview first
For future iterations, there will likely be other tools for visualizing, so there will be more variety in end destination.
One special use case to consider is when somebody is using the map comparison widget to compare two different datasets. My gut tells me that we should still only allow for one "action" to send a user somewhere, and that action should take the user to the E&A tool with those layers loaded. The thinking being that if somebody is comparing two datasets on a map comparison widget, we should assume they're allowed to compare them in E&A. But we should check my thinking on that.
Acceptance criteria
[ ] By default, all map, map comparison, and scrollytelling widgets have an action that I can click to send me to the dataset overview page for that map layer. All other AC describe something that has been configured by content managers and can override this action.
[ ] For map comparison widgets comparing two different datasets ONLY, the default is to go directly to the E&A tool with both layers loaded and temporal/spatial selection to match the map where I came from
[ ] From a map widget in a data story, I can click an action to go directly to the E&A tool with the layer, time, and zoom level pre-loaded to match the view I came from (not necessarily the view configured in the data story)
[ ] From a map comparison widget in a data story, where it is comparing one dataset with two different dates, I can click an action to go directly to the E&A tool with the same layer loaded, zoom levels, and times configured in comparison mode
[ ] From a scrollytelling chapter in a data story, I can click an action to go directly to the E&A tool with the map layer pre-loaded to match the location and time of the view I came from
As a user reading a data story, I would like to explore the dataset more completely, so that I can learn more about the data and how I can use it
Content managers might want to do two different things at the moment:
For future iterations, there will likely be other tools for visualizing, so there will be more variety in end destination.
One special use case to consider is when somebody is using the map comparison widget to compare two different datasets. My gut tells me that we should still only allow for one "action" to send a user somewhere, and that action should take the user to the E&A tool with those layers loaded. The thinking being that if somebody is comparing two datasets on a map comparison widget, we should assume they're allowed to compare them in E&A. But we should check my thinking on that.
Acceptance criteria