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

[Bug 4864] New: modules required by SIP not in module list
by bugzilla-daemon＠bugs.koha-community.org 03 May '15

03 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4864 Summary: modules required by SIP not in module list Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Installation and upgrade (command-line installer) AssignedTo: gmcharlt(a)gmail.com ReportedBy: colin.campbell(a)ptfs-europe.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 SIPServer.pm requires Net::Server and UNIVERSAL::require which are not in the dependencies listing -- 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 5294] New: Vendor name shows with '%20'
by bugzilla-daemon＠bugs.koha-community.org 03 May '15

03 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5294 Summary: Vendor name shows with '%20' Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: robin(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 To reproduce: 1) create a new subscription 2) search for a vendor who has spaces in their name 3) choose it, and note that when its name is put into the field, it has %20 where spaces should be. -- 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 17

[Bug 5704] New: bib level item type icon should display on search results
by bugzilla-daemon＠bugs.koha-community.org 01 May '15

01 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5704 Summary: bib level item type icon should display on search results Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Depends on: 4359 Estimated Hours: 0.0 Created attachment 3079 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=3079 display introduced with patch for bug 4359 I talked to Owen today (chat transcript below) about the recent changes applied by the commit for bug 4359. Basically the icon shouldn't show on the search results unless the item-level_itypes pref is off. But I think we need a new pref that does not take the item-level_itypes pref into consideration to show the bib level item type icon on the search results (if the library so chooses). --------------- Owen Leonard: But if you have item-level item types turned on (and I think most people do now?) then there is no way to choose which item type to display on the results page Owen Leonard: And mightn't libraries not be setting a biblio-level item type at all? Nicole Engard: so maybe we need two prefs Nicole Engard: you are right - they may not be setting that bib level item type Owen Leonard: Hm... They don't have some copies in reference and others which circulate? Owen Leonard: That's the big use we have of the feature Nicole Engard: i would think they would Nicole Engard: basically whatever commit this was needs to be reverted cause it has too many variables that weren't considered Nicole Engard: i just can't find the report for it Nicole Engard: i think we need multiple prefs: Owen Leonard: http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=7a945dbc284… Nicole Engard: #1 show icons on the search results (yes/no) Nicole Engard: #2 use the bib level/first item level icon for display Nicole Engard: #3 show icons on the items on the bib detail Owen Leonard: I'm going to submit another patch to make display of the item type icon contingent on having item-level_itypes off Nicole Engard: i'll add my notes after you do that - cause that's too broad a condition - if you turn them off for all items and want the icon to display on the search results if you don't have attached items you can't have that Nicole Engard: i don't know if that makes sense Owen Leonard: I think at this point there is no logical way to display icons on the search results page if you have item-level itemtypes turned on. Nicole Engard: hence my suggestions for multiple prefs Owen Leonard: Displaying the first item-level item type doesn't make sense to me, I think that would be misinformation. Nicole Engard: i agree with you!! don't get my wrong - i'm just telling you what we're being asked for Nicole Engard: i'm okay with your way - but we need a pref to use the bib level item type for search results icon display if people want Nicole Engard: and that has to be regardless of the value in the item level pref Nicole Engard: who are we to tell libraries they can't share misinformation? :) hehe Owen Leonard: Fair enough. Owen Leonard: So we need a new bug report for that enhancement Nicole Engard: i'll do that and i'll relate it to the one you're fixing -- 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 4

[Bug 6007] New: Checking 'Display only used Tags/Subfields' on MARC framework page results in unusable output
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '15

29 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6007 Bug #: 6007 Summary: Checking 'Display only used Tags/Subfields' on MARC framework page results in unusable output Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All URL: /cgi-bin/koha/admin/marctagstructure.pl OS/Version: All Status: NEW Severity: normal Priority: P5 Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 3531 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=3531 Screenshot of the problematic display When looking at tags for a particular MARC framework, if you check the 'Display only used Tags/Subfields' the page automatically reloads and the table redisplays in a way that is unusable. The table columns no longer match the header and there are no longer links for editing, deleting, etc. -- 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 17

[Bug 5511] New: Check for Change in Remote IP address for Session Security. Disable when remote ip address changes frequently.
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '15

22 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5511 Summary: Check for Change in Remote IP address for Session Security. Disable when remote ip address changes frequently. Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: amit.gupta(a)osslabs.biz QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 Check for Change in Remote IP address for Session Security. Disable when remote ip address changes frequently. -- 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 59

[Bug 5627] New: lock symbol even on not locked fields
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '15

14 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5627 Summary: lock symbol even on not locked fields Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: Mac OS Status: NEW Severity: normal Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 When cataloging the authority controlled fields always show the lock symbol even if the field can be typed in - this is confusing to users and should only show locked if you can't type in the field. If it matters I'm on Mac and FF. -- 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 5

[Bug 5185] New: Match modification should (optionally) update the last seen time
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '15

14 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5185 Summary: Match modification should (optionally) update the last seen time Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: robin(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 When using the batch modification tool, there should be the option of updating the last-seen time. -- 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 5069] New: Authority clean-up scripts
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '15

14 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5069 Summary: Authority clean-up scripts Change sponsored?: --- Product: Koha Version: rel_3_0 Platform: PC OS/Version: Linux Status: NEW Severity: enhancement Priority: P5 Component: Command-line Utilities AssignedTo: chris(a)bigballofwax.co.nz ReportedBy: ccurry(a)amphilsoc.org QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 When we originally migrated our data, we loaded ~ 40,000 auth records corresponding to ~ 200,000 bib records. I ran the link_bibs_to_authorities.pl script, but it appears that we have some bad data in our authorities (or our bibs?), because some did not link correctly. I wonder if there's a way to utilize the process that creates authority records from the appropriate fields during the record creation process to generate authority records from unlinked headings of existing bibs. In addition, we'd like to be able to delete the authorities we imported that have no bibs linked. I asked this question yesterday on IRC#koha and Chris Cormack mentioned that a script could be written for both of these and it "might be a good koha code learning exercise for someone at catalyst." He asked me to submit this enhancement and assign it to him. One thing I should add is this: If there is not already a duplicate auth record checking functionality built into the process which auto-generates authorities during the record creation process, it seems that this would be important for a command line script, since we wouldn't want to create a bunch of identical authorities (which would then not function correctly as authority records). Perhaps the link_bibs_to_authorities.pl script contains the necessary dup finding code? We're running 3.00.05.001 (on Debian Lenny), so it would be useful for us if the scripts were compatible with 3.0 & 3.2. If necessary, we'd be willing to upgrade to 3.00.06 (we're hoping to do so soon, anyway, unless 3.2 becomes stable before we get around to 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 2

[Bug 5377] New: Database fields too small for multiple ISBN and ISSN
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '15

13 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5377 Summary: Database fields too small for multiple ISBN and ISSN Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Database AssignedTo: gmcharlt(a)gmail.com ReportedBy: fridolyn.somers(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Hie, I noticed a wrong behavior in "koha to MARC mapping". Using a mapping for ISBN and ISSN fields, I noticed that fields "isbn" and "issn" where truncated in "biblioitems" table when using multiple values. With multiple values, ISBN and ISSN are separated by a " | ". In fact, "isbn" field is a VARCHAR(30) and "issn" field is a VARCHAR(9). This is far to small. I propose a VARCHAR(255). Regards, -- 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 38

[Bug 5458] New: length of items.ccode disagrees with authorised_values.authorised_value
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '15

09 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5458 Summary: length of items.ccode disagrees with authorised_values.authorised_value Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Database AssignedTo: gmcharlt(a)gmail.com ReportedBy: pete.huerter(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Koha allows you to define an authorised value having length 80, but then you can't use it. Here is why: The SQL field items.ccode is a varchar(10). The SQL field authorised_values.authorised_value is a varchar(80). Therefore the authorised value is truncated to length 10 in items.ccode and the mapping from authorised value to description string fails in Koha. Not sure how this change will "bubble up" in Koha but the change to the table schema seems straightforward: increase the size of items.ccode to varchar(80). This is preferable to shortening authorised_values.authorised_value since we have many category codes (CCODE) that are longer than length 10. -- 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 3