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

[Bug 15377] Remove 'checked out' items from course reserves
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15377 --- Comment #3 from Rogan Hamby <rogan.hamby(a)gmail.com> --- Removing the check for a circulation preventing the removal is fairly straightforward. Should we add a confirmation dialogue or some visual indicator that the item is currently checked out? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 15377] Remove 'checked out' items from course reserves
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15377 Rogan Hamby <rogan.hamby(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rogan.hamby(a)gmail.com --- Comment #2 from Rogan Hamby <rogan.hamby(a)gmail.com> --- Removing the check for a circulation preventing the removal is fairly straightforward. Should we add a confirmation dialogue or some visual indicator that the item is currently checked out? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 17984] New: Warn catalogers if item type doesn't match 942c
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17984 Bug ID: 17984 Summary: Warn catalogers if item type doesn't match 942c Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Because circ rules can be thrown off if the item type in the items record doesn't match the 942c when it comes to bib level hold requests, it would be helpful to have a warning next to field "y - Koha item type" if it does not match the 942c. Maybe something like: "WARNING: item type does not match 942c. May have unexpected results on hold requests." -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 10532] koha-run-backups option --output doesn't work
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10532 Bohdan <b.pastern4k(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |b.pastern4k(a)gmail.com --- Comment #6 from Bohdan <b.pastern4k(a)gmail.com> --- Still a problem on 19.05 and 19.11. Output option does not create directories named as instances in the backup folder. The following error occurs ls: cannot access /path: No such file or directory And even after these folders are created, script still ignores everything and simply creates files inside /var/spool/koha. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8643] Add important constraint to MARC tags and subfields
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8643 Maryse Simard <maryse.simard(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Needs Signoff --- Comment #93 from Maryse Simard <maryse.simard(a)inlibro.com> --- (In reply to Jonathan Druart from comment #88) > 1. Who is the original author of this patch? Bernardo? Regarding the history > I do not think so. The author was lost when the patches were squashed. I changed it back to simith. > 2. Not blocker but, when a code is not nice, better refactore and improve it > than duplicate it ;) > I am referring to the JS code to test if a mandatory field is filled, it > would have been easier to make the function accepts an argument to check for > mandatories or importants. It's true this duplication is not very nice. I added a patch to try and reuse the current function instead of duplicating it. I followed your suggestion and used an argument to indicate whether we want a mandatory or important check. I've also set the bug back to Needs Signoff because of this change. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8643] Add important constraint to MARC tags and subfields
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8643 --- Comment #92 from Maryse Simard <maryse.simard(a)inlibro.com> --- Created attachment 97326 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=97326&action=ed… Bug 8643: code cleanup Merges "AreMandatoriesNotOk" and new "AreImportantsNotOk" into one function "AreFieldsNotOk". It can search for mandatory or important fields depending on the value of it's boolean "mandatory" parameter. To test: This patch should not change current behavior. Follow the test plan from previous patch and check that saving is still prevented for unfilled mandatory fields. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8643] Add important constraint to MARC tags and subfields
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8643 Maryse Simard <maryse.simard(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #96627|0 |1 is obsolete| | --- Comment #91 from Maryse Simard <maryse.simard(a)inlibro.com> --- Created attachment 97325 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=97325&action=ed… Bug 8643: Add important constraint to marc subfields This fix permits to add an "Important" option to the marc structure pages. Testing: 1) Apply the patch 2) Run updatedatabase.pl 3) Regenerate CSS 4) Define 100 as an "important" field ( Administration » MARC bibliographic framework » MARC structure ( Default Frameword) » Edit ) 5) Define 100$a as an "important" subfield (Administration » MARC bibliographic framework » MARC structure (Default Frameword) » Subfield » Onglet a) 6) Edit a record to clear the field 100 (subfields are all blank) 7) Save the record. 8) Validate the following message: A few important fields are not filled: * tag 100 subfield a Nom de personne in tab * Field 100 is important, at least one of its subfields should be filled. Are you sure you want to save? Sponsored by the CCSR ( http://www.ccsr.qc.ca ) Signed-off-by: Bernardo Gonzalez Kriegel <bgkriegel(a)gmail.com> Tested on update and new install, works as described. No errors. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 16766] New: Merging two records with title level holds for the same patron creates two holds on one record
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16766 Bug ID: 16766 Summary: Merging two records with title level holds for the same patron creates two holds on one record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: 1 - Place a title level hold for a patron on a record 2 - Do it again on another record 3 - Merge these recrods 4 - See they now have two holds on one record -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 24411] New: Offline circulation should require login
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24411 Bug ID: 24411 Summary: Offline circulation should require login 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 Currently, regular circulation tracks who checked in/out what. Offline Circ does not track this information. Instead, when offline circ info is uploaded, it is recorded as the person doing the upload. I would suggest that offline circ require a quasi login - the Koha username should be asked for. Obviously, there is no way to authenticate if Koha is down, but this would give us something. Then, when the information is uploaded, Koha should confirm the id, and if it is an actual patron, show (and optionally confirm) that is the correct person. If it can't confirm the staff member (keyed in wrong), we should have a pref that would either ask you if you want to proceed uploading, recording the staff member as you (the uploader), or display what was entered and select the staff member who you think was circing at the time. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 10758] Show bibliographic information of deleted records in acquisitions
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10758 --- Comment #69 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- (In reply to Katrin Fischer from comment #68) > (In reply to Jonathan Druart from comment #67) > > That should be done on top of bug 20271. > > We could do it in a different way too - I know that we got some logic in a > table now where 2 biblionumbers are stored in different columns - that way > FK can be set. Martin did it, I just fail to remember the bug report and > table. Yes, but it is adding more stuffs to unravel for bug 20271. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0