May 2012 - Koha-bugs - lists.koha-community.org

[Bug 6533] New: Enhancement: Printer Friendly Lists
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '12

05 Nov '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6533 Bug #: 6533 Summary: Enhancement: Printer Friendly Lists Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: helen.linda(a)goddard.edu QAContact: koha-bugs(a)lists.koha-community.org Lists currently print without navigational elements, but they do print with images. A great feature would be to create a printer friendly version that strips out all the images in addition to nav elements so that it is compact and clean: 1. Could be something like Gmail has for printing an email, wherein you click print and it opens the "Printer-Friendly" version in a new window in addition to the printer dialog box. 2. Could have options set on the staff side for what an insitution would wanto print. Some places might wish to keep elements, like cover art, that others would not. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 2

[Bug 7192] New: can't print in FF without tools permission
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '12

30 Oct '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7192 Bug #: 7192 Summary: can't print in FF without tools permission Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 - low Component: Browser compatibility AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: ian.walls(a)bywatersolutions.com Created attachment 6254 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=6254 permissions Okay this is a weird one! I made it critical though because I still can't FF to open back up after it crashed due to this bug. It's Firefox 7.0.1 on Windows 7, Mac OS X 10.7.2 and Debian 6. I also tried Iceweasel 7.0 (Debian's rebranded Firefox) with the same results. Chrome on Mac OS X did not cause a crash. 1. Create a patron with permissions to match the attachment. 2. Log in as that patron to the staff client 3. Visit any patron detail page 4. Go to File > Print in the browser 5. Print the page 6. FF will crash miserably! Give that patron Tools permissions and repeat the steps above and you can print just fine. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 5

[Bug 6090] New: empty mails are sent
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '12

26 Oct '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6090 Bug #: 6090 Summary: empty mails are sent Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Notices AssignedTo: henridamien(a)koha-fr.org ReportedBy: julian.maurice(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 29

[Bug 6283] New: no way to enter price when ordering from a batch
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '12

25 Oct '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6283 Bug #: 6283 Summary: no way to enter price when ordering from a batch Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Created attachment 4017 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=4017 no price field When you're ordering from a staged marc record the form that appears with item information does not let you enter the pricing info ... is this by design or an oversight? I think that there should be a way to enter in the pricing info for each title or at least tell Koha what field the vendor has put that info in so that it's imported. As it stands now you have to touch each record you import after the fact. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 2

[Bug 7445] New: Clicking on a tag gives "Language ... does not exist"
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '12

24 Oct '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7445 Bug #: 7445 Summary: Clicking on a tag gives "Language ... does not exist" Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: magnus(a)enger.priv.no QAContact: ian.walls(a)bywatersolutions.com To reproduce: - Install another language alongside English - Make sure this language is chosen in the OPAC - Click on a tag, either in a result list or on the "Tag cloud" page - The message "Language 'nb-no' does not exist" is displayed (or some other language code) When English is the chosen language, things work as expected. I have tested this on current master and 3.6.2, and the problem is the same in both places. It can be seen in master here: http://head.bibkat.no/cgi-bin/koha/opac-tags.pl (Remember to choose Norwegian as language) See also attached screenshot. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 19

[Bug 5116] New: Duplicate and missing entries in "apt-get-debian-lenny.sh"
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '12

24 Oct '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5116 Summary: Duplicate and missing entries in "apt-get-debian-lenny.sh" Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: Linux Status: NEW Severity: minor Priority: P5 Component: Installation and upgrade (command-line installer) AssignedTo: gmcharlt(a)gmail.com ReportedBy: ricmarques(a)spamcop.net QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Today (11-Aug-2010), I did a git clone from the Koha "master" branch - the branch that will lead to the 3.2 version - to a machine running Debian 5.0.5 (Debian "lenny") I ran the "apt-get-debian-lenny.sh" install script - located at "install_misc/apt-get-debian-lenny.sh" I noticed, in that script, there were some missing lines for packages that exist for Debian Lenny and that have versions that satisfy the requirements of the Koha Installer, listed in the "PerlDependencies.pm" file - located at "C4/Installer/PerlDependencies.pm" - namely: - libnet-server-perl "Net::Server" module. "PerlDependencies.pm" requires version 0.97 ('min_ver' => '0.97') and the debian package for Lenny - http://packages.debian.org/lenny/libnet-server-perl - is version "0.97-1", thus satisfying the version requirement. - libpdf-table-perl "PDF::Table" module. "PerlDependencies.pm" requires version 0.9.3 ('min_ver' => '0.9.3') and the debian package for Lenny - http://packages.debian.org/lenny/libpdf-table-perl - is version "0.9.3-2", thus satisfying the version requirement. I also noticed, in that same "apt-get-debian-lenny.sh" script, that there were some duplicate entries / lines for other modules. So: 1 - I added the missing "libnet-server-perl" and "libpdf-table-perl" lines 2 - I removed the duplicate entries I'll submit a patch, through git, and link it to this Bug Report. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 3

[Bug 6610] New: Integration of Google Analytics in Koha.
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '12

24 Oct '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6610 Bug #: 6610 Summary: Integration of Google Analytics in Koha. Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: juan.sieira(a)xercode.es QAContact: koha-bugs(a)lists.koha-community.org New system preference for the introduction of Google Analytics in the Koha ILS. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 17

[Bug 7818] New: support DOM mode for Zebra indexing of bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '12

24 Oct '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7818 Priority: P5 - low Change sponsored?: --- Bug ID: 7818 Assignee: gmcharlt(a)gmail.com Summary: support DOM mode for Zebra indexing of bibliographic records QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: gmcharlt(a)gmail.com Hardware: All Status: NEW Version: unspecified Component: Architecture, internals, and plumbing Product: Koha Koha DOM Indexing for bibliographic records ------------------------------------------- Overview ======== Koha uses the Zebra search engine to implement bibliographic and authority record search. Zebra comes with several filters that support the indexing of various document types, including MARC and XML. Koha currently uses Zebra’s GRS-1 filter for indexing MARC and Zebra’s DOM filter for indexing authority records (represented as MARCXML). To oversimplify a bit, the GRS-1 filter allows for constructing the following kinds of search indexes for MARC records: Keyword and phrase indexes of the contents of a MARC subfield Keyword and phrase indexes of the contents of a fixed field What the GRS-1 index cannot provide, however, is the ability to index a phrase that spans subfield boundaries. For example, giving the subject heading: 650 $a Cats $x pharmacology $x catnip it is not possible to construct a search that will reliably match all instances of the phrase “cats pharmacology catnip”. This in turn means that it is not possible to reliably search on a bibliographic or authority heading with out extensive post-search pruning of the result set. The DOM filter, in contrast, takes an XML document (in this case, a MARC XML record) and applies a stylesheet to generate another XML document that contains all of the strings to be indexed by Zebra. This allows for much more flexibility, and in particular, allows for retrieving records on normalized heading. Furthermore, since the indexing definitions are ultimately expressed as an XML stylesheet, the DOM filter allows for an arbitrary amount of manipulation of tokens and phrases to be made during indexing. Goals ===== The goals of this development project are to: * Add support for the Zebra DOM filter for indexing bibliographic records in Koha, similar to existing support for DOM indexing of authority records. * Make use of DOM indexing to allow for complete and partial searches of headings fields. * Provide indexing definitions to allow for searching of title phrases that span subfield boundaries in the 245. Components ========== Indexing Preparation ==================== A new class (Koha::Indexer) hierarchy will be created to manage preparation of biblio and authority XML records for indexing. In the case of a bib record, biblionumber → MARC::Record representation of bib → one or more Koha::Indexer::MARC::RecordNormalizer routines that perform operations on the MARC::Record object. The one normalizer to be added for this project will be Koha::Indexer::MARC::RecordNormalizer::EmbedItems. → MARCXML representation of bib → Zebra indexing pipeline Two tables will be defined to allow for specifying pre-indexing record normalizer profiles record_norm_profile code varchar2(10) PK name varchar2(100) metadata_type varchar2(10) -- currently only ‘MARC’ record_type varchar2(10) -- ‘bilbio’ or ‘authority’ record_norm_profile_normalizer seq int -- order in which normalizer is to be applied record_norm_profile FK references record_norm_profile.code normalizer varchar2(100) -- references available Koha::Indexer::$metadata_type::RecordNormalizer classes The normalization pipeline will be used by rebuild_zebra.pl. DOM indexing The koha-indexdefs-to-zebra.xsl stylesheets currently used for DOM indexing of authorities will be made available to biblio as well. In addition XSLT functions will be added that can -- trim nonfiling characters -- calculate the applicable thesaurus of a bibliographic subject heading A script (misc/maintenance/convert_record_abs_to_dom.pl) will be written that will convert indexing definitions from record.abs to DOM format. For example: melm 022$a ISSN:w,Identifier-standard:w would be come something like this: <kohaidx:index_subfields tag="022" subfields="a"> <kohaidx:target_index>ISSN:w</kohaidx:target_index> <kohaidx:target_index>Identifier-standard:w</kohaidx:target_index> </kohaidx:index_subfields> In addition to handling converting existing record.abs config files, additional new standard indexing definitions will be added to index authority-controlled headings fields the same way as they are currently indexed in authority records. For example, topical subject headings will use: <kohaidx:index_heading tag="650" subfields="abvxyz" subdivisions="vxyz"> <kohaidx:target_index>Subject-topical-heading:w</kohaidx:target_index> <kohaidx:target_index>Subject-topical-heading:p</kohaidx:target_index> <kohaidx:target_index>Subject-topical-heading:s</kohaidx:target_index> <kohaidx:target_index>Heading:w</kohaidx:target_index> <kohaidx:target_index>Heading:p</kohaidx:target_index> <kohaidx:target_index>Heading:s</kohaidx:target_index> </kohaidx:index_heading> Headings index definitions will be provided in at least two variants: heading as a phrase heading as a phrase with insertions to include subdivision markers and thesaurus -- this type is meant to be used for future work for linking bib records to authority headings Searching enhancements ====================== The new standard indexing definitions will include two whole-245-as-phrase indexes, with one variant including nonfiling characters and the other excluding them. OPAC display enhancements ========================= The OPAC display XSLT (MARC21slim2OPACDetail.xsl) will be changed so that subject heading links will construct phase searches instead of searches on the subfield $9: The Koha interface should be updated to allow for user to select partial subject headings from the OPAC and staff client Details pages. for example, on a record with subject heading “History -- United States -- 18th Century -- Periodicals”, clicking: History would search for “History” United States would search for “History -- United States” 18th Century would search for “History -- United States -- 18th Century” Periodicals would search for “History -- United States -- 18th Century -- Periodicals” The advanced search page template will include an exact-title search that will perform an whole-phrase search on the new whole-245-as-phrase indexes. The subject search in the masthead and advanced search templates will be changed to use the new subject heading index, allowing for partial heading searches. Installation and upgrade considerations ======================================= During installation, a new query will be adding to Makefile.PL to specify the biblio indexing mode. The default value will be DOM. During upgrade, an option will be presented to convert the indexing definitions to DOM and reindex the biblio records. The specific upgrade steps will include: -- running misc/maintenance/convert_record_abs_to_dom.pl to create a biblio-koha-indexdefs.xml that includes the existing indexing definitions as well as the new standard bib headings indexes. -- using koha-indexdefs-to-zebra.xsl and an XSLT processor to create an biblio-zebra-indexdefs.xml to be used as the stylesheet that Zebra uses directly to convert incoming MARCXML records to their indexed phrases. -- running rebuild_zebra.pl -b -r on the entire database -- You are receiving this mail because: You are watching all bug changes.

1 60

[Bug 7751] New: Decrease loan period on items with a high number of holds
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '12

23 Oct '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7751 Priority: P5 - low Change sponsored?: --- Bug ID: 7751 CC: gmcharlt(a)gmail.com Assignee: kyle.m.hall(a)gmail.com Summary: Decrease loan period on items with a high number of holds QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: chris(a)bigballofwax.co.nz Hardware: All Status: NEW Version: master Component: Circulation Product: Koha Controlled by a syspref, this will reduce the amount of time something can be onloan, if it has a lot of holds on it -- You are receiving this mail because: You are watching all bug changes.

1 70

[Bug 7378] New: It should be possible to auto increment 952$i inventory number based on a system preference
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '12

19 Oct '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7378 Bug #: 7378 Summary: It should be possible to auto increment 952$i inventory number based on a system preference Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support AssignedTo: gmcharlt(a)gmail.com ReportedBy: kmkale(a)anantcorp.com QAContact: ian.walls(a)bywatersolutions.com It should be possible to auto increment 952$i inventory number based on a system preference -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 2