Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List of catalogs not very helpful #4

Open
m-mohr opened this issue Aug 10, 2018 · 0 comments
Open

List of catalogs not very helpful #4

m-mohr opened this issue Aug 10, 2018 · 0 comments

Comments

@m-mohr
Copy link
Contributor

m-mohr commented Aug 10, 2018

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.

/cc @cholmes again ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant