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

[Bug 5161] Patron attributes clearing if duplicate warning
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '20

27 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5161 --- Comment #14 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- Nice work everyone! Pushed to master for 20.05 -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 5161] Patron attributes clearing if duplicate warning
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '20

27 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5161 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version(s)| |20.05.00 released in| | Status|Passed QA |Pushed to master -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 25142] Staff can access patrons' infos from outside of their group
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '20

27 Apr '20

1 0

[Bug 16922] New: Add RewriteRule to apache-shared-intranet for dev package installs
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '20

27 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16922 Bug ID: 16922 Summary: Add RewriteRule to apache-shared-intranet for dev package installs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 25009] opac-showmarc.pl allows fetching data directly from import batches
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '20

27 Apr '20

1 0

[Bug 7013] required format is not enforced for authorized values
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '20

27 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7013 --- Comment #23 from Pablo AB <pablo.bianchi(a)gmail.com> --- Sorry, it was for bug 23861 :( -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 7013] required format is not enforced for authorized values
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '20

27 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7013 Pablo AB <pablo.bianchi(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pablo.bianchi(a)gmail.com --- Comment #22 from Pablo AB <pablo.bianchi(a)gmail.com> --- On bug 17216 it was created the authorised_value_categories table. Probably should be added a new column there for the description of each category of AVs, and therefore add to the UI a Modify button to change it. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 25272] New: Different behavior between live and deferred merges and between merged and retained record
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '20

26 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25272 Bug ID: 25272 Summary: Different behavior between live and deferred merges and between merged and retained record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl A bit complicated, and requires badly mislinked data to be seen. To create the mislinks, you either have to edit the Default MARC Framework to allow editing of subfield 9, which is sort of a pain, or just enable the advanced editor with the system preference . You have to edit system preferences anyway, to lower AuthorityMergeLimit, so I recommend that method. 1. Change the system preference AuthorityMergeLimit to 1 2. Enable EnableAdvancedCatalogingEditor 3. Authorities - New - Personal Name 4. Five required fields on the first tab, with red labels, just click in each to fill in automatic data 5. On the second tab, click the HEADING--PERSONAL NAME label to open the subfields, and in subfield a type the letter A and click Save (there will probably be a duplicate warning, just click No, Save as new) 6. Click the Edit menubutton, and choose Edit as new (duplicate) 7. On the "1" tab, change the A to B and save 8. Edit menubutton, Edit as new (duplicate), change the B to C and save 9. At this point, you know the authority id number for C, because it's shown there on the page as "Authority #1710". That tells you that B is one less, and A is two less. You need to know those three numbers. 10. Go to Circulation, Search the catalog, search for anything that will return at least five records with authors. Perl works nicely. 11. On the first, click Edit record, which will open the basic editor. Click settings, Switch to advanced editor, and click through the warning. 12. Find the 100 tag for the author, and its subfield 9, which will look like ‡917 13. Leaving the 9, replace the number with the number for your first authority record, the author A 14. Do the same thing for two more records, using the number for your second author, B 15. Do the same thing for two more records, using the number for your third author, C 16. Back to Authorities, search for Personal name / starts with / A, and verify that you have 1 matching record. Open the link for that record in a new tab. 17. From that tab, open Authorities in a new tab, search for Personal name / starts with / B, verify it has 2 records, open the link for them in a new tab. 18. Authorities in a new tab, name starts C, verify there are 2, open the records in a new tab. 19. Back to the authorities tab for A, Actions button, merge 20. Over to the authorities tab for B, Actions button, merge 21. You do want to keep B, so click Next, then Merge 22. In the tab with the two records for B (which is a search for B's authority id) reload the page, you should now see three records, the one that was linked to A now having B as the author because it was merged immediately, and the other two still having their original authors because 2 was over the merge limit 23. Run misc/cronjobs/merge_authorities.pl -b 24. Reload the tab with the search for B's authority id, all three records should now have the author B. 25. Merge B to C 26. Both were over the limit, so nothing has changed 27. Run misc/cronjobs/merge_authorities.pl -b 28. Reload the tab with C's records, there should now be 5, all with the author C Alas, you haven't yet seen the bug, only that it doesn't occur when the mislinked bib records are linked to the proper sort of authority for the bib field. Now you have to go through all those steps again, but instead of creating personal name authorities, create corporate name authorities. Still put the authority numbers into the 100 fields of the bib records. When you merge A to B, the bib record for A will be unchanged, still having the original author, still having the mislinked number in subfield 9 which goes to the wrong authority. When you run the cronjob to do the deferred B to B merge, again nothing will change. But when you merge B to C, so that both halves of the merge are deferred, while the C to C merge will not change anything on those two records, the B to C merge will remove a 100 field and replace it with a 110 field for the corporate author C. Only in merges through the cronjob, and only for the ones that were mislinked to the authority record that's going away, it ignores the tag number and just replaces whatever field has the authority id in subfield 9. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 5161] Patron attributes clearing if duplicate warning
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '20

26 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5161 --- Comment #13 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Great to see this old bug squashed! -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 5161] Patron attributes clearing if duplicate warning
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '20

26 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5161 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #103418|0 |1 is obsolete| | --- Comment #12 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Created attachment 103717 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=103717&action=e… Bug 5161: Keep patron's attributes on warning/duplicate When a patron is added or modified and a warning appears (duplicate, inconsistent data, etc.) the form lost the patron's attributes. Test plan: Create some attribute types for patrons Create a new patron, use an userid that already exists and fill the attributes => You get a warning and the attributes are kept Modify the userid and save again Edit the same patron Modify the attributes, as well as the userid (to get the duplicate warning) => You get a warning and the attributes are kept with the modified values Modify the userid and save again => The new values are saved Edit the attributes from the detail page (so not with the full edit form) Modify them and save => The new values are saved Signed-off-by: David Nind <david(a)davidnind.com> Signed-off-by: Katrin Fischer <katrin.fischer.83(a)web.de> -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0