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

[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 12370] New: tell user how many records will be imported on staged tool
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '14

05 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12370 Bug ID: 12370 Summary: tell user how many records will be imported on staged tool Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org On the staged marc record tool it can be confusing when you have a large batch in which you told Koha to ignore certain items which items will be imported. A tip somewhere on the page before you finally click 'import' would be nice. For example you say you want it to ignore matches a note saying that only the non matching records (with a count) will be imported would be comforting. -- You are receiving this mail because: You are watching all bug changes.

1 0

[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

[Bug 12349] New: patron name on suggestions should be linked
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '14

05 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12349 Bug ID: 12349 Summary: patron name on suggestions should be linked Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/suggestion/suggestion.pl?#ASKED OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It would be great if patron names on suggestions were linked to their patron record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 6070] New: On a new order defined from suggestion some fields were missing.
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '14

05 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6070 Bug #: 6070 Summary: On a new order defined from suggestion some fields were missing. Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org (MT #4937) The missing fields : publicationyear, place, collectiontitle. More the layout has been modified. -- 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 54

[Bug 3144] anti-spam for opac-suggestions
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '14

05 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3144 --- Comment #19 from Chris Cormack <chris(a)bigballofwax.co.nz> --- (In reply to Christopher Brannon from comment #18) > Do you think it should be communicated to the user that the submission > failed? I know it is highly unlikely, but in the off chance that it is a > human, and something goes wrong, should something be in place? > Perhaps, however id be worried that telling them it failed might make the bot try again and again. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 3144] anti-spam for opac-suggestions
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '14

05 Jun '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3144 --- Comment #18 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- Do you think it should be communicated to the user that the submission failed? I know it is highly unlikely, but in the off chance that it is a human, and something goes wrong, should something be in place? Christopher -- You are receiving this mail because: You are watching all bug changes.

1 0