Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

008/35-37 and 041 $a/$d conversion #38

Open
wafschneider opened this issue Jun 7, 2017 · 1 comment
Open

008/35-37 and 041 $a/$d conversion #38

wafschneider opened this issue Jun 7, 2017 · 1 comment

Comments

@wafschneider
Copy link
Collaborator

Currently, a bf:language property of the work is generated both by the 008/35-37 and by 041 $a and $d. Of the 041, the MARC standard states:

Used in conjunction with 008/35-37 (Language). If there is a code in 008/35-37, it is recorded as the first code in subfields $a or $d (for sound recordings) of field 041.

Should the conversion for the 008/35-37 take the 041 into account, to avoid duplicate bf:language assertions? If both 008/35-37 and 041 $a/$d are present, which would be preferred?

@osma
Copy link
Contributor

osma commented Jun 8, 2017

+1 for avoiding duplicate assertions. However, depending on the amount of indirection involved, this could happen naturally - if the assertions was simply e.g. <work> bf:mainLanguage "eng" (see my proposal in #37) then several assertions like this in the RDF/XML output would collapse into a single triple when interpreted as RDF.

If the languages in 008 and 041 are different, I think just including them all in the output would make sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants