You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The list of catalogs usually just has the path shown, which often is not very helpful. For example, for the planet disaster data (https://storage.googleapis.com/pdd-stac/disasters/hurricane-harvey/catalog.json) there is a subcatalog "0831/catalog.json". You can only guess what that means and similar things apply to other catalogs. This is due to the fact that for catalogs, the browser relies on the title of the links being set and for Items it lazy loads data from the items itself.
An idea could be to lazy load catalog titles, too. But it's the same issue as with Fixed date formatting #1, lazy loading all data comes at a cost. Also, all the ISERV catalogs have the same title, which would be even more confusing than the paths. (This also leads to strange breadcrumbs: ISERV / ISERV / ISERV / ISERV - but that's an issue with the catalog, not the browser.)
Another idea is to encourage to fill the title fields during generation with appropriate content, i.e. the title/name of the referenced catalogs/items, but this would be something for the spec.
The list of catalogs usually just has the path shown, which often is not very helpful. For example, for the planet disaster data (https://storage.googleapis.com/pdd-stac/disasters/hurricane-harvey/catalog.json) there is a subcatalog "0831/catalog.json". You can only guess what that means and similar things apply to other catalogs. This is due to the fact that for catalogs, the browser relies on the title of the links being set and for Items it lazy loads data from the items itself.
/cc @cholmes again ;)
The text was updated successfully, but these errors were encountered: