-
Notifications
You must be signed in to change notification settings - Fork 2
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
Improve handling of DUOS replicas #6139
Comments
Assignee to consider next steps. |
hannes-ucsc
added
enh
[type] New feature or request
debt
[type] A defect incurring continued engineering cost
manifests
[subject] Generation and contents of manifests
labels
Apr 30, 2024
It is very tempting to continue exploiting the Terra imported loop hole. I want to sit on this for a bit and see if the current behavior get in the way of some of the other outstanding verbatim manifest work. |
Move to backlog. |
bvizzier-ucsc
added
+
[priority] High
-
[priority] Medium
and removed
-
[priority] Medium
+
[priority] High
labels
Nov 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Replicas containing the dataset description from DUOS should be given a distinct
replica_type
: "duos_dataset_registration". There should be a way to links the rows in this table to those in theanvil_dataset
table. Perhaps having the same entity ID will be sufficient. We should also add the DUOS ID to these replicas.The text was updated successfully, but these errors were encountered: