A way to address when datasets are outdated in our library

[heidimok]

• stac ipyleaflet version: for release 0.3.0
• Python version: python >= 3.9 (some of the widgets are incompatible at v 3.8)
• Reference column Number 17 in the MAAP-ipleaflet-DevRoadmap

Context

During the June user working group, a member mentioned that they went to look at the landsat 8 surface collection with a date range and noticed that the timestamp ranges didn’t reflect the updated data.

Problem

There are “antique” datasets in our library.

This is actually a problem with Data Curation. So there are several paths:

1. Link to the STAC browser details to get more info
2. Ignore, but add to docs where to go learn about data details.

Notes

• Connecting to a 2nd STAC is a different issue

Acceptance Criteria

• Let users to know if a dataset is outdated
• Allow users to learn more about data details

[emmalu]

We already include a link to view the data via the MAAP STAC Browser, but it could be better differentiated, or noted, if/when a Collection's dates are outdated.

To know whether a dataset is outdated, we would need to apply a cutoff date across all Collection/Collection items, to compare the Collection's metadata dates with.

[heidimok]

Adding supporting user working group feedback on value of this issue:

Went to look at the landsat 8 surface collection with a date range and noticed it looks like timestamp ranges don’t reflect the updated. This is an “antique” dataset.

[heidimok]

Design Iteration 1

• Figma link
• A simple first start is using an alert component (could be warning or danger state...but maybe just warning) that is placed in context of the widget.
• Question here around whether the thing that's out of date is the collection itself or the date range, or both?
• Ideally we can offer a solution for the user. We need to discuss what's appropriate messaging to be as helpful as possible so that users can actually go find the updated data.