July 2011 - Koha-bugs - lists.koha-community.org

[Bug 6517] New: koha-create wants "use database" in DEFAULTSQL
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '11

26 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6517 Bug #: 6517 Summary: koha-create wants "use database" in DEFAULTSQL Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Packaging AssignedTo: robin(a)catalyst.net.nz ReportedBy: magnus(a)enger.priv.no QAContact: koha-bugs(a)lists.koha-community.org If koha-create is given the path to a DEFAULTSQL in /etc/koha/koha-sites.conf, it looks like it expects to find a statement similar to this at the top of that file: use koha___KOHASITE__; This piece of the code will then replace __KOHASITE__ with the name of the site being created: # Populate the database with default content. zcat "$DEFAULTSQL" | sed "s/__KOHASITE__/$name/g" | mysql --host="$mysqlhost" --user="$mysqluser" --password="$mysqlpwd" As far as I can see this means one has to remember to add the use koha___KOHASITE__; to the file whenever a new DEFAULTSQL is created. Wouldn't it be easier and less error prone to make mysql use the right database by including the name of the database in the call to mysql? Something like this: # Populate the database with default content. zcat "$DEFAULTSQL" | mysql --host="$mysqlhost" --user="$mysqluser" --password="$mysqlpwd" $mysqldb -- 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 13

[Bug 6516] New: koha-create makes assumptions about borrowernumber of staff user
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '11

26 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6516 Bug #: 6516 Summary: koha-create makes assumptions about borrowernumber of staff user Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Packaging AssignedTo: robin(a)catalyst.net.nz ReportedBy: magnus(a)enger.priv.no QAContact: koha-bugs(a)lists.koha-community.org In debian/scripts/koha-create a random password is set for a staff user, but this staff user is hardcoded to have borrowernumber = 3: mysql --host="$mysqlhost" --user="$mysqluser" \ --password="$mysqlpwd" <<eof USE \`$mysqldb\`; UPDATE borrowers SET password = '$staffdigest' WHERE borrowernumber = 3; eof For me it would make sense to have one pre-defined staff user in the DEFAULTSQL file, with borrowernumber = 1. Maybe the borrowernumber of the staff user could be set in /etc/koha/koha-sites.conf? -- 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 9

[Bug 6256] New: Many bib1 attributes missing
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '11

26 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6256 Bug #: 6256 Summary: Many bib1 attributes missing Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: MARC Bibliographic data support AssignedTo: jcamins(a)cpbibliography.com ReportedBy: jcamins(a)cpbibliography.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com The Zebra configuration for Koha is missing many bib1 attributes. Even if they are not all used, they should all be listed in the bib1.att configuration file. The following attributes are missing: SICI 1037 Abstract-language 1038 Application-kind 1039 Classification 1040 Classification-basic 1041 Classification-local-record 1042 Enzyme 1043 Possessing-institution 1044 Record-status 1046 Treatment 1047 Control-number-GKD 1048 Control-number-linking 1049 Control-number-PND 1050 Control-number-SWD 1051 Control-number-ZDB 1052 Country-publication (country of Publication) 1053 Date-conference (meeting date) 1054 Date-record-status 1055 Dissertation-information 1056 Meeting-organizer 1057 Note-availability 1058 Number-CAS-registry (CAS registry number) 1059 Number-document (document number) 1060 Number-local-accounting 1061 Number-local-acquisition 1062 Number-local-call-copy-specific 1063 Number-of-reference (reference count) 1064 Number-norm 1065 Number-volume 1066 Place-conference (meeting location) 1067 Reference (references and footnotes) 1068 Referenced-journal (reference work) 1069 Section-code 1070 Section-heading 1071 Subject-GOO 1072 Subject-name-conference 1073 Subject-name-corporate 1074 Subject-genre/form (Formerly "Subject-name-form" renamed August 2003) 1075 Subject-name-geographical 1076 Subject--chronological (formerly "Subject-name-chronological" renamed August 2003) 1077 Subject--title (formerly "Subject-name-title" renamed August 2003) 1078 Subject--topical (formerly "Subject-name-topical" renamed August 2003) 1079 Subject-uncontrolled 1080 Terminology-chemical (chemical name) 1081 Title-translated 1082 Year-of-beginning 1083 Year-of-ending 1084 Subject-AGROVOC 1085 Subject-COMPASS 1086 Subject-EPT 1087 Subject-NAL 1088 Classification-BCM 1089 Classification-DB 1090 Identifier-ISRC 1091 Identifier-ISMN 1092 Identifier-ISRN 1093 Identifier-DOI 1094 Code-language-original 1095 Title-later 1096 Performer 1185 Performer-Individual 1186 Performer-Group 1187 Instrumentation 1188 Instrumentation-Original 1189 Instrumentation-Current 1190 Arrangement 1191 Arrangement-Original 1192 Arrangement-Current 1193 Musical Key-Original 1194 Musical Key-Current 1195 Date-Composition 1196 Date-Recording 1197 Place-Recording 1198 Country-Recording 1199 Number-ISWC 1200 Number-Matrix 1201 Number-Plate 1202 Classification-McColvin 1203 Duration 1204 Number-Copies 1205 Musical Theme 1206 Instruments - total number 1207 Instruments - distinct number 1208 Identifier - URN 1209 Sears Subject Heading 1210 OCLC Number 1211 Composition 1212 Intellectual level 1213 EAN 1214 NLC 1215 CRCS 1216 Nationality 1217 Equinox 1218 Compression 1219 Format 1220 Subject - occupation 1221 Subject - function 1222 Edition 1223 GPO Item Number 1224 This list does not include Dublin Core or GILS attributes. -- 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 12

[Bug 6555] New: only 10 lists in pull down when adding from a bib record
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '11

26 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6555 Bug #: 6555 Summary: only 10 lists in pull down when adding from a bib record Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All URL: cgi-bin/koha/virtualshelves/addbybiblionumber.pl?bibli onumber=3 OS/Version: All Status: NEW Severity: major Priority: P5 Component: Virtual Shelves AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Created attachment 4559 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=4559 10 lists instead of 12 (or all) I have attached a screenshot of the problem. We currently have 12 public lists (and I have 1 private list) but when I try to add to a list from within a bib record in the staff client, I only get a list of 10...and of course the one I need (Educations & Licensure) is not on it. -- 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 13

[Bug 6528] New: Cataloging search issues - Holdings not displayed in location column
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '11

26 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6528 Bug #: 6528 Summary: Cataloging search issues - Holdings not displayed in location column Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: wizzyrea(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com It looks like the template should show the count of holdings per branch in the location column, but the data doesn't appear. To test: More -> cataloging (addbooks.pl) Do a search You will not see any holdings, except checked out/lost items. I believe it should (and was intended to) show the holdings per branch, similar to how the other search (search.pl) shows holdings. -- 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 10

[Bug 6275] New: Automated backups of data and config
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '11

26 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6275 Bug #: 6275 Summary: Automated backups of data and config Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Packaging AssignedTo: robin(a)catalyst.net.nz ReportedBy: robin(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Currently there is no built-in way of doing backups. This will add a cron job that will perform daily backups to a set location on the file system (whereupon it can be archived off-machine, or whatever.) -- 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 6368] New: unimarc_field_4XX plugin does not work with new templates
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '11

26 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6368 Bug #: 6368 Summary: unimarc_field_4XX plugin does not work with new templates Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: januszop(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org unimarc_field_4XX does not work now in 3.4+, after introducing the new templates system. This particular error is due to prefixing $index in loops with accidental names. A patch will follow. -- 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 10

[Bug 6562] New: Reserve request generates unnecessary runtime errors
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '11

26 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6562 Bug #: 6562 Summary: Reserve request generates unnecessary runtime errors Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: colin.campbell(a)ptfs-europe.com QAContact: koha-bugs(a)lists.koha-community.org Because the script action is directed by 'action' but is initially called with action undefined it fills the log with noise. Assign a suitable falsy value to action if undefined so that we can use the error logs more efficiently. script is a prime candidate for refactoring if anyone has the time as its over complex and slow -- 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 7

[Bug 6318] New: fields missing when editing a layout
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '11

26 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6318 Bug #: 6318 Summary: fields missing when editing a layout Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Label printing AssignedTo: cnighswonger(a)foundations.edu ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org When you create a layout you have 7 (i think) fields you can choose from under the 'Choose Order Of Text Fields to Print' heading. If you set any of them to 'blank' (aka not to show) then when you come back to edit the label those fields aren't there as a choice anymore. For those of us who know the database and the marc fields it's not a big deal, we can use the box under the 'List fields' heading, but for most librarians it's confusing to have those fields disappear. I think that they should be there at all times that way librarians can just choose a number from the pull down to make them reappear. Another option is to have a menu like on notices where all the fields are listed and you choose which ones you want to add to your label. -- 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 6479] New: Encoding problem in "recievedlist" when the numbering formula contains utf-8 characters
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '11

26 Oct '11

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6479 Bug #: 6479 Summary: Encoding problem in "recievedlist" when the numbering formula contains utf-8 characters Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Serials AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: fcapovilla(a)live.ca QAContact: koha-bugs(a)lists.koha-community.org Created attachment 4424 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=4424 Corrections the encoding problem with "recievedlist" If a numbering formula using utf-8 characters is used with a subscription("N° {X}" for example), the "Received issues" list gets encoded incorrectly when the number of received issues is greater than 1. The problem is a double-encoding problem that happens when adding a new issue's number to the content of the recievedlist field, because a utf-8 string gets concatenated with a non-utf8 string. Patch attached that converts the issue number to utf-8 before the concatenation happens. -- 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 14