October 2013 - Koha-bugs - lists.koha-community.org

[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

[Bug 10121] New: unhighlight doesn't carry over to other pages
by bugzilla-daemon＠bugs.koha-community.org 07 Dec '15

07 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10121 Bug ID: 10121 Summary: unhighlight doesn't carry over to other pages Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nengard(a)gmail.com I I click 'unhighlight' on page 1 of my results and then go to page 2 it's highlighted. My option to 'unhighlight' should carry over. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 9495] New: split NotesBlacklist in to two prefs for staff and OPAC
by bugzilla-daemon＠bugs.koha-community.org 07 Dec '15

07 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9495 Bug ID: 9495 Summary: split NotesBlacklist in to two prefs for staff and OPAC Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com CC: gmcharlt(a)gmail.com Depends on: 9162 It would be nice if the NotesBlacklist preference were actually 2 - one for the opac and one for the staff clients. Often staff will want to hide local notes (590) from the OPAC but will want to see them in the staff client still. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 8290] New: Replace Greybox library with jQueryUI Dialog
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '15

05 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8290 Priority: P5 - low Change sponsored?: --- Bug ID: 8290 Assignee: oleonard(a)myacpl.org Summary: Replace Greybox library with jQueryUI Dialog Severity: enhancement Classification: Unclassified OS: All Reporter: oleonard(a)myacpl.org Hardware: All Status: NEW Version: master Component: Templates Product: Koha jQueryUI includes a Dialog widget which can replace the Greybox library. Doing so will make the UI of dialogs in Koha consistent with other jQueryUI components and offer a tool which can be expanded into a wider array of usages. http://jqueryui.com/demos/dialog/ -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 7411] New: remove diacritics when automatically generating userid
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '15

05 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7411 Bug #: 7411 Summary: remove diacritics when automatically generating userid Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: sophie.meynieux(a)biblibre.com QAContact: ian.walls(a)bywatersolutions.com CC: gmcharlt(a)gmail.com When userid is automatically generated from firstname and surname, diacritics should be removed because login with diacritics may results in failure -- 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 23

[Bug 5517] New: After removal of koha-common package in Debian Squeeze cron jobs are not deleted
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '15

05 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5517 Summary: After removal of koha-common package in Debian Squeeze cron jobs are not deleted Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Packaging AssignedTo: robin(a)catalyst.net.nz ReportedBy: gaurav.paliwal1989(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 When someone remove the koha-common in debian squeeze the cron jobs that are automatically added at the time of installation are not automatically removed even after the complete removal of the koha-common package. -- 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 8

[Bug 7021] New: patron category in the statistics table
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '15

04 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7021 Bug #: 7021 Summary: patron category in the statistics table Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com The patron category code should be in the statistics table. We track the item type and item number, but we only track the borrowernumber for the patron and part way through the year the patron's category could change from child to adult - or the patron could be deleted and that will mess with the statistics on circulation/actions based on patron category. Once that data is added to that table, the circulation stats wizard will need to be updated as well. -- 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