j08lue
commented
1 week ago Users
Scientist (terrabyte perspective)
- Is mostly not an expert of using REST APIs however can easily learn how to use them (e.g., in Python or R). For example, they can be more familiar with writing commands with client libraries like pystac. they can be more familiar with writing commands with client libraries like pystac
- Would love to use client libraries instead of pure REST APIs (e.g., not handling all the authentication flow on their own)
- Will in many cases create STAC items for generated output data programmatically
- Would in some cases create STAC items for single input datasets manually in a STAC metadata editor
- Will in many cases create and configure STAC collections manually, but does not make sense for hundred of items.
- Creating STAC / OGC API Records metadata is new to many of them
- Would like to visualize their data in a web-based client
- Would like to publish data visualizations for external (only pre-defined styles) - supported with render stac extension
Requirements
- BR041: The Resource Discovery BB shall provide a web-enabled Administration UI for maintenance of configuration, metadata etc.
- BR058: The Data Access BB shall provide a web-enabled Administration UI for maintenance of configuration, and definitions for products, layers, styles, etc.
Epics
Design authentication and authorization UX
- Objective: Design the authentication flow for a scientist and an operator for the administration UI.
- Lead Contributor: DevSeed
- Priority: 1
- Upper Bound Estimate: 4
- Lower Bound Estimate: 2
Implement the authentication and authorization flow for the administration UI
- Objective: Implement the authentication and authorization flow for the administration UI which integrates the API gateway.
- Lead Contributor: DevSeed
- Priority: 1
- Upper Bound Estimate: 5
- Lower Bound Estimate: 3
Integrate the STAC Admin for editing STAC metadata
- Objective: Integrate the STAC Admin with Terrabyte given the authentication flow and our data infrastructure. It already includes update functionality. We can quickly add support for delete functionality. Includes renaming a collection.
- Lead Contributor: DevSeed
- Priority: 1
- Upper Bound Estimate: 6
- Lower Bound Estimate: 4
Add validation of STAC metadata to STAC Admin
- Objective: Add validation of STAC catalogs including the JSON data, but also the referenced assets.
- Lead Contributor: DevSeed
- Priority: 1
- Upper Bound Estimate: 5
- Lower Bound Estimate: 3
Add support for render extension in the STAC Admin
- Objective: Add support for the render extension within the STAC Admin. Define visualization styles for update and create functionalities.
- Lead Contributor: DevSeed
- Priority: 1
- Upper Bound Estimate: 4
- Lower Bound Estimate: 2
Add create functionality to the STAC Admin
- Objective: Add creating STAC collections and items within the STAC Admin. Add configuration of backend-specific parameters (e.g., pgstac partition) on collection creation.
- Lead Contributor: DevSeed
- Priority: 1
- Upper Bound Estimate: 4
- Lower Bound Estimate: 2
Add clear functionality to the STAC Admin
- Objective: Clear items associated with a collection.
- Lead Contributor: DevSeed
- Priority: 2
- Upper Bound Estimate: 3
- Lower Bound Estimate: 1
Add deactivating/activating data services of a collection within STAC Admin
- Objective: Add deactivating/activating data services of a collection. For each collection define which data access services are available (e.g., STAC collection without data access services, STAC collection with OGC WMTS enabled, STAC collection with OGC API Coverages enabled
- Lead Contributor: DevSeed
- Priority: 1
- Upper Bound Estimate: 3
- Lower Bound Estimate: 1
Integrate the STAC Browser for viewing and exploring STAC Metadata
- Objective: Integrate the STAC Browser
- Lead Contributor: DevSeed
- Priority: 1
- Upper Bound Estimate: 4
- Lower Bound Estimate: 2
Add Mass import/export using external Geoparquet file
- Objective: Mass import/export using external Geoparquet file based on common use case from DLR.
- Lead Contributor: DevSeed
- Priority: 1
- Upper Bound Estimate: 6
- Lower Bound Estimate: 4
Add batch functionality for updates in STAC Admin
- Objective: Add downstream updates to the items of a collection. For example, change the name of asset for all items and in the collection metadata.
- Lead Contributor: DevSeed
- Priority: 1
- Upper Bound Estimate: 6
- Lower Bound Estimate: 4
Add programmatic tips in STAC Admin
-
Objective: Always show how functions in the UI can be executed programmatically.
-
Lead Contributor: DevSeed
-
Priority: 1
-
Upper Bound Estimate: 6
-
Lower Bound Estimate: 4
-
Operators should see, manage and validate all collections
Design Data Access Web-Enabled Administration for configuration of Layers UX
- Objective: Design the UX flow for setting up our configurations. For example, configuring the pgSTAC partition of a collection.
- Lead Contributor: DevSeed
- Priority: 1
- Upper Bound Estimate: 6
- Lower Bound Estimate: 4
Implement Data Access Web-Enabled Administration for configuration of Layers
- Objective: Implement the UX flow for setting up our configurations. For example, configuring the pgSTAC partition of a collection. Including authorization logic
- Lead Contributor: DevSeed
- Priority: 1
- Upper Bound Estimate: 10
- Lower Bound Estimate: 6
The Resource Discovery Building Block provides a catalogue that maintains metadata for the resources held within a platform, and also supports platform federation by maintaining records to resources in other platforms.
It is planned to feature STAC API (via eoAPI / PgSTAC) for STAC collections and OAPI Records (via pycsw) for other types of assets.
An important feature of this building block is a graphical user interface for administration of resources (both in eoAPI and pycsw).
This ticket is to get a better grip on the vision for this epic.