-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add Manifest
class
#2230
Add Manifest
class
#2230
Conversation
|
@aclum, @SamuelPurvine, @corilo, @turbomam, @pdpiehowski - I could benefit from an early review and/or input on the |
the current values for ManifestCategoryEnum make sense to me. Tagging @mbthornton-lbl, if implemented nmdc_automation would have to check manifest_set to see if data objects should be combined together. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, this is good. Let's see what we can do together today in terms of refining the descriptions. I see you already have one comment about that. I'm going to suggest some more edits that emphasize minimal, realism-based descriptions.
I especially want to add comments about potential vulnerabilities in this modelling, which I think is mainly in the area of not enforcing some coupling with other schema elements, like any fractions manifest should correspond to data objects that were the output of one single fractionation process.
src/schema/basic_classes.yaml
Outdated
in_manifest: | ||
range: Manifest | ||
multivalued: true | ||
#TODO KRH: add description and structured_pattern constraints |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the timeline for adding a description? Can I help in any way?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one or more combinations of other DataObject
s that can be analyzed together in the same context ?
@turbomam - Thanks for the assist with the descriptions and suggested comments, I've incorporated them all now and I think this is ready for merging! |
This PR
Manifest
class (inherits fromInformation
class) to model collections ofDataObjects
records for workflows.Manifest
class has slotmanifest_category
with range ofManifestCategoryEnum
in_manifest
slot toDataObject
to connectDataObject
s to aManifest
or to multipleManifests
smanifest_set
toDatabase
classin_manifest
slot,Manifest
class, andmanifest_set
slotNo migration necessary, this only adds slots and classes and does not refactor existing classes or slots.
Addresses #766; should unblock microbiomedata/nmdc-server#1365