Closed RichardWallis closed 2 years ago
@RichardWallis thanks for the report. The issue is corrected on the master branch (and will be in the forthcoming v1.7), and has been backported to the v1.6 branch. I made a new release (v1.6.2) in case that is useful to you, but you should also feel free to use the master branch, or the v1.7-RC, which contains most if not all of the updates that will be part of v1.7 at this time.
Running the latest version 1.6.1 against several thousand MarcXML records has identified a common error where certain subfields with leading/trailing spaces cause invalid URIs to be created. Although the error is in the source data, some space trimming in the XSLT could make the process more robust in this area.
Example MarcXML:
Resultant RDFXML:
The result is that downstream RDF processing complains about invalid URIs, that contain the preserved leading space. I have also seen examples where a trailing space causes the same symptoms.
This is not confined to the
336
tag, it is also apparent for 337, 338.Looking at the XSL I see there is
normalize-space(.)
being applied to subfield 'b', could something similar be applied to subfield '2'?