Recommendations for re-importing a project?

Data Management
1

Are there any caveats to running something like the following in mongosh to remove the project, workspace, and job documents directly from the database, before removing any cs.lock lockfiles on the filesystem and then re-importing?

cryosparcm mongo
db.jobs.deleteMany( { "project_uid" : "P1", "uid": "J1" })
db.jobs.deleteMany( { "project_uid" : "P1", "uid": "J2" })
db.jobs.deleteMany( { "project_uid" : "P1", "uid": "J3" })
db.workspaces.deleteMany( { "uid" : "W1" , project_uid : "P1" })
db.workspaces.deleteMany( { "uid" : "W2" , project_uid : "P1" })
db.projects.deleteMany({ "uid": "P1"} )
Recovering missing jobs/workspaces after CryoSPARC v5 database recovery – project partially restored
2

There are. To prepare a project directory for import to any (even the same) CryoSPARC instance, one should detach the project.
After detaching the project from a CryoSPARC instance, one may apply the Delete Project from Database data management action.
Please can you describe the motivation for re-importing the project to the same instance?

3

Hi @wtempel ,

There is no immediate motivation on my part. This is not an issue that we are facing. One of our users brought this issue to our attention and we were curious about whether removing documents directly from the database would be an option. If we ever face a similar issue, it would be helpful to know what the best course of action would be to resolve it.

4

@jpellman I created a new topic for this discussion.

For issues of this type, we might recommend tailored approaches depending on “fine” details. The general recommendation would be to follow the appropriate procedures in the Data Management Guide during day-to-day operation and usage of CryoSPARC. If/when a problem related to data management occurs, please create a topic in this forum and describe specific details.