http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14198

--- Comment #1 from Héctor Eduardo Castro Avalos <hector.hecax...@gmail.com> ---
Created attachment 39301
  -->
http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=39301&action=edit
Bug 14198: RDA: Indexing 264 field (Zebra) This patch add zebra indexes to RDA
264 field. The new Provider index is added too. The XSLT for staff and OPAC has
been updated to reflect the index.

To test:
1) Download RDA records with 264 fields from this attachment
<http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=36825>. Import the
file and re-index/rebuild zebra. These records contain 260 and 264 fields per
record.
2) Do a search with pb:Bethany two records will appear with title The guardian.
Search with pl:Minneapolis too, the two records will appear. Notice that 264
not show the link for Publisher in the record detail page.
3) Select one record of both records and delete the 260 field keeping the 264
field and save, rebuild your zebra.
4) Search again with pb:Bethany and just one record will appear. Thats mean 264
is not indexed.
5) Apply patch.
6) Rebuild your zebra but this time all biblio records.
7) Search again with pb:Bethany, this time will appear the two records, 264 is
indexed.
8) This patch add three new indexes Provider, Provider-date and Provider-place
for 260 and 264 fields.
9) Do a search with the three new indexes for Bethany publisher.
10) Search with copydate:2013 and Provider-date:2013 both searches will give
the same result.
11) Get access to record detail page of one record and notice that the link for
Publisher in 264 field appear.

Sponsored-by: Universidad de El Salvador

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to