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

who/what is responsible for declaring and monitoring data_portal_subset elements? #1342

Open
turbomam opened this issue Nov 13, 2023 · 0 comments

Comments

@turbomam
Copy link
Member

turbomam commented Nov 13, 2023

This is a question about using subsets to let responsible parties know when a change in modeling may effect portal functionality.

The nmdc-schema has a data_portal_subset. It is documented on this page: https://microbiomedata.github.io/nmdc-schema/DataPortalSubset/

data_portal_subset:
  description:
    Subset consisting of entities that Kitware/nmdc-server use to populate the data portal.
  comments:
    - Schema authors are responsible for alerting and supporting Kitware and nmdc-server authors 
      about changes they will have to make if entities labeled with data_portal_subset are modified.
    - Assignment of the data_portal_subset is incomplete in the schema.

I really like the spirit of this subset, but am concerned that

  • the way it is being applied to schema elements is inconsistent
  • the communication responsibilities are be easy to forget.

For example, when the DOI modelling was changed from multiple free standing slots to a class, that had an impact of the SubmissionPortal. Should we have a submission_portal_subset? Who communicate the new modeling to SubmissionPortal maintainers?

see also

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

1 participant