You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That is the expected metadata instance input of the migrate() function, only instances of Dandiset, not including instances of PublishedDandiset, or instances of Dandiset and its subclass PublishedDandiset.
This problem would be more of an issue if #266 is to put in place to enforce more strict validation.
The text was updated successfully, but these errors were encountered:
I noticed that
dandischema.metadata.migrate()
is not only used to migrateDandiset
objects butPublishedDandiset
objects as well ( see https://github.com/dandi/dandi-archive/blob/master/dandiapi/api/management/commands/migrate_published_version_metadata.py). However, it seems thatdandischema.metadata.migrate()
is hardcoded to handle onlyDandiset
objects, as indicated in the following lines:dandi-schema/dandischema/metadata.py
Line 435 in f0be592
dandi-schema/dandischema/metadata.py
Line 460 in f0be592
That is the expected metadata instance input of the
migrate()
function, only instances ofDandiset
, not including instances ofPublishedDandiset
, or instances ofDandiset
and its subclassPublishedDandiset
.This problem would be more of an issue if #266 is to put in place to enforce more strict validation.
The text was updated successfully, but these errors were encountered: