Evolution of STAC Admin (STAC Manager)

[j08lue]

This project is planned to evolve into a highly reusable, extendable frontend for STAC data management.

Our current development surge is driven by needs we encounter on the NASA VEDA project and the ESA EOEPCA+ project. Nonetheless, we aim at providing a generic tool that is useful to anyone managing data in STAC, similar to how STAC Browser has become the ubiquitous tool for browsing a STAC catalog.

We are planning to rename this package to STAC Manager, to give it a similar role description to STAC Browser. Nomen est omen... 🤞

Please see the relevant EOEPCA+ docs about our vision for how this project will be used in the EOEPCA+ ecosystem of open source software.

[j08lue]

Definition of MVP

These are the essential features that bring users value to STAC Manager, in prioritized order:

Must have

1. Creating single STAC collections and items without manually pushing JSON to an API
2. UI features for creating valid STAC for core fields (e.g. limited set of provider roles)
3. Support for STAC extensions (selected ones to begin with)
4. Search / filtering functionality to find the collection they seek to edit
5. Search / filtering functionality to find the item they seek to edit
6. JSON input and JSON editing (whole collection / item) as alternative to form

Nice to have

1. Validation of submitted data upon submission (to STAC API Transaction extension)
2. Validation of data as is is entered into the form

Later

1. Bulk STAC item ingestion
2. Bulk STAC collection ingestion
3. Preview for entered data, e.g. render extension or CommonMark

Kano model

Attempt at putting these items into a Kano model diagram. This shows the current state, not the target.