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

Q: Event support for collection management? #29

Open
lliming opened this issue Sep 20, 2024 · 1 comment
Open

Q: Event support for collection management? #29

lliming opened this issue Sep 20, 2024 · 1 comment

Comments

@lliming
Copy link
Contributor

lliming commented Sep 20, 2024

There are currently no event types that allow for collection creation or updating. Lacking that, each STAC index is likely going to manage collections manually (out of band wrt the message stream). But of course the East & West indices need to have the same collections!

Resolve the following questions:

  • How many collections (ESGF projects) do we expect during the first year of CMIP7 operation?
  • How much effort do we expect it to be to manage these collections manually?
  • Do we think it's important to have collection management events?
  • Do we have a clear understanding of the authorization policy for managing collections (ESGF projects)?
  • When should we begin designing/implementing in-band collection management (via STAC Transaction API and event stream) in the system?
@sashakames
Copy link
Contributor

Might be related to this: I recently had a conversation with Karl T. from WIP/CMIP orgs. There is interest in assigning datasets to "Collections" This may not be the use of STAC collections, as those are best used to organize sets of records as mutually-exclusive sets (is that the case?), and with these "CMIP collections" would be multiple membership.

  • What are all the "collection management" operations? And this includes the maintenance of records/items/assets within a collection? Is there other "collection metadata" that would be managed as well? We haven't determined if we will allow publishers a "hard delete" as there are tradeoffs from lessons learned with allowing that in ESGF-1.

  • Projects/Collections assuming no migrated inactive projects, projects where migration has been discussed or presumed to be active

    • CMIP7-FT, CMIP6, CMIP6Plus, E3SM, CORDEX-CMIP6, input4MIPs, obs4MIPs

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

2 participants