In MARC 21 authority records, three bytes (008/14-16) indicate what the heading can be used for (main/added entry, subject entry, series entry). Koha should be able to respect the record's intended use in authority search during cataloging, provided that the authority file is well formed. Also, we should be able to decide between more strict but correct behavior and current lax behavior.
I think so too :) I can't remember whether I actually looked at whether you could do it with LinkerOptions rather than yet another pref, though. *** This bug has been marked as a duplicate of bug 33296 ***
This is not a duplicate to Bug 33296. Automated linker will be the next step. This is for cataloging authority finder, which is, technically, not connected with the linker.
Created attachment 174863 [details] [review] Bug 38494: Add 'ConsiderHeadingUse' system preference Add new system preference 'ConsiderHeadingUse' to by able to consider the intended use of authority records (008/14-16) during cataloging and linking.
Created attachment 174864 [details] [review] Bug 38494: Koha should consider authority heading use in cataloging In MARC 21 authority records, three bytes (008/14-16) indicate what the heading can be used for (main/added entry, subject entry, series entry). Koha should be able to respect the record's intended use in authority search during cataloging, provided that the authority file is well formed. Also, we should be able to decide between more strict but correct behavior and current lax behavior. Test plan: ---------- 1. Apply the patch; updatedatabase ; restart_all 2. Set the ShowHeadingUse system preference to ‘Show’ 3. Go to the Cataloging editor and open the authority finder plugin for the 100 field. Search for Peter. With standard ktd test data you should get 9 results, some with ‘v’ before Main/Added Entry, some with ‘x’. These with ‘x’ are not to be used in this context, provided you use a well-formed authority file 4. Set ConsiderHeadingUse system preference to ‘Do’ 5. Repeat p. 3. You should get now only 4 Peters – those with ‘v’ before Main/Added Entry (008/14 = ‘a’) 6. You can repeat the test for subject headings (6XX) and series headings (sometimes you would have to modify the test data, e.g. there are few authority records with 008/16 = ‘a’ (series use) 7. This should work equally with Zebra and with Elasticsearch
Created attachment 174865 [details] [review] Bug 38494: Add 'ConsiderHeadingUse' system preference Add new system preference 'ConsiderHeadingUse' to be able to consider the intended use of authority records (008/14-16) during cataloging and linking. Sponsored-by: Ignatianum University in Cracow
Created attachment 174866 [details] [review] Bug 38494: Koha should consider authority heading use in cataloging In MARC 21 authority records, three bytes (008/14-16) indicate what the heading can be used for (main/added entry, subject entry, series entry). Koha should be able to respect the record's intended use in authority search during cataloging, provided that the authority file is well formed. Also, we should be able to decide between more strict but correct behavior and current lax behavior. Test plan: ---------- 1. Apply the patch; updatedatabase ; restart_all 2. Set the ShowHeadingUse system preference to ‘Show’ 3. Go to the Cataloging editor and open the authority finder plugin for the 100 field. Search for Peter. With standard ktd test data you should get 9 results, some with ‘v’ before Main/Added Entry, some with ‘x’. These with ‘x’ are not to be used in this context, provided you use a well-formed authority file 4. Set ConsiderHeadingUse system preference to ‘Do’ 5. Repeat p. 3. You should get now only 4 Peters – those with ‘v’ before Main/Added Entry (008/14 = ‘a’) 6. You can repeat the test for subject headings (6XX) and series headings (sometimes you would have to modify the test data, e.g. there are few authority records with 008/16 = ‘a’ (series use) 7. This should work equally with Zebra and with Elasticsearch Sponsored-by: Ignatianum University in Cracow
I need to investigate a bit more how it represents in MARC for us, but I know that for GND records you can use the same records for both main/added and subject. So we don't have that differentiation in our authority file I believe.
(In reply to Katrin Fischer from comment #7) > I need to investigate a bit more how it represents in MARC for us, but I > know that for GND records you can use the same records for both main/added > and subject. So we don't have that differentiation in our authority file I > believe. Of course, it is totally correct. In such a case the authority record should have 008/14-15 = 'aa'. I am aware that there are libraries with authority files of low quality, self/automatically generated, not paying attention to 008. Therefor this feature should be optional, with default = 'do not'. For us it is essential because we are using more than one authority file for subject heading and only one for main/added headings. It happens that in different authority files there are names of equal form but only one file should be used for main/added entries. And this is controlled by 008/14-16. The story is in some sense analogous to the use of different thesauri (cf. Bug 30280). Official MARC 21 documentation regarding this topic: https://www.loc.gov/marc/authority/ad008.html
Created attachment 174897 [details] [review] Bug 38494: Koha should consider authority heading use in cataloging In MARC 21 authority records, three bytes (008/14-16) indicate what the heading can be used for (main/added entry, subject entry, series entry). Koha should be able to respect the record's intended use in authority search during cataloging, provided that the authority file is well formed. Also, we should be able to decide between more strict but correct behavior and current lax behavior. Test plan: ---------- 1. Apply the patch; updatedatabase ; restart_all 2. Set the ShowHeadingUse system preference to ‘Show’ 3. Go to the Cataloging editor and open the authority finder plugin for the 100 field. Search for Peter. With standard ktd test data you should get 9 results, some with ‘v’ before Main/Added Entry, some with ‘x’. These with ‘x’ are not to be used in this context, provided you use a well-formed authority file 4. Set ConsiderHeadingUse system preference to ‘Do’ 5. Repeat p. 3. You should get now only 4 Peters – those with ‘v’ before Main/Added Entry (008/14 = ‘a’) 6. You can repeat the test for subject headings (6XX) and series headings (sometimes you would have to modify the test data, e.g. there are few authority records with 008/16 = ‘a’ (series use) 7. This should work equally with Zebra and with Elasticsearch Sponsored-by: Ignatianum University in Cracow
Created attachment 174898 [details] [review] Bug 38494: Add 'ConsiderHeadingUse' system preference Add new system preference 'ConsiderHeadingUse' to be able to consider the intended use of authority records (008/14-16) during cataloging and linking. Sponsored-by: Ignatianum University in Cracow
Created attachment 174899 [details] [review] Bug 38494: Koha should consider authority heading use in cataloging In MARC 21 authority records, three bytes (008/14-16) indicate what the heading can be used for (main/added entry, subject entry, series entry). Koha should be able to respect the record's intended use in authority search during cataloging, provided that the authority file is well formed. Also, we should be able to decide between more strict but correct behavior and current lax behavior. Test plan: ---------- 1. Apply the patch; updatedatabase ; restart_all 2. Set the ShowHeadingUse system preference to ‘Show’ 3. Go to the Cataloging editor and open the authority finder plugin for the 100 field. Search for Peter. With standard ktd test data you should get 9 results, some with ‘v’ before Main/Added Entry, some with ‘x’. These with ‘x’ are not to be used in this context, provided you use a well-formed authority file 4. Set ConsiderHeadingUse system preference to ‘Do’ 5. Repeat p. 3. You should get now only 4 Peters – those with ‘v’ before Main/Added Entry (008/14 = ‘a’) 6. You can repeat the test for subject headings (6XX) and series headings (sometimes you would have to modify the test data, e.g. there are few authority records with 008/16 = ‘a’ (series use) 7. This should work equally with Zebra and with Elasticsearch Sponsored-by: Ignatianum University in Cracow
Created attachment 174914 [details] [review] Bug 38494: Add 'ConsiderHeadingUse' system preference Add new system preference 'ConsiderHeadingUse' to be able to consider the intended use of authority records (008/14-16) during cataloging and linking. Sponsored-by: Ignatianum University in Cracow Signed-off-by: Roman Dolny <roman.dolny@jezuici.pl>
Created attachment 174915 [details] [review] Bug 38494: Koha should consider authority heading use in cataloging In MARC 21 authority records, three bytes (008/14-16) indicate what the heading can be used for (main/added entry, subject entry, series entry). Koha should be able to respect the record's intended use in authority search during cataloging, provided that the authority file is well formed. Also, we should be able to decide between more strict but correct behavior and current lax behavior. Test plan: ---------- 1. Apply the patch; updatedatabase ; restart_all 2. Set the ShowHeadingUse system preference to ‘Show’ 3. Go to the Cataloging editor and open the authority finder plugin for the 100 field. Search for Peter. With standard ktd test data you should get 9 results, some with ‘v’ before Main/Added Entry, some with ‘x’. These with ‘x’ are not to be used in this context, provided you use a well-formed authority file 4. Set ConsiderHeadingUse system preference to ‘Do’ 5. Repeat p. 3. You should get now only 4 Peters – those with ‘v’ before Main/Added Entry (008/14 = ‘a’) 6. You can repeat the test for subject headings (6XX) and series headings (sometimes you would have to modify the test data, e.g. there are few authority records with 008/16 = ‘a’ (series use) 7. This should work equally with Zebra and with Elasticsearch Sponsored-by: Ignatianum University in Cracow Signed-off-by: Roman Dolny <roman.dolny@jezuici.pl>