Fiying symlinks from imports / exports after data migration

Data Management
1

Hi,

I currently have a major migration from our old 3x NAS storage solution to a 1 TrueNAS storage pool. This involves copyin and resorting all projects and data.
It mostly works fine, with the help of cli.job_import_replace_symlinks but there a couple of symlinks for the import and exports which are not touched by this method. Fore example:
{‘exists’: False,
‘link_path’: ‘/mnt/CryoEM-Projects/XXX/CS-YYYYYY/exports/jobs/J42_select_2D/J42_particles_selected/J14/extract/000407881546258787423_FoilHole_6233291_Data_5079145_24_20251106_075937_fractions_patch_aligned_doseweighted_particles.mrc’,
‘link_target’: ‘/mnt/Data3/CryoEM_Projects3/CS-YYYYYY/J14/extract/000407881546258787423_FoilHole_6233291_Data_5079145_24_20251106_075937_fractions_patch_aligned_doseweighted_particles.mrc’}

In this case the project lived in /mnt/Data3/CryoEM_Projects3/CS-YYYYYY before and now (after archive/unarchive) lives in /mnt/CryoEM-Projects/XXX/CS-YYYYYY

Is there a good way to handle those as well?

Best

Jan

2

Symbolic links under exports/ are, unfortunately, outside the scope of the cli.job_import_replace_symlinks() function and would need to be updated outside CryoSPARC, likely using an external shell, python or similar script. Alternatively, if the referenced path(s) no longer exist, one might create symlinks at those paths that point to the new paths of the referenced data.