Publishing profiles should be able to produce valid MARCXML
The ability to produce valid MARCXML exports from publishing profiles, with the namespace included, would be useful.
Currently the "MARCXML" option produces a file that is not valid MARCXML. It doesn't include a namespace.
The rationale given by ExL Support for not including a namespace was that it would be possible for the user to use norm rules to change the data on export, in which case the data might not be valid, so they didn't want to include a namespace. In some cases it may be necessary for libraries to produce data exports that are not valid, but even in those cases it may be helpful to have the namespace included.
This enhancement would change the publishing profile configuration page (and the machinery behind it). When publishing using "Physical format" = XML, there should be two additional choices that appear:
Include XML Namespace: yes/no
Validate before publishing: yes/no
For most use cases, I would think libraries would want to choose 'yes' to both of those. In that case, the profile should build the export file (with namespace included) and then validate it.
If the validation is request and fails, the next step should be one of these options (listed in order of preference):
1. Don't publish the file, and send a job report to the appropriate user saying why it didn't validate.
2. Publish the file (with namespace), and send a job report to the appropriate user saying why it didn't validate.
3. Publish the file (without namespace), and send a job report to the appropriate user saying why it didn't validate.