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
Is your feature request related to a problem? Please describe.
In the current implementation of AnalysisNwbfile.create() the new nwb inherits the object id of both the nwb file and objects within it that aren't removed.
The UUID of the object id is not a hash of the data, so in theory I think it would be ok to alter them to be unique.
Describe the solution you'd like
A retroactive solution needs to:
alter the object_ids of existing files
correct the stored datajoint checksum/hash
correct any spyglass utilities that use this to find data
A forward solution needs to:
ensure unique object ids are created when creating a new analysis file
Describe alternatives you've considered
Would need dandi to change restriction policy on overlapping uuid. Since the same uuid do redundantly refer to duplicated data in different nwb files this might not be unreasonable.
The text was updated successfully, but these errors were encountered:
@samuelbray32 re: forward solution. Are new analysis NWB files created via the export function? You can generate new object IDs for each object in the nwbfile by calling nwbfile.generate_new_id() before export.
For older files, yes, you would need to edit the existing NWB file via h5py and do the following steps as you mentioned. For editing, you could do something like:
Is your feature request related to a problem? Please describe.
AnalysisNwbfile.create()
the new nwb inherits the object id of both the nwb file and objects within it that aren't removed.Describe the solution you'd like
A retroactive solution needs to:
A forward solution needs to:
Describe alternatives you've considered
Would need dandi to change restriction policy on overlapping uuid. Since the same uuid do redundantly refer to duplicated data in different nwb files this might not be unreasonable.
The text was updated successfully, but these errors were encountered: