Bug 18892 - RDA fields not searchable as Publisher
Summary: RDA fields not searchable as Publisher
Status: RESOLVED DUPLICATE of bug 15704
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-04 22:26 UTC by Barton Chittenden
Modified: 2020-01-11 21:34 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Barton Chittenden 2017-07-04 22:26:03 UTC
Bug 14198 - RDA: Indexing 264 field (Zebra) added an index called 'Provider' (with a CCL mapping of 'pv').

However, this does not allow bibs cataloged under RDA to be searched using the 'Publisher' search.

Library of congress shows that 264 indicator 2 can be used to distinguish manufacture and distribution vs. publication:

Second Indicator - Function of entity
0 - Production
Field contains a statement relating to the inscription, fabrication, construction, etc., of a resource in an unpublished form.

1 - Publication
Field contains a statement relating to the publication, release, or issuing of a resource.

2 - Distribution
Field contains a statement relating to the distribution of a resource.

3 - Manufacture
Field contains a statement relating to the printing, duplicating, casting, etc., of a resource in a published form.

4 - Copyright notice date
Field contains a date associated with a notice of protection under copyright or a similar regime. Copyright dates include phonogram dates (i.e., dates associated with claims of protection for sound recordings).

... so indicator 2 values of 1 or 4 should correspond to publisher. We have the ability to specify indicator values when indexing; we should use it in this case.
Comment 1 Katrin Fischer 2020-01-11 21:34:49 UTC

*** This bug has been marked as a duplicate of bug 15704 ***