Bug 38494 - Koha should consider authority heading use in cataloging
Summary: Koha should consider authority heading use in cataloging
Status: Signed Off
Alias: None
Product: Koha
Classification: Unclassified
Component: MARC Authority data support (show other bugs)
Version: unspecified
Hardware: All All
: P3 enhancement
Assignee: Janusz Kaczmarek
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks: 33296 38514
  Show dependency treegraph
 
Reported: 2024-11-20 12:56 UTC by Janusz Kaczmarek
Modified: 2024-11-23 16:02 UTC (History)
2 users (show)

See Also:
Change sponsored?: Sponsored
Patch complexity: Small patch
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments
Bug 38494: Add 'ConsiderHeadingUse' system preference (3.69 KB, patch)
2024-11-20 23:12 UTC, Janusz Kaczmarek
Details | Diff | Splinter Review
Bug 38494: Koha should consider authority heading use in cataloging (3.02 KB, patch)
2024-11-20 23:12 UTC, Janusz Kaczmarek
Details | Diff | Splinter Review
Bug 38494: Add 'ConsiderHeadingUse' system preference (3.74 KB, patch)
2024-11-20 23:16 UTC, Janusz Kaczmarek
Details | Diff | Splinter Review
Bug 38494: Koha should consider authority heading use in cataloging (3.07 KB, patch)
2024-11-20 23:17 UTC, Janusz Kaczmarek
Details | Diff | Splinter Review
Bug 38494: Koha should consider authority heading use in cataloging (4.18 KB, patch)
2024-11-21 16:41 UTC, Janusz Kaczmarek
Details | Diff | Splinter Review
Bug 38494: Add 'ConsiderHeadingUse' system preference (3.75 KB, patch)
2024-11-21 16:45 UTC, Janusz Kaczmarek
Details | Diff | Splinter Review
Bug 38494: Koha should consider authority heading use in cataloging (3.08 KB, patch)
2024-11-21 16:45 UTC, Janusz Kaczmarek
Details | Diff | Splinter Review
Bug 38494: Add 'ConsiderHeadingUse' system preference (3.80 KB, patch)
2024-11-22 08:38 UTC, Roman Dolny
Details | Diff | Splinter Review
Bug 38494: Koha should consider authority heading use in cataloging (3.13 KB, patch)
2024-11-22 08:38 UTC, Roman Dolny
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Janusz Kaczmarek 2024-11-20 12:56:11 UTC
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.
Comment 1 Phil Ringnalda 2024-11-20 21:38:37 UTC
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 ***
Comment 2 Janusz Kaczmarek 2024-11-20 23:11:09 UTC
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.
Comment 3 Janusz Kaczmarek 2024-11-20 23:12:57 UTC
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.
Comment 4 Janusz Kaczmarek 2024-11-20 23:12:59 UTC
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
Comment 5 Janusz Kaczmarek 2024-11-20 23:16:58 UTC
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
Comment 6 Janusz Kaczmarek 2024-11-20 23:17:00 UTC
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
Comment 7 Katrin Fischer 2024-11-21 09:20:10 UTC
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.
Comment 8 Janusz Kaczmarek 2024-11-21 10:37:10 UTC
(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
Comment 9 Janusz Kaczmarek 2024-11-21 16:41:15 UTC
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
Comment 10 Janusz Kaczmarek 2024-11-21 16:45:16 UTC
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
Comment 11 Janusz Kaczmarek 2024-11-21 16:45:19 UTC
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
Comment 12 Roman Dolny 2024-11-22 08:38:52 UTC
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>
Comment 13 Roman Dolny 2024-11-22 08:38:54 UTC
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>