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

Take into account MARC relator codes in RDA entries #72

Closed
acka47 opened this issue Apr 21, 2016 · 12 comments
Closed

Take into account MARC relator codes in RDA entries #72

acka47 opened this issue Apr 21, 2016 · 12 comments

Comments

@acka47
Copy link
Contributor

acka47 commented Apr 21, 2016

Moved here from lobid/lodmill#759. Sub-issue of hbz/lobid#161, see hbz/lobid#161 (comment).

We just have to take the code from subfield 4 in the 1** and 2** fields and append it to http://id.loc.gov/vocabulary/relators/ to get the relator code for the respective entry. Default entry (at least for person) is aut but for now we will continue using dct:creator.

Examples:

http://lobid.org/resource/HT018772877, source (snippet):

<datafield tag="100" ind1="b" ind2="1">
  <subfield code="p">Klein, Volkmar</subfield>
  <subfield code="4">edt</subfield>
  <subfield code="3">Herausgeber</subfield>
  <subfield code="9">(DE-588)174630727</subfield>
</datafield>

http://lobid.org/resource/HT018776405, source (snippet):

<datafield tag="200" ind1="b" ind2="1">
  <subfield code="k">Theater im Pfalzbau</subfield>
  <subfield code="4">isb</subfield>
  <subfield code="3">Herausgebendes Organ</subfield>
  <subfield code="9">(DE-588)301289-X</subfield>
</datafield>

https://lobid.org/resource/HT018781534, source (snippet):

<datafield tag="100" ind1="-" ind2="1">
  <subfield code="p">Schroeder, Hermann</subfield>
  <subfield code="d">1904-1984</subfield>
  <subfield code="4">cmp</subfield>
  <subfield code="3">Komponist</subfield>
  <subfield code="9">(DE-588)118823442</subfield>
</datafield>

https://lobid.org/resource/HT018782520, source (snippet):

<datafield tag="104" ind1="a" ind2="1">
  <subfield code="p">Heitmann, Michaela</subfield>
  <subfield code="d">1969-</subfield>
  <subfield code="4">art</subfield>
  <subfield code="3">Künstler</subfield>
  <subfield code="9">(DE-588)142552739</subfield>
</datafield>
@acka47 acka47 added the launch label Apr 21, 2016
dr0i pushed a commit that referenced this issue Jan 11, 2017
@acka47 acka47 changed the title Take into account MARC relator codes in RDA entries Take into account MARC relator codes in RDA entries Feb 7, 2017
@acka47 acka47 added the ready label Feb 7, 2017
ChristophEwertowski added a commit that referenced this issue Mar 3, 2017
@ChristophEwertowski ChristophEwertowski removed their assignment Mar 3, 2017
@ChristophEwertowski
Copy link
Contributor

Looked at the 5021 files of the small test (test.tar.bz2) to find some examples for the functional review. The only file where changes can be seen is: HT018939763 (test server) / HT018939763 (production). Other files which have the subfield but aren't converted because of the missing role in the morph are: HT018770176, HT019093814, HT018786244 and HT018924091 (all /pbl or publisher), HT018889713 (/oth or other) and HT018889713 (/isb or issuing body). I don't know if there are more files which have the subfield in the folder of all Xml files but I doubt it. @acka47 : You can "review" it now.

@acka47
Copy link
Contributor Author

acka47 commented Mar 6, 2017

. Other files which have the subfield but aren't converted because of the missing role in the morph are: HT018770176, HT019093814, HT018786244 and HT018924091 (all /pbl or publisher), HT018889713 (/oth or other) and HT018889713 (/isb or issuing body)

pbl comes from field 677 and thus isn't covered. isbcomes from 204 and thus should be covered according to 9f31e5c#diff-9cd7dc3a9e57c8e575367094c6f3306bR1074. oth should also be covered.

I wonder why the roles have to be mentioned in the morph at all. We could just take the code from subfield 4 and put it behind the namespace id http://id.loc.gov/vocabulary/relators/...

@ChristophEwertowski
Copy link
Contributor

The files mentioned above have the roles in the subfield 4 of the 100s and 200s datafields. We can't take the roles only from the subfield 4 because there are next to none entries.

@acka47
Copy link
Contributor Author

acka47 commented Mar 7, 2017

The files mentioned above have the roles in the subfield 4 of the 100s and 200s datafields.

As I said above, this is not the case for HT018770176, HT019093814, HT018786244 and HT018924091 where pbl is in subfield 4 of 677.

I guess, we can leave out oth in the conversion as it doesn't add useful information.

However, I think we should transform isb (i.e. add it to the morph) and show it as "Herausgeber/in" in the labels.json (similar to edt).

@ChristophEwertowski
Copy link
Contributor

Added the role "issuing body" with the label "Herausgeber" to the files. @fsteeg : I suppose, since it's a new role, although with an already existing label, it isn't shown in the gui, is it? At least I can't see it with a new test index.

@fsteeg
Copy link
Member

fsteeg commented Mar 7, 2017

Not sure where it's supposed to be in the data.

Also, you can always use the link in the upper right corner of the details table:

http://test.lobid.org/resources/HT018770176

to check if it's in the JSON:

http://test.lobid.org/resources/HT018770176?format=json

In general I'd hope that a new role should show up in the UI automatically.

@acka47
Copy link
Contributor Author

acka47 commented Mar 8, 2017

This is the file with the isb role: http://test.lobid.org/resources/HT018889713. I can't find it in the RDF.

@ChristophEwertowski
Copy link
Contributor

Improved the regular expression so that issuing body is now shown as "Herausgeber/in" (example (test) / example (production). But now the responsibility statement isn't shown anymore although I didn't changed anything about it (see example above). @fsteeg : Is the responsibility statement only shown if there is no "Herausgeber"?

Also the issuing body can now be seen in the frontend but can't be found in the json file (json of the same example). Does anybody have an idea what the reason for this is?

@fsteeg
Copy link
Member

fsteeg commented Mar 15, 2017

Latest changes were not deployed to test system, updated it: http://test.lobid.org/resources/HT018889713

@acka47
Copy link
Contributor Author

acka47 commented Mar 15, 2017

Looks good to me. +1

@ChristophEwertowski ChristophEwertowski removed their assignment Mar 15, 2017
@dr0i dr0i added deploy and removed review labels Mar 17, 2017
@dr0i dr0i self-assigned this Mar 17, 2017
@dr0i dr0i added review and removed deploy labels Mar 17, 2017
@dr0i dr0i removed their assignment Mar 21, 2017
@dr0i dr0i added deploy and removed review labels Mar 21, 2017
@dr0i
Copy link
Member

dr0i commented Mar 23, 2017

Deployed to stage.

@acka47
Copy link
Contributor Author

acka47 commented Mar 23, 2017

Just noticed that art ("Künstler/in", example http://lobid.org/resources/HT018782520) and cmp ("Komposition", example lobid.org/resources/HT018782520) aren't taken into account in the transformation yet. Anyway, +1 and please deploy to production. I opened another issue for these two at #336.

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

No branches or pull requests

4 participants