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

[Bug 10241] New: Easy analyticals creates two 773 fields. Search/link from host to children is broken
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10241 Bug ID: 10241 Summary: Easy analyticals creates two 773 fields. Search/link from host to children is broken Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: normal Priority: P4 Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: eb(a)efdss.org UseControlNumber preference is set to "Don't use" and the EasyAnalyticalRecords preference is set to 'Display.' I created a record, and then selected New child record and created an analytic. Then, following the instructions in the manual Chapter 5 http://es.koha-community.org/manual/3.10/en/cataloging.html#cataloganalytics I linked the analytic to the host item. This resulted in two 773 fields. The first (created when adding a new child record contains: w Host Record control number 005037189 d Place, publisher, and date of publication Milwaukee : Hal Leonard, [2002?] z International Standard Book Number 0634038788 t Title Selections from O brother, where art thou? : The second 773, created when I linked the child to the parent contains the above, plus 0 Host Biblionumber 19017 9 Host Itemnumber 20551 The search for analytics is driven by the host item number, which is not included in the 773 that is created with a new child record. So you must link the child to the parent. But why create an additional 773? It looks messy. Second part possibly not related at all to the above: When I go to the host item in the staff interface and click on Analytics it says Used in 4 analytics ('4 analytics' is a link: http://kohaadmin-test.efdss.org/cgi-bin/koha/catalogue/search.pl?idx=hi&q=2… If I click on the link: No results found. No results match your search for 'hi,wrdl: 20551' in VWML Test Catalog. But if I put the host item number 20551 into the search field, it returns the children and the parent record. Something about the search from analytics is not functioning correctly. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 12210] New: Baker & Taylor book jackets not disabled when BakerTaylorBookstoreURL is not populated
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12210 Bug ID: 12210 Summary: Baker & Taylor book jackets not disabled when BakerTaylorBookstoreURL is not populated Change sponsored?: --- Product: Koha Version: 3.14 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: bartonski(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The description of the BakerTaylorBookstoreURL syspref says "Baker and Taylor "My Library Bookstore" links should be accessed at https:// isbn (this should be filled in with something like ocls.mylibrarybookstore.com/MLB/actions/searchHandler.do?nextPage=bookDetai…) Leave it blank to disable these links." Leaving this syspref blank does not disable the links. Instead, they are populated without the bookstore URL: the cover image for ISBN 1575725738 will cause koha to make a request to http://1575725738, which will, of course, time out. Leaving BakerTaylorBookstoreURL blank should disable any URL that depends on this syspref, as stated in the syspref description. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 12028] New: add cardnumber on update patron records page
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12028 Bug ID: 12028 Summary: add cardnumber on update patron records page Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 26768 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=26768&action=edit patron update Hi, It would be fine to have patron cardnumber on member-update.pl. This will avoid confusion of homonymous. Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 7497] New: "kw, wrdl" and variants should be replaced by something more explicit in search history
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '16

18 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7497 Bug #: 7497 Summary: "kw,wrdl" and variants should be replaced by something more explicit in search history Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: gaetan.boisson(a)biblibre.com QAContact: koha.sekjal(a)gmail.com A patron search history typically reads like this : Date Search Results 03/02/2012 15:49:18 au,wrdl: test2 0 03/02/2012 15:49:04 se,wrdl: test 0 03/02/2012 15:48:51 nb: test 0 03/02/2012 15:47:09 kw,wrdl: tsfdfs 0 03/02/2012 15:47:01 kw,wrdl: tsfdfs 0 A more explicit list would be a nice improvement : au,wrdl : author se,wrdl : series nb : isbn kw,wrdl : (all) ti,wrdl : title su,wrdl : subject callnum,wrdl : callnumber Am i missing any ? -- 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 13

[Bug 10891] New: Make facets customisable
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '16

18 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10891 Bug ID: 10891 Summary: Make facets customisable Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: mathieu.saby(a)univ-rennes2.fr QA Contact: testopia(a)bugs.koha-community.org Currently, facets are hard coded in Search.pm and Koha.pm. This bug will provide a way for each library to customize facets. Here is my plan : 1. move facets configuration into a YAML block of data, still stored in Koha.pm. No functional changes at that step 2. store configuration in a YAML file and create a page for allowing librarians to change - the fields used for each Koha standard facets - the sorting order of results inside each facet (ie. alphabetic a-z or z-a, nbr of occurencies 1-100 100-1) - the displaying orders of facets blocks (ie. Authors before Libraires etc) - the visibility of each facets (ie. ability to hide "Title" or "Author" facet) 3. define new standard Koha facets (that could be masked by users if they don't like them) - precise subjects and author facets (geographical subjects, etc.) - date of publication - language 4. allow librarians to define custom facets 5. allow facets on coded fieds (0XX in MARC21 and 0XX / 1XX in Unimarc) 6. allow opac facets to be different from staff interface facets That's all folks! For the moment, I have only written the 1st patch ;-) Maybe the best would be to make several bugs an attach them to this one? -- You are receiving this mail because: You are watching all bug changes.

1 45

[Bug 10213] New: UniqueItemFields should be implemented for creating items in cataloguing and serials
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '16

18 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10213 Bug ID: 10213 Summary: UniqueItemFields should be implemented for creating items in cataloguing and serials Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de CC: m.de.rooy(a)rijksmuseum.nl The system preference UniqueItemFields helps to guarantee that some fields in the item table are filled with unique values on ordering and receiving items. It would be consistent to have the same functionality also available when adding items in cataloguing and in serials. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 11557] New: Collector bug for Academy bootstrap3 upgrading work
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '16

18 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11557 Bug ID: 11557 Summary: Collector bug for Academy bootstrap3 upgrading work Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org This bug is a collector for the work done by Catalyst Academy on upgrading the OPAC to bootstrap 3. These patches are probably incomplete, but possibly a starting point for the work to be done upgrading the OPAC to bootstrap3. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 10881] New: Fast Add Framework has different item fields
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '16

18 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10881 Bug ID: 10881 Summary: Fast Add Framework has different item fields Change sponsored?: --- Product: Koha Version: 3.12 Hardware: PC OS: Windows Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: akilsdonk(a)esilibrary.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When using the Fast Add MARC Framework, the Add Item form is different from the Add Item form that appears with other Frameworks. Additional fields are visible in the Fast Add item form. I also noticed that Nonpublic notes added in the Fast Add item form do not show up in the Notes during check in. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 7143] New: Bug for tracking changes to the about page
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '16

18 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7143 Bug #: 7143 Summary: Bug for tracking changes to the about page Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All URL: /cgi-bin/koha/about.pl OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: About AssignedTo: nengard(a)gmail.com ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org Bug for tracking changes to the about page (new release teams, new developers, companies, 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 513

[Bug 6322] New: It's possible to view lists/virtualshelves even when virtualshelves is off
by bugzilla-daemon＠bugs.koha-community.org 15 Jan '16

15 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6322 Bug #: 6322 Summary: It's possible to view lists/virtualshelves even when virtualshelves is off Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Virtual Shelves AssignedTo: gmcharlt(a)gmail.com ReportedBy: magnus(a)enger.priv.no QAContact: koha-bugs(a)lists.koha-community.org In current head, setting the virtualshelves syspref to off removes the Lists "button" from the OPAC, but if you visit the URL of a list, you can still view it's contents. I would have expected to get a message like "this feature is currently turned off" or similar. -- 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 23