Improve naming and description of Sandbox Explorer STAC catalogue

[robbibt]

Issue

Currently the Sandbox Explorer provides the STAC endpoint to the production database for DEA data on AWS: https://explorer.sandbox.dea.ga.gov.au/stac/

Matthias Mohr recently added this endpoint to the official STAC index (https://stacindex.org/catalogs/digital-earth-au#/), and pointed out that the STAC catalogue metadata could be improved: https://twitter.com/matthmohr/status/1417127562787045387

In particular, the "id" and "title" STAC catalogue is "Sandbox Explorer", which doesn't make it clear that this is the main STAC metadata for the Digital Earth Australia program. In addition, the "description" is generic and uninformative:

"id": "Sandbox_Explorer",
"title": "Sandbox Explorer",
"description": "Configure stac endpoint information in your Explorer `settings.env.py` file"

Suggested fix

As this is our main STAC endpoint, we should rename the "id" and "title" to better portray this as the place to access metadata about DEA's data. We should also improve the description field to better describe the catalogue. For example:

"id": "digitalearthau",
"title": "Digital Earth Australia",
"description": "Digital Earth Australia (DEA) is a platform that uses spatial data and images recorded by satellites orbiting our planet to detect physical changes across Australia in unprecedented detail."

Ping @GypsyBojangles @alexgleith @jeremyh

[jeremyh]

Agreed -- it would be nice to make these more consistent.

They're all defined by the cloud team's deployments in the datakube-apps repo:

These are the current values in master:

❯ rg STAC_END
workspaces/dea-sandbox/web/04_explorer_sandbox_latest.yaml
88:      STAC_ENDPOINT_ID = 'Sandbox_Explorer'
89:      STAC_ENDPOINT_TITLE = 'Sandbox Explorer Latest'

workspaces/dea-sandbox/web/04_explorer_sandbox.yaml
99:      STAC_ENDPOINT_ID = 'Sandbox_Explorer'
100:      STAC_ENDPOINT_TITLE = 'Sandbox Explorer'

workspaces/deafrica-prod-af/web/04_explorer.yaml
73:      STAC_ENDPOINT_ID = 'DEAfrica_data'
74:      STAC_ENDPOINT_TITLE = 'Digital Earth Africa'

workspaces/deafrica-prod-af/web/04_explorer_latest.yaml
70:      STAC_ENDPOINT_ID = 'DEAfrica_data'
71:      STAC_ENDPOINT_TITLE = 'Digital Earth Africa'

workspaces/dea-sandbox/web/04_explorer_prod.yaml
88:      STAC_ENDPOINT_ID = 'AWS_Explorer'
89:      STAC_ENDPOINT_TITLE = 'AWS Explorer'

workspaces/dea-sandbox/web/04_explorer_nci.yaml
85:      STAC_ENDPOINT_ID = 'NCI_EKS_Prod_Explorer'
86:      STAC_ENDPOINT_TITLE = 'NCI eks prod explorer'

workspaces/dea-sandbox/web/04_explorer_prod_latest.yaml
88:      STAC_ENDPOINT_ID = 'AWS_Explorer'
89:      STAC_ENDPOINT_TITLE = 'AWS Explorer Latest'

and dev:

workspaces/deafrica-dev/web/04_explorer_latest.yaml
71:      STAC_ENDPOINT_ID = 'DEAfrica_dev_data'
72:      STAC_ENDPOINT_TITLE = 'Digital Earth Africa Development Latest'

workspaces/deafrica-dev/web/04_explorer.yaml
71:      STAC_ENDPOINT_ID = 'DEAfrica_dev_data'
72:      STAC_ENDPOINT_TITLE = 'Digital Earth Africa Development'

workspaces/dea-dev/web/04_explorer.yaml
89:      STAC_ENDPOINT_ID = 'AWS_EKS_Dev_Explorer'
90:      STAC_ENDPOINT_TITLE = 'AWS eks dev explorer'

workspaces/dea-dev/web/04_explorer_nci.yaml
85:      STAC_ENDPOINT_ID = 'NCI_EKS_Dev_Explorer'
86:      STAC_ENDPOINT_TITLE = 'NCI eks dev explorer'

... and none of them seem to have 'description' set

[robbibt]

So many explorers! I guess I've been assuming the Sandbox Explorer would be our "official" STAC endpoint, but perhaps it would be 'AWS_Explorer' instead? Or one of the "latest" ones? Either way, I think it would be idea if we could choose one to be the main endpoint we advertise as our best public facing metadata, and name it accordingly so users don't have to think too much about which endpoint to use.