Pull in the published PLUTO corrections file from Bytes, creating the base records for pluto_corrections
Insert records from pluto_input_research into pluto_corrections if there is not already a record for a given bbl and field in pluto_corrections and the old_value equals the "current" value in the field
Use pluto_corrections to apply changes to PLUTO
Issue with this approach, illustrated with a scenario:
We wanted to change value foo for bbl 123 from A to B and added this as a record to pluto_input_research
Later we wanted to change value foo for bbl 123 from A to C, so we updated the record in pluto_input_research
Because a combination of foo and 123 exists in the pluto_corrections the updated record with value A to C is not added to the pluto_corrections table; therefore, the intended correction is not applied.
Looking through the issues, I do not see a reason for bringing in the published PLUTO corrections file.
Proposed solution
Only pull in pluto_input_research as a source for correction and not the published PLUTO corrections file from Bytes
Current state for creating pluto_corrections:
Issue with this approach, illustrated with a scenario:
Proposed solution Only pull in pluto_input_research as a source for correction and not the published PLUTO corrections file from Bytes