Closed wdduncan closed 2 years ago
I have concerns about this, I would like to unmerge the PR
We should not be adding baroque fields like depth2
to the schema
depth2
)This field is a temporary fix for capturing depth ranges. There are a number of fields that need such ranges (e.g., temperature, size). A ticket has been filed with MIXS: https://github.com/GenomicsStandardsConsortium/mixs/issues/166
@wdduncan can this issue be closed? Or should it be moved to August?
@ssarrafan Please move to August sprint. We have an approach to implement. I think @cmungall and myself have a few details to finalize.
@wdduncan @cmungall any updates on this? I know you've been busy with other work. Let me know if this should be moved to the 'backlog' or if it's done.
Thank you!
Sorry. I haven't had a chance to get to this yet. I would move it to the next sprint.
@wdduncan should this issue be closed, moved to the backlog or moved to the October sprint?
@ssarrafan Please move this to the October spring :) Thanks!
@wdduncan we are planning to devote November to fixes, clean up etc. Would it make sense to move this issue to November?
@dehays
I think I can get to it in October. Unless, a number of other issues crop up :(
for biosamples (and related package tables)
depth2
andsubsurface_depth2
slots are needed for when the depth is within a range.