Occasionally folks have an old version of rad / roman_datamodels installed, but want to use a file produced by a newer version of rad/roman_datamodels. Presently roman_datamodels objects to opening the new file because the schema that defines it is not in the currently installed rad. Users can address this issue by updating rad and roman_datamodels.
However, frequently our schema changes are very minor and so it's fairly clear how the file "should" be opened in roman_datamodels. e.g., some optional keyword has been added that isn't used, and an old, installed schema could likely successfully open the file, for example.
We should consider whether there is a supportable option enabling users to lag behind in their installed rad / roman_datamodels for these minor updates.
Occasionally folks have an old version of rad / roman_datamodels installed, but want to use a file produced by a newer version of rad/roman_datamodels. Presently roman_datamodels objects to opening the new file because the schema that defines it is not in the currently installed rad. Users can address this issue by updating rad and roman_datamodels.
However, frequently our schema changes are very minor and so it's fairly clear how the file "should" be opened in roman_datamodels. e.g., some optional keyword has been added that isn't used, and an old, installed schema could likely successfully open the file, for example.
We should consider whether there is a supportable option enabling users to lag behind in their installed rad / roman_datamodels for these minor updates.