Two requested changes:

1. Remove the use of this slot on any examples in the src/data/ folder
2. File a follow up issue to move this element to deprecated.yaml (similar to: Move ProtocolExecution to deprecated.yaml after the next release (11.4.0?) #2337)

Reassigning to @eecavanna to plan the migrator.

Now that (i.e. as of commit 2c9c250 on this branch) instances of the PortionOfSubstance schema class can no longer have a field named sample_state_information, creating an accompanying migrator will be necessary (in order to "keep data valid across schema versions").

In the schema docs, I can see that the PortionOfSubstance class is in the range of the substances_used slot of the following schema classes:

• Extraction
• StorageProcess
• DissolvingProcess
• ChemicalConversionProcess
• MobilePhaseSegment

The migrator will locate each "instance" of each of those classes in the database, check whether it has a substances_used field and—if it does—delete the sample_state_information field from each object in that substances_used field.

@eecavanna note that there will not be instances of MobilePhaseSegment, that class is also in-lined so you'll need to go one class up for that class.

Thanks, @kheal! In search of instances of the MobilePhaseSegment class, I'm planning to have the migrator look at the ordered_mobile_phases fields of instances of the ChromatographyConfiguration class (all of which are represented by documents in the configuration_set collection) and the ChromatographicSeparationProcess class (all of which are represented by documents in the material_processing_set collection).

@turbomam @eecavanna @sierra-moxon
Anyone know why these checks are failing now that I've moved the slot to the deprecated.yaml?

@mslarae13 the check failed because the computer (one of GitHub's servers) that runs the check failed to install some Python packages. I think it's a transient failure unrelated to the changes on this branch. I've launched a re-run of the check.