Conversion of tag 048 #119
Assignees
Labels
Comments
wafschneider
added a commit
that referenced
this issue
May 8, 2019
Codes in 048 $a/$b that aren't accounted for in the conversion specs should not attempt to create BIBFRAME data. Fixes #119.
wafschneider
added a commit
that referenced
this issue
May 8, 2019
Codes in 048 $a/$b that aren't accounted for in the conversion specs should not attempt to create BIBFRAME data. Fixes #119.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Data in MARC tag 048 that isn't specifically listed in the spec should be ignored -- instruction was added to ConvSpec-048-Codes-v1.4.
Recent example that created an empty value:
mo
ma
Error log:
In the 010-048 conversion, if the 048 does not have a correct value found in the instrumentCode table, it tries to create an element name “”. Can you have Wayne default to something
<xsl:template match="marc:datafield[@tag='048']" mode="work">
yaz-record-conv /marklogic/id/marc2bibframe2/record-conv.vlp3.xml split_0000015.xml > split_0000015.rdf
runtime error: file /marklogic/id/marc2bibframe2/xsl/ConvSpec-010-048.xsl line 781 element element
xsl:element: The effective name '' is not a valid QName.
runtime error: file /marklogic/id/marc2bibframe2/xsl/ConvSpec-010-048.xsl line 782 element element
xsl:element: The effective name '' is not a valid QName.
runtime error: file /marklogic/id/marc2bibframe2/xsl/ConvSpec-010-048.xsl line 781 element element
The text was updated successfully, but these errors were encountered: