January 2018 - Koha-bugs - lists.koha-community.org

[Bug 18225] New: Return date to be same as issue date after holiday closed period
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '23

10 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18225 Bug ID: 18225 Summary: Return date to be same as issue date after holiday closed period Change sponsored?: --- Product: Koha Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Holidays Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.stone(a)wiltshire.ac.uk QA Contact: testopia(a)bugs.koha-community.org Request for return date to be same as issue date after holiday closed period. Currently having to manually change each Hard Due Date via Circulation and Fine Rules for every variation of Patron Category and item type with 21 day loans and 7 day loans before holiday closed period. Then return to "none defined" manually. Due to having students that do not attend every day of the week, we need return dates to be on the same day of the week as the day they are issued. This works until we have a closed period when the return date automatically goes to the first day that we are open. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 18216] New: Apache2.4 403 errors for Gitified or git clone installs
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '23

10 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18216 Bug ID: 18216 Summary: Apache2.4 403 errors for Gitified or git clone installs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Fixes this install step for dev installs: https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#403_errors_f… --SNIP-- 403 errors for Gitified or git clone installs In Ubuntu 14.04 you may discover that your gitified install returns 403 errors - this is because of the changes to Apache directory security. A possible fix includes adding the following stanza to apache2.conf (could be added in the virtualhost, or in one of the koha-shared*.conf files as well): <Directory /home/my-user/koha-src/koha/> Options Indexes FollowSymLinks AllowOverride None Require all granted </Directory> --SNAP-- -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 18202] New: Define profiles for Z39.50 server targets
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '23

10 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18202 Bug ID: 18202 Summary: Define profiles for Z39.50 server targets Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Different Z39.50 servers support different use attributes using different profiles. NorZIG: http://www.norzig.no/profiles/profile2.1.html Libraries Australia (LA): http://www.nla.gov.au/librariesaustralia/services/search/z3950/ Library of Congress (LOC): https://www.loc.gov/z3950/lcserver.html More profiles: https://www.loc.gov/z3950/agency/profiles/profiles.html In the case of Libraries Australia and Library of Congress, the profiles are different between bibliographic databases and authority databases, and this can be traced back to differences in the functional areas of the Bath profile: http://web.archive.org/web/20080218122658/http://www.collectionscanada.gc.c… For instance, Libraries Australia claims to support "Functional Area D (Authority Record Search & Retrieval) to Level 1" http://web.archive.org/web/20080219085710/http://www.collectionscanada.gc.c… It doesn't appear to in reality as it doesn't support use attribute 1002 (while the Library of Congress does support this use attribute). The Library of Congress appears to be more in line with Functional Area D (Authority Record Search & Retrieval) to Level 2: http://web.archive.org/web/20080219085716/http://www.collectionscanada.gc.c… It doesn't look like LOC perfectly adheres to Level 2, but I'd say it does up to 99.99%. It also supports a extra attributes belonging to local indexes. Anyway, here's the problem: LOC use attributes 1,2, and 3, but LA does not support these attributes. On the other hand, LA supports 1003, 1004, 1005, and 1006, but LOC does not. LOC supports 1002, but LA does not. We need to be able to define profiles on a server by server basis. In fact, this is even recommended by Libraries Australia: "Step 4. Configure your Bib-1 Search Attributes (if required):". -- I don't think it would be that difficult to define profiles. We'd have a table with id, profile name, a name/index/description column, and a use attribute column. Then we could add a foreign key to z3950servers to specify the profile. We'd need to do a different query for each server target but that would be easy enough on its own. The difficulty may lie in what to do about the Z39.50 search form. Not all "names" would be supported by all targets. Bug 18096 (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18096) also mentions some local attributes. We don't have a way of specifying those in the search form at the moment, and obviously those local attributes would be local to that particular server. I suppose we could dynamically create the search form... but again not all names will correspond to all servers. I suppose we could just add that caveat. We could also be better with our presentation of results. If we get an error code of unsupported use attribute from a target server, we could surface that to users. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 18197] New: Make borrowers-force-messaging-defaults a bit more standard
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '23

10 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18197 Bug ID: 18197 Summary: Make borrowers-force-messaging-defaults a bit more standard Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Possible tasks to do: - Make it .pl - give it better help documentation - make sure it's presence is noted in the manual - make it so that optionally, if a borrower has preferences set that don't match the default, that borrower is skipped for re-setting (as they have likely set their preferences). For another time, but just noting it: put a function that does this into the web interface for superlibrarians. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 18196] New: Holds Queue table should link to Holds table by reserve_id
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '23

10 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18196 Bug ID: 18196 Summary: Holds Queue table should link to Holds table by reserve_id Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Now that the 'reserves' table has an id column, it would be nice to link the tmp_holdsqueue table to it using reserves_id as a foreign key. Furthermore, we could require the tmp+holdsqueue column to be unique, as we can only have a single line in tmp_holdsqueue for any given rserve_id. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 18192] New: Add form for fast changes to tab/ visibility in marc frameworks
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '23

10 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18192 Bug ID: 18192 Summary: Add form for fast changes to tab/visibility in marc frameworks Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be nice to have a form where we can quickly change tab/visibility (especially the last one) for a larger number of fields and subfields in a particular framework. Often you want to hide a (sub)field and set tab to -1. Or unhide a (sub)field by restoring tab and setting hidden to 0 (or possibly another value). In order to select fields we could use constructions like: 100|110a|200|300abc etc. Or regexp based: /^1|^20|300[ab]|500a/ etc. And all fields selected, perform a hide or unhide operation. Do you have suggestions about its interface? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 18153] New: UNIMARC bib records exported with invalid 'a' char in label pos.9
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '23

10 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18153 Bug ID: 18153 Summary: UNIMARC bib records exported with invalid 'a' char in label pos.9 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: stephane.delaune(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The standard UNIMARC requires than the 9th character (starting from 0) in labels must be blank (while it may be 'a' in marc21), but under certain conditions (e.g. when a iso2709 file is imported) Koha's unimarc records can have an invalid char. 'a' in label pos.9 So when we want to export them with export's tool, if marcflavour syspref is UNIMARC, we need to delete this bad 'a' char from label pos.9 (to have blank) -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 18141] New: Edifact messages won't allow deletion of baskets
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '23

10 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18141 Bug ID: 18141 Summary: Edifact messages won't allow deletion of baskets Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: jacqueline(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If you have messages from a vendor in Edifact then you are not able to delete baskets from that vendor until the messages are deleted on the back end. This is even if the basket has not been closed and just cancelled. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 18113] New: Add ability to arbitrarily add charges to acquisitions
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '23

10 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18113 Bug ID: 18113 Summary: Add ability to arbitrarily add charges to acquisitions Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be great to add the ability to arbitrarily add charges to acquisitions. If we could edit a fund without adding an order to a basket, for example, MARC Record charges that are a flat fee from a vendor. This would provide some flexibility when working with fund for miscellaneous charges in the budget that are not attached to an order. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 18105] New: Should we restart koha-indexer differently i.e. like koha-plack?
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '23

10 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18105 Bug ID: 18105 Summary: Should we restart koha-indexer differently i.e. like koha-plack? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net Koha-indexer uses a daemon --restart: A daemon restart does not really stop and start; the client processes are terminated, but the named daemon itself is not. Changed options are not taken into account. Same for koha-restart-zebra btw. Koha-plack implements its restart by doing a daemon --stop and daemon --start. This makes that changed options are taken into account. If you know how this work, no problem. But it is not consistent. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6