You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In the Onix export plugin in OMP, each "product" (publication format) has a <RecordReference>. For a publication that has more than one publication format, there will be multiple <RecordReference> tags in the output XML.
Currently these are the same for every publication format, but they should be unique for each in order to align with the ONIX standard, and ensure that records can be identified by a unique identifier and differentiated from each other. We should also change how we are setting them to better align with best practices (see link below for more info on recommendations).
If we upgrade to newer versions of Onix, the current implementation will cause validation to fail as it will be enforced in future versions (e.g. 3.0.8).
This is a potentially breaking change, as it changes the identifiers for all of these records once we fix it. It has the potential to create duplicate records if the XML is being imported and is using these tags to check if the record exists already.
Describe the bug
In the Onix export plugin in OMP, each "product" (publication format) has a
<RecordReference>
. For a publication that has more than one publication format, there will be multiple<RecordReference>
tags in the output XML.Currently these are the same for every publication format, but they should be unique for each in order to align with the ONIX standard, and ensure that records can be identified by a unique identifier and differentiated from each other. We should also change how we are setting them to better align with best practices (see link below for more info on recommendations).
If we upgrade to newer versions of Onix, the current implementation will cause validation to fail as it will be enforced in future versions (e.g. 3.0.8).
This is a potentially breaking change, as it changes the identifiers for all of these records once we fix it. It has the potential to create duplicate records if the XML is being imported and is using these tags to check if the record exists already.
What application are you using?
OMP 3.3/3.4/main
Additional information
The text was updated successfully, but these errors were encountered: