-
Notifications
You must be signed in to change notification settings - Fork 10
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
Draft version timestamps not updated when embargoed assets were moved #2002
Labels
bug
Something isn't working
Comments
So it seems this is mainly a retroactive issue? That is, we should update these respective versions to reflect the last modified time of those assets, but it's not a systematic issue going forward? Seems like it's just a side effect of the embargo re-design data migration. |
@jjnesbitt Yes, that sounds correct. |
@jwodder I believe I've addressed the issue. Can you verify this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that, on or around April 29, embargoed asset blobs were moved from the
dandiarchive-embargo
bucket to thedandiarchive
bucket. This was accompanied by updates to the assets'contentUrl
metadata, and the assets'modified
properties were updated at that time, but themodified
properties of the respective Dandisets'draft
versions were not updated, andbackups2datalad
does not like this.For a specific example, the embargoed Dandiset 000770 contains an asset
sub-Elgar/sub-Elgar_ses-2022-06-04_ecephys.nwb
with amodified
property of2024-04-29T19:35:05.558024Z
, yet themodified
property for 000770/draft is still2024-04-09T19:15:02.126137Z
.The text was updated successfully, but these errors were encountered: