UI Improvements

[smohiudd]

Description

The VEDA team has conducted user interviews and gathered some feedback on the initial prototype of STAC admin: NASA-IMPACT/veda-backend#304. Although this feedback is fairly high level, we could use it to guide certain features for an upcoming STAC-admin release.

Some features requests include:

• Ability to create a new collection with required fields (mandatory) + additional fields. Identify which are required field and which are optional.
• Edit all the fields that are present in a collection/item (not just a subset)
• Ability to apply a change to all collections/all items in a collection or a select list of collections. For example for things like stac-extensions or license or renders.colormap_name
• License field should be a dropdown of all the valid values
• Validation of fields (ex - url provided is valid and returns a 2XX response; if stac-extensions is provided, check the schema validity)

PI Objective

Objective DS-2: STAC Admin NASA-IMPACT/veda-architecture#454

Acceptance Criteria

• UI improvements are available in updated release of STAC Admin

[tjaeuth]

@smohiudd Hi, my search query on Google "UI STAC catalog creation" was leading me to this repository.

I am also looking for a way to create catalogs, collections and items using the web UI.
Your project seems to be pursuing this goal.

I am just curious why not just extending the https://github.com/radiantearth/stac-browser?

Furthermore, I guess you are reimplementing every field from the JSON schema into your UI. That means custom metadata fields will never be part of your UI, or am I wrong?
I was thinking why not just using JSON forms to build the UI out of the official JSON schema.

What do you think about this?

[j08lue]

Great to hear about your interest. We are currently moving this project forward in the context of the NASA VEDA and the ESA EOEPCA+ projects. Some details about our plans and ongoing work are in project-related repositories and docs here: https://eoepca.readthedocs.io/projects/resource-discovery/en/latest/design/resource-admin-ui/design/

I will try to cross-link relevant issues into this repo, so our ongoing work is easier to discover for people who stumble over this project, like you did.

I guess you are reimplementing every field from the JSON schema into your UI

We decided against implementing JSON schema. Here are some details about that decision:

• Spike: How to implement support for STAC render extension EOEPCA/data-access#57 (comment)

That means custom metadata fields will never be part of your UI, or am I wrong?

We are planning to implement a lightweight plugin system for STAC Admin that can be used to enable support for non-required fields such as custom properties or STAC extensions. See details about that here:

• Flexible plugin system for the STAC metadata editor EOEPCA/data-access#73

I am also looking for a way to create catalogs, collections and items using the web UI.

We do not currently have plans to support Catalog creation, only Collection and Item CRUD.

[smohiudd]

Thanks for reaching out @tjaeuth! And thanks for the info @j08lue.

To answer this question:

I am just curious why not just extending the https://github.com/radiantearth/stac-browser?

STAC browser serves a powerful use case for searching catalogs and may not be the best interface for editing granular metadata without changes to that UI. It may not be appropriate to conflate STAC viewing and editing in this case.

[tjaeuth]

@j08lue @smohiudd Thanks a lot for your clarifications.

I will keep an eye on this. Definitely, interesting ideas coming up here.