GeneticAnalyses can have their genetic IDs and assessments updated either through the WALDO webform (link) or through the genetic_analysis_assessment_update command.
Because of the uniqueness constraint on genetic IDs, the current implementation errors out if we try to change a genetic ID to an already existing one, even if we are also changing the existing one to something new later in the same batch update. Here is an example of an update that would fail:
S1234 -> S1235
S1235 -> Ignore_S1235
This can be solved by simply re-ordering the input file. However, if we have a cycle within the update form, re-ordering does not work either, e.g.:
S1234 -> S1235
S1235 -> S1234
The proposed solution is to iterate through the upload form, updating every GeneticAnalysis to have some new temporary garbage genetic ID, and then iterate through again to update to proper new genetic IDs.
GeneticAnalyses can have their genetic IDs and assessments updated either through the WALDO webform (link) or through the genetic_analysis_assessment_update command.
Because of the uniqueness constraint on genetic IDs, the current implementation errors out if we try to change a genetic ID to an already existing one, even if we are also changing the existing one to something new later in the same batch update. Here is an example of an update that would fail:
S1234 -> S1235
S1235 -> Ignore_S1235
This can be solved by simply re-ordering the input file. However, if we have a cycle within the update form, re-ordering does not work either, e.g.:
S1234 -> S1235
S1235 -> S1234
The proposed solution is to iterate through the upload form, updating every GeneticAnalysis to have some new temporary garbage genetic ID, and then iterate through again to update to proper new genetic IDs.