August 2014 - Koha-bugs - lists.koha-community.org

[Bug 4162] Inventory Tool Fails Silently
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '14

05 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4162 M. Tompsett <mtompset(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #29660|0 |1 is obsolete| | -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 4162] Inventory Tool Fails Silently
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '14

05 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4162 Marc Véron <veron(a)veron.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off CC| |veron(a)veron.ch -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 4162] Inventory Tool Fails Silently
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '14

05 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4162 --- Comment #5 from Marc Véron <veron(a)veron.ch> --- Created attachment 30548 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=30548&action=edit [Signed-off] Bug 4162 The inventory tool lacks validation for barcodes The inventory tool had no form of validating on what was assumed to be a valid barcode number. To solve this, an extra loop to read before processing was added. This allows to validate length and content (assumed that [:print:] was good enough). The template was modified to accomodate validation messages related to the length and content errors. TEST PLAN --------- 1) Attempt to select a file which does not contain barcodes and is not a text file. -- a horrible lack of validation and spamminess ensues. 2) Apply patch 3) Create three files. a) One containing valid barcodes on each line -- this file should trigger no errors. b) A copy of the first with an extra line of >20 characters (e.g. The Quick Red Fox Jumped Over The Brown Fence^A^B^C) -- this file should trigger the singular error message case. ^A^B^C are actually CTRL-A,CTRL-B,CTRL-C, and it is left as an exercise to the reader to add them to the line. c) A copy of the second with the last line duplicated -- this file should trigger the plural error message case. 4) Attempt each of the three files. 5) Run koha-qa tools. Followed test plan 1-4. Patch behaves as expected. Signed-off-by: Marc Véron <veron(a)veron.ch> -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 12712] New: Custom search facets
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '14

05 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12712 Bug ID: 12712 Summary: Custom search facets Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: vfernandes(a)keep.pt QA Contact: testopia(a)bugs.koha-community.org The librarian should be able to configure which data appears on refine search facets: libraries, locations, publication dates, authors, topics, subjects, etc. The search facets should be configurable. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 12477] New: We need better ways to manage MARC Frameworks
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '14

05 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12477 Bug ID: 12477 Summary: We need better ways to manage MARC Frameworks Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Authority data support Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org We need better ways to manage MARC frameworks for authority and bibliographic records (for new and existing instances). After a review of updatedatabase.pl, I noted 1 change to auth_tag_structure and 12 changes to auth_subfield_structure. According to http://www.loc.gov/marc/status.html, there have been a lot more than 13 changes in the past 15 years. I believe that bug 9826 and bug 10488 bring the authorities up to at least 2013 in terms of currency, which is great...for new installs. However, if you're an existing install, your authority frameworks (and your bibliographic frameworks) are going to be horribly out of date. As some people have pointed out, we can't necessarily automatically update frameworks, because people may have (ie probably have) customized their frameworks and an automatic update could lead to unexpected results. That being said, what do we need to update? 1) Missing fields 2) Missing subfields 3) Changes to "repeat" value 4) Maybe changes to labels (for when fields are renamed) The real "key", in my mind, to custom frameworks is visibility, the ability to add 'local' fields/subfields, and perhaps labels (for libraries who want less technical labels for cataloguing staff). If we automatically change "repeat" values transparently and push missing fields/subfields with a visibility of "hidden", then there are substantively no changes to the appearance or experience of frameworks in the editor or the detail/result/list pages. The one unexpected change might be if staff go to customize a framework and see a lot of standard fields that they deleted in the past. That...is a bit more of a puzzle. However, that puzzle can probably be solved in a few ways: 1) Inform users that standard fields/subfields will be periodically added/updated in the frameworks; or 2) Create a "Refresh" type button next to each framework which puts the updating of frameworks into the hands of library staff We could even include both these options and wrap the 1st one around a system preference that defaults to ON for new installs, and OFF for existing installs (so as to not change existing behaviour). In order for this all to work, I think we would need to move away from maintaining default frameworks as SQL files, and instead store them in something like YAML which can be easily loaded into a script that does the work. The majority of information stored in the frameworks is actually Koha-specific rather than MARC-specific. The only thing the frameworks contain relating to MARC are field codes, subfield codes, labels (i.e. liblibrarian and libopac), and repeat values. We could actually just store this MARC-specific data in the YAML file, and then build the Default and other Custom frameworks based on a Perl script, which would probably be easier to maintain than the SQL that we maintain now. Thoughts? -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 12715] New: Re-Build Zebra
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '14

04 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12715 Bug ID: 12715 Summary: Re-Build Zebra Change sponsored?: --- Product: Koha Version: 3.14 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: mpprasanth75(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The following error shown while running re build zebra command. ......................error retrieving biblio 6602 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 679. and while searching in advanced search calalouged items not seen. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 12711] New: Add support to new protocols
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '14

04 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12711 Bug ID: 12711 Summary: Add support to new protocols Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: vfernandes(a)keep.pt QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently Koha can only import records from Z39.50. This feature is to add support to other protocols than Z39.50 when importing records. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 12714] New: Export report in PDF
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '14

04 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12714 Bug ID: 12714 Summary: Export report in PDF Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: vfernandes(a)keep.pt QA Contact: testopia(a)bugs.koha-community.org New export option: PDF. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 12713] New: Mark records already in possession of the patron
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '14

04 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12713 Bug ID: 12713 Summary: Mark records already in possession of the patron Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: vfernandes(a)keep.pt QA Contact: testopia(a)bugs.koha-community.org Show in OPAC search results and in OPAC record details, something (a label, an image) that identifies if the logged patron had some item of the record on his possession. This will allow patrons identified which books books had read or not. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12710] New: Import/export reports
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '14

04 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12710 Bug ID: 12710 Summary: Import/export reports Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: vfernandes(a)keep.pt QA Contact: testopia(a)bugs.koha-community.org Add new option to import/export reports (something like import/export MARC frameworks). This allows librarians to share and edit reports instead of create them from scratch. I think this will be a good improvement to librarians that doesn't have MySQL knowlegdes. Can be also done a integration with Koha wiki reports page. -- You are receiving this mail because: You are watching all bug changes.

1 0