storing invalid data: less strict mode
since the validation is required for all new data imports i would recommend one of the following, to enable users to store invalid data forcefully:
- allow a less strict mode by
- adding a checkbox to the publisher GUI
- adding a boolean parameter
- try to get a missing schema file first, even when it is not added to the import process
- may be this also allows the usage of a schema from a different location (any non-textgrid https URL)
- make this functionality optional with a checkbox in the GUI and an appropriate parameter
since this FR proposes new parameters and there are already 4 existing at connect:publish
we may think of a configuration given as map
.