@jtyoung84 @mekhlakapoor this PR refactors the upload scripts in the following way:
The upload_new_asset.py generates uploads a different folder for each curation file. This is done by modifying the process_name to reflect the naming given by the user (see here).
As an example, the curation file:
ecephys_713591_2024-03-01_11-18-28/experiment1_Record Node 104#Neuropix-PXI-100.ProbeA_recording1/kilosort2_5/curation_KanghoonJ.json
will be uploaded and registered as:
ecephys_713591_2024-03-01_11-18-28_curated-KanghoonJ_{commit-datetime}
The upload_all_assets.py (which can be triggered manually), will upload and re-register all assets (in case we decide this is a better way to go)
Also update aind-data-schema to the latest version
Fixes #22
@jtyoung84 @mekhlakapoor this PR refactors the upload scripts in the following way:
upload_new_asset.py
generates uploads a different folder for each curation file. This is done by modifying the process_name to reflect the naming given by the user (see here).As an example, the curation file:
ecephys_713591_2024-03-01_11-18-28/experiment1_Record Node 104#Neuropix-PXI-100.ProbeA_recording1/kilosort2_5/curation_KanghoonJ.json
will be uploaded and registered as:ecephys_713591_2024-03-01_11-18-28_curated-KanghoonJ_{commit-datetime}
upload_all_assets.py
(which can be triggered manually), will upload and re-register all assets (in case we decide this is a better way to go)Also update
aind-data-schema
to the latest versionLet me know what you guys think!