Best practice to split a project into two projects

Data Management
1

Hello all,

I have a CryoSPARC v5 project that currently contains four workspaces.

Two of the workspaces are finished and are ready to be archived. However, I am still actively working on the other two workspaces.

Since CryoSPARC archives projects rather than individual workspaces, I am looking for the best way to separate the active workspaces from the archived ones.

My current idea is:

  1. Duplicate the entire project. 2. Archive the original project after removing the active workspaces. 3. Remove the archived workspaces from the duplicated project and continue processing there.

Is this a reasonable approach?

Alternatively, is there a better or recommended way to split one project into two projects while preserving all jobs and dependencies? The project contains approximately 100 jobs, so I would prefer to avoid exporting/importing individual jobs if possible.

Thanks very much!

Da

2

This approach looks plausible. To ensure that the project directory is duplicated in a valid state, you may want to (temporarily) apply the CryoSPARC Archive data management action to the relevant project before beginning duplication of the project directory and unarchive it after duplication is complete.

A split project feature is under consideration for a future CryoSPARC release.