Users can now export the settings on the Create production page to a file, save and name locally, to then be imported into the same or other databases. This will reduce the need to set up the same configuration multiple times.
There are now two new actions at the top of the page when creating a new production: Download settings and Upload settings file.
Downloading settings
Click Download settings and the browser download will begin, along with a success message. This download is a .settings file that can be saved, renamed, and otherwise managed locally as the user chooses.
Uploading settings
DISCO generated .settings files can be imported into any DISCO database, but only .settings files can be imported. To import a .settings file, click Upload settings file. Use the file picker to select your file.
If the chosen .settings file is able to be imported with no errors or issues, a success message will appear. Cancel or continue to apply the settings to the page. After settings are imported and applied, users can then further modify on the page, run the production, or save the settings as the database default.
If the chosen .settings file has a problem, various warning messages will appear to inform the user of the issue. Warnings will occur if a tag does not exist or if a metadata field does not exist.
In this case, users can choose to continue and apply all the settings possible or cancel the import to make some changes in their database. There is even an option at the bottom of the window to copy the warning details to your clipboard for later reference. If a user chooses to proceed after warnings, impartial rules or settings will not be applied. An example of this: if a tag defined in the Confidentiality Stamp rule does not exist in the database, the entire Confidentiality Stamp configurations will not be imported. DISCO highly recommends reviewing settings after import to ensure they have applied as expected.
If a .settings file cannot be imported, an error message will notify the user. This can happen if the .settings file has been incorrectly manually modified.