aclum

This is sleek, i like it. WRT to duplicates I think we'd want to store both in the aggregation table, but then handle display with nmdc-server logic. It's potentially useful...

I'd assumed the reference free workflow would have a different workflow exeuction subclass name which would allow for easy aggregations. Since the current results are only presence/absence no work has...

Yuri has to decide if he wants this slot to be a boolean or a curie. If a curie it should be populated with a data object (nmdc:dobj*). I do...

@mbthornton-lbl notes we have the same issue with was_generated_by. @cmungall @turbomam where are we at with having linkml enforce a range.

I’m talking about enforcing a class constraint via range without specifying `structured_pattern.syntax` On Tuesday, April 2, 2024, Chris Mungall ***@***.***> wrote: > Are you talking about applying id pattern constraints...

Yes, the main branch of the schema. Mark updated the berkeley schema to enforce type but that isn't in main yet so for now you could look at the type...

Yes, `nmdc:omprc`, they typecode for OmicsProcessing is different than the activity identifiers which are typically `nmdc:wf*`

@shreddd Tagging you in this issue as it pertains to the database discussion. This would be easy in a relational database with a foreign key constraint. In practice for re-iding...

@sierra-moxon @turbomam is there an update on this? We've had to implement ad-hoc code here to make sure the values for was_generated_by follow napa style identifiers. Is the only short...

@turbomam or @sierra-moxon do you have time to fix the ranges for was_informed_by and was_generated by separate if figuring out how to validate this. Code that @PeopleMakeCulture is prototyping checks...