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

[Bug 11290] New: members-home.pl displays badly if using non english templates and have a utf8 char in categorycode description
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '14

06 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11290 Bug ID: 11290 Summary: members-home.pl displays badly if using non english templates and have a utf8 char in categorycode description Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: chris(a)bigballofwax.co.nz QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 11513] New: Warnings in Patron categories
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '14

06 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11513 Bug ID: 11513 Summary: Warnings in Patron categories Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Floody warnings were discovered during testing Koha. To reproduce what was discovered: 1) Log in to staff client 2) Click 'Administration' 3) Click 'Patron categories' 4) Review error log, several warnings. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 11138] New: Auto-unsuspend holds not in default cronjobs
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '14

06 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11138 Bug ID: 11138 Summary: Auto-unsuspend holds not in default cronjobs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Auto Unsuspend holds is not in the cronjobs by default in the packages. It should be in the defaults. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 11363] New: Label printer profile units are not translatable
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '14

06 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11363 Bug ID: 11363 Summary: Label printer profile units are not translatable Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)pttk.fi QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Tools > Labels > Printer profiles > Edit printer profile has a pull-down for printing units. The pull-down has entries such as "Postscript Points", "Adobe Agates", etc. The values in the pull-down cannot be translated. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 10691] New: 5xx not properly linked by authid in authority search result list
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '14

06 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10691 Bug ID: 10691 Summary: 5xx not properly linked by authid in authority search result list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: jcamins(a)cpbibliography.com Authority search in OPAC does not use the authid for creating the link in the result list, but it does on the detail page. Example: https://eh-freiburg.bsz-bw.de/cgi-bin/koha/opac-authorities-home.pl?op=do_s… Heading: Schmidt, Andrea Link: Betriebswirtin -- You are receiving this mail because: You are watching all bug changes.

1 60

[Bug 9611] New: Changing the password hashing algorithm from MD5 to more secure Bcrypt
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '14

06 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9611 Bug ID: 9611 Summary: Changing the password hashing algorithm from MD5 to more secure Bcrypt Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: srikanth(a)catalyst.net.nz CC: dpavlin(a)rot13.org In the current version of Koha, the passwords are stored as md5 hashes. MD5 hashing has its limitations, changing the hashing method to Bcrypt will improve in more secure password storage. -- You are receiving this mail because: You are watching all bug changes.

1 110

[Bug 11472] New: MARC21 008 plugin should consult leader to set default type of material
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '14

06 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11472 Bug ID: 11472 Summary: MARC21 008 plugin should consult leader to set default type of material Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently, when you use the MARC21 008 plugin to edit field positions, the type of material is always set to BKS, regardless of the actual material type of the record. This means that you always have to change the material type in the fixed field editor to the appropriate value. It would be nice if the type of material were determined by the current leader value. The "material type" in this context is determined by the Leader/06 and Leader/07. The "input conventions" heading near the bottom of http://www.loc.gov/marc/bibliographic/bdleader.html contains a "dependencies" section that designates the appropriate material type for the 008 based on the Leader/06-07. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 10438] New: Packages naming/versioning broken
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '14

05 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10438 Bug ID: 10438 Summary: Packages naming/versioning broken Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com CC: robin(a)catalyst.net.nz Our current packages naming and versioning doesn't support what we claim: if someone wants to maintain an specific version then we'll let him. It is also unnecesarilly complex for the users too. The current schema provides only two stable versions support at a given time, with 'oldstable' and 'stable' dists as a way of specifying that. Not only has that versions limitation (which could be fixed adding something like 'olderoldstable') but is also difficult for the user who has to check whether to change stable to oldstable to avoid unwanted version jump. This makes maintenance difficult even for IT stuff (is not *that* difficult, but is unnecesary). I propose changing the packages naming schema to something like: - Dists: stable (for the stable releases), devel (for the development branches) - Packages naming/version: pick the one VirtualBox uses and have: koha-common-3.8 koha-common-3.10 koha-common-3.12 and so on as packages names. Versioned with their corresponding full version (with minor release number) as it obvoiusly should. I think changing ths should be a minor task, and would make install instructions easier to write, maintain and follow, and would allow us to support more than two stable releases at a time. In a simpler way. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 8956] New: Split serials enumeration data into separate fields
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '14

05 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8956 Priority: P5 - low Change sponsored?: --- Bug ID: 8956 CC: colin.campbell(a)ptfs-europe.com Assignee: koha-bugs(a)lists.koha-community.org Summary: Split serials enumeration data into separate fields Severity: enhancement Classification: Unclassified OS: All Reporter: kyle(a)bywatersolutions.com Hardware: All Status: NEW Version: master Component: Serials Product: Koha Work to be done 1) Add an option 'published_end_date' to the serials table. It will only be used to represent the last issue date in a bound volume. 2) Data clean up: Extract the published dates from the existing enumeration field. Populate serials.publisheddate and serials.published_end_date with this data. 3) Strip the publishing dates from their enumeration fields (probably by simply deleting matched parentheses and everything in between them). 4) In order to break the “Numbered” field into three columns, add X, Y and Z columns to serials, as well as X, Y and Z descriptions columns to the subscription table. 5) Port existing data into these columns. Once all the enumeration fields are of the correct format, e.g., Vol. X No. Y, we can use everything preceding {X} as X_Description, and everything preceding {Y} until } as Y_Description. Another way to look at this is if we split on {?}, we will have all the label fields in order of use. Once we have the label fields, we can parse those out of the enumeration string, and we will have the set of values they represent. 6) Add a calendar widget for published on and expected on (serials-edit.pl). This will require librarians to enter new dates in the accepted format. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 67

[Bug 9851] New: way to get full records for purchase suggestions
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '14

05 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9851 Bug ID: 9851 Summary: way to get full records for purchase suggestions Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com It would be nice if there were a way to get full records for purchase suggestions - a replace via Z39.50 option maybe. Right now most libraries order from a batch given to them from a vendor or from a Z target to get full records, but if they do this then their orders aren't linked to the suggestions. The only way to keep the suggestion linked is to order from it and in essence a brief record. I don't have a good suggestion here, but thought I should share the idea in case someone else has a solution. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1