search

EOEPCA / data-access

EOEPCA+ Data Access BB
https://eoepca.readthedocs.io/projects/data-access
Apache License 2.0
0 stars 0 forks source link

UI: Wireframes (Q2) #65

Closed j08lue closed 1 month ago

j08lue commented 3 months ago

Q2 plan for

Sub-tasks

j08lue commented 2 months ago

Takeaways from first prototype presentation with @kalxas, @jonas-eberle, @jankovicgd, @ricardoduplos:

  1. There is a nice cross-walk between STAC and OGC API Records https://github.com/stac-utils/stac-crosswalks/tree/master/ogcapi-records - can come in handy
  2. Jonas E encouraged us to be mindful of our limited budget and wants to keep it to minimum viable
  3. One (minimum) feature we had not thought of yet was to help users make the choice between Records and STAC - related to https://github.com/EOEPCA/data-access/issues/69
  4. Confirmed: UI should not deal with data assets, only metadata. Uploading even of small assets e.g. notebooks or so would instead happen through the Workspace BB or Resource Registration
  5. Validation is a topic of interest - how will we do it (in the app / plugins, STAC transactions API, JSON schema?) - not urgent now, but to keep in mind
  6. Should the app take the STAC API as a dynamic parameter (like STAC Browser), or be deployed for a specific (set of) STAC APIs?
  7. EarthCODE is not using STAC API but static STAC JSON in Git. They may want to use STAC Admin for Git-flow-managed STAC in the future. FYI
  8. Bulk ingest / asset upload can be a topic for later
  9. Do we want to support collections of collections (called “catalogs” in STAC but not in OGC because that term is reserved for something else)?

(just as a visual reminder of what was shown)