April 2017 - Koha-bugs - lists.koha-community.org

[Bug 16275] New: Prevent patron creation if the email already filled in borrowers.email
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '25

31 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16275 Bug ID: 16275 Summary: Prevent patron creation if the email already filled in borrowers.email Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nicolas.legrand(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some of our patrons are not sure they succeed their self registration and self register multiple times. We would like to prevent this by blocking the selfregistration if the field borrowers.email is already filled by the same email address. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 17507] New: Preference to limit how old an offline circ file can be when uploaded
by bugzilla-daemon＠bugs.koha-community.org 26 Mar '25

26 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17507 Bug ID: 17507 Summary: Preference to limit how old an offline circ file can be when uploaded Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We recently ran into an issue where old transactions were uploaded from offline circ. This caused a BIG MESSS. Mistakes will happen. It would be great if there was a setting in Koha to limit the number of days old a file can be when uploaded. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 16105] New: Cache::Memory is loaded even if memcache is used
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '25

18 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16105 Bug ID: 16105 Summary: Cache::Memory is loaded even if memcache is used Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 11998, 16104 Cache::Memory is loaded and Koha::Cache::_initialize_memory is called even if a memcached cache has been correctly initialize, it does not make sense. It should only be initialize if needed. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11998 [Bug 11998] Syspref caching issues https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16104 [Bug 16104] Warnings "used only once: possible typo" should be removed -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 16104] New: Warnings "used only once: possible typo" should be removed
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '25

18 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16104 Bug ID: 16104 Summary: Warnings "used only once: possible typo" should be removed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Since bug 11998, the following warnings are raised: Name "Tie::Hash::FIELDS" used only once: possible typo at /usr/share/perl/5.22/fields.pm line 135. Name "Cache::RemovalStrategy::LRU::FIELDS" used only once: possible typo at /usr/share/perl/5.22/fields.pm line 135. Name "Cache::RemovalStrategy::FIELDS" used only once: possible typo at /usr/share/perl/5.22/fields.pm line 135. It comes from the Koha::Cache 103 if ( can_load( modules => { 'Cache::Memory' => undef } ) ) { -- You are receiving this mail because: You are watching all bug changes.

1 38

[Bug 16196] New: Acquisitions Module Not Showing Subtotals
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '25

17 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16196 Bug ID: 16196 Summary: Acquisitions Module Not Showing Subtotals Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: amy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Partner reports that when receiving books in the Acquisitions module, subtotals are not identifying which fund they are for. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 17173] New: Quick edit a subfield in frameworks
by bugzilla-daemon＠bugs.koha-community.org 11 Mar '25

11 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17173 Bug ID: 17173 Summary: Quick edit a subfield in frameworks Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: System Administration Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There are too many click to jump to the edit form of a specific subfield. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 17898] New: Add a way to automatically convert SQL reports
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '25

10 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17898 Bug ID: 17898 Summary: Add a way to automatically convert SQL reports Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Bug 17196 move the marcxml out of the biblioitems table. That will break SQL reports using it. It would be handy to propose an automagically way to convert the SQL reports. -- You are receiving this mail because: You are watching all bug changes.

1 37

[Bug 17791] New: On UNIMARC system, USMARC field 100 gets overwritten
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '25

09 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17791 Bug ID: 17791 Summary: On UNIMARC system, USMARC field 100 gets overwritten Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: gmcharlt(a)gmail.com Reporter: synapse.ova(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Overview: On Z39.50 search some functions depend not on the remote server marc flavour, but on current server setting. This bug is present on versions 3.22+ Steps to Reproduce: 1) On UNIMARC system, go to Cataloguing → New from Z39.50/SRU 2) Search USMARC server (Library of Congress, for example) for a book, that has field 100 (for example, isbn 0816310653) 3) On results list, press «MARC» to see MARC fields Actual Results: Instead of seeing the author name in subfield A, you'll see something like «20161219 frey50 », yet you could see other subfields properly Expected Results: Name of the author in 100$a Additional Information: LC Z39.50/SRW/SRU Server Configuration Guidelines: https://www.loc.gov/z3950/lcserver.html -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 16629] New: Fields available for printing are inconsistent between label layouts and SpineLablFormat system preference
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16629 Bug ID: 16629 Summary: Fields available for printing are inconsistent between label layouts and SpineLablFormat system preference Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In label layouts all marc fields are available, however, when setting quick spine fields in the system preferences you can only use columns from the db tables. It would be nice to have access to record fields here as well -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 18273] New: Bulkmarcimport inserts authority duplicates
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '25

03 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18273 Bug ID: 18273 Summary: Bulkmarcimport inserts authority duplicates 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: matthias.meusburger(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz When importing authorities through bulkmarcimport with the -match option, there are 3 possibilities: 1) An existing authority has been found in koha according to the -match criteria. The authority is replaced if needed (005 are checked first). This is ok. 2) No authority is found in koha according to the -match criteria. The authority is inserted. This is also ok. 3) Multiple authorities have been found in koha according to the -match criteria. The authority is inserted. => Is this the expected behavior? As the -match criteria is used for deduping, the existing authorities are very likely to be already existing duplicates. Do we really want to add another one? My feeling is that in this case, the authority should NOT be inserted. Can I have your opinion on this? -- You are receiving this mail because: You are watching all bug changes.

1 28