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

[Bug 7012] New: limit to available not limiting anymore
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7012 Bug #: 7012 Summary: limit to available not limiting anymore Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org When I limit to only available items in the OPAC it doesn't appear to be limiting anymore. -- 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 6

[Bug 11311] New: Browse selected authorities
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11311 Bug ID: 11311 Summary: Browse selected authorities Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 11051] New: Performance of opac-search
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11051 Bug ID: 11051 Summary: Performance of opac-search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: robin(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org I did a profile of opac-search and am going to make a few improvements to it. You can see the results here: http://debian.koha-community.org/~robin/opac-search/ This was run on a production 3.12.2 system, with 10 branches, with a database server on a different machine. This means that database latency is more visible. -- You are receiving this mail because: You are watching all bug changes.

1 45

[Bug 8609] New: Add an URL validation plugin for authority and biblio frameworks
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '15

09 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8609 Priority: P5 - low Change sponsored?: --- Bug ID: 8609 CC: m.de.rooy(a)rijksmuseum.nl Assignee: gmcharlt(a)gmail.com Summary: Add an URL validation plugin for authority and biblio frameworks Severity: enhancement Classification: Unclassified OS: All Reporter: fcapovilla(a)live.ca Hardware: All Status: NEW Version: master Component: Cataloging Product: Koha Created attachment 11511 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=11511&action=edit Add an URL validation plugin for authority and biblio frameworks. This patch adds a new validation plugin that can be used in biblio and authority frameworks. The plugin uses a regex to validate that a field contains a valid url. For example, this plugin could be used for field 856$u of MARC21 biblio and authority frameworks. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 9313] New: add fine amounts to overdue with fines
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '15

09 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9313 Bug ID: 9313 Summary: add fine amounts to overdue with fines Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All URL: cgi-bin/koha/circ/branchoverdues.pl OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Would be nice if we could see the fine amounts on the overdues with fines report: cgi-bin/koha/circ/branchoverdues.pl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 9321] New: holds queue printable version
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '15

09 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9321 Bug ID: 9321 Summary: holds queue printable version Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.8 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: nengard(a)gmail.com It would be nice if there were a printable stylesheet for the holds queue. Right now it's a print screen basically and that means that the table doesn't always fit on the page - in fact it never has for me. I think it should be a list or a thinner table or something a bit more printer friendly. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 10662] New: Build OAI-PMH Harvesting Client
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '15

09 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10662 Bug ID: 10662 Summary: Build OAI-PMH Harvesting Client Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Currently, Koha only acts as a OAI-PMH server, I propose to add a harvesting client as well (likely using the HTTP::OAI::Harvester module), so that Koha can ingest records from other data sources (such as digital repositories like Dspace). I've only started reading about it but despite initial reservations about resumption tokens, I think the hardest part will not be with the retrieval of records so much as the parsing of those records into MARC. The Library of Congress does provide some crosswalks (http://www.loc.gov/standards/marcxml/) for converting other metadata formats into MARC21. However, the DC to MARC crosswalk (which is the obvious choice for Dspace) does not produce records of a high quality. So, as part of this new feature, I will also be working on a more complete DC to MARC crosswalk. Their DCMI terms (http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=elements#type) have been mapped reasonably well to the MARC21 LEADER 6th and 7th positions, which improves the quality of the record and helps to produce a "best guess" 008. I'll be looking at adding more datafields and providing better fixed field transformation. Of course, some OAI-PMH repositories serve MARC so this crosswalk might not always be necessary. However, I've looked at Dspace's DC=>MARC crosswalk and it's similar to the LoC one, so I think this will be a valuable addition (both to Koha and to anyone wanting to transform DC to MARC21). As I mentioned, I'm just starting out with OAI-PMH, but I imagine having Koha as a OAI-PMH harvester might be useful in union catalogue situations where other servers might send quality MARC records. -- My plan: 1) Set up a script that is able to continuously harvest records from a OAI-PMH server (likely Dspace or Koha itself for my trials) 2) Set up a database table to handle harvester configuration (such as baseurl, sets, (possibly dates), metadata format, and any pointers to XSLTs. 3) Set up a solid (yet likely basic) DC => MARC XSLT. If anyone has comments or advice, I'd love to hear it. Hopefully, I'll be able to focus on this over the next little while... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 79

[Bug 7985] New: In Checkout, list of items checked out should show Charge from table accountlines
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '15

08 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7985 Priority: P5 - low Change sponsored?: --- Bug ID: 7985 CC: gmcharlt(a)gmail.com Assignee: kyle.m.hall(a)gmail.com Summary: In Checkout, list of items checked out should show Charge from table accountlines QA Contact: koha.sekjal(a)gmail.com Severity: normal Classification: Unclassified OS: All Reporter: veron(a)veron.ch Hardware: All Status: NEW Version: unspecified Component: Circulation Product: Koha Created attachment 9262 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=9262&action=edit List of fines&charges (above) and list of checkouts (below). Do the following: ----------------- - Check out some items from a certain item type (to saem patron) - Modify item type, change Rental charge - Check out additional item to same patron Result: ------- In the list of checkouts, all items show the new rental charge and not the Rental charge that was applied at chckout time. Totals differ. This situation will result in a lot of support questions. See screenshot in attachment, first and second item were issued with a rental charge of 1.01 and 3rd with a rental charge of 1.02. The values are displayed correctly under the fines tab. Fazit: ------ The list of checkouts should be linked with the table accountlines instead of grabbing the current value of the rental charge from the item type. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 7041] New: Sort >1000 search results with sortmax parameter in zebra config file
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '15

08 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7041 Bug #: 7041 Summary: Sort >1000 search results with sortmax parameter in zebra config file Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: m.de.rooy(a)rijksmuseum.nl QAContact: koha-bugs(a)lists.koha-community.org By default, zebra does not sort more than 1000 records (search results). You can increase this number by adding the sortmax parameter in zebra-biblios.cfg. Putting this value in Koha's zebra config file will make this default value visible and make it easier to increase it if one prefers that. This patch therefore adds the default of 1000 to zebra-biblios.cfg. Does not change any Koha/Zebra behavior. If you want to test it, look for a search in your catalog with >1000 results. Look at the order of the records. Now apply the patch and copy the zebra-biblios.cfg to your zebra directory. Increase sortmax, reindex and search again. If you increased sortmax above the number of hits, you should see a difference in sort order now. -- 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 11

[Bug 9163] New: Cataloguing validation workflow
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '15

08 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9163 Bug ID: 9163 Summary: Cataloguing validation workflow Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: vfernandes(a)keep.pt CC: m.de.rooy(a)rijksmuseum.nl New feature to have cataloguing validation workflow (some user validates the cataloguing of others and put the record online in OPAC). The idea is the following: - all framework needs to have suppress subfield hidden - the normal cataloguers uses this frameworks to catalogue the record - the record will not have suppress subfield filled (I don't know what happens when the record has no suppress - if it appears there is the need of set suppress = 1 automatically) - there is special framework with suppress subfield visible - only some users have access to the special framework - those users uses the special framework to validate the cataloguing and set suppress = 0 if everything is OK (after indexation the record appears online in OPAC) To have this working there is the need of a multi system preference with 3 options: 1 - Turn on/off the validation workflow (controll the appearing of the special framework in the dropdown list in addbook.pl and addbiblio.pl, set suppress = 1 if needed, etc) 2 - Set which will be the special framework (text box to set the framework code) 3 - List of users with access to this functionallity separated by comma (can be a permission but if the validation is off the permission has no sense, can be a file in the Koha structure with each username in one line, etc...) -- You are receiving this mail because: You are watching all bug changes.

1 40