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

[Bug 8976] Default sequence of subfields in cataloguing editor
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8976 --- Comment #24 from Michal Denar <black23(a)gmail.com> --- Created attachment 114494 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=114494&action=e… Bug 8976: Sort subfields for authority records Same patch for the authority frameworks/records Sponsored-by: Orex Digital Signed-off-by: Michal Denar <black23(a)gmail.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8976] Default sequence of subfields in cataloguing editor
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8976 --- Comment #23 from Michal Denar <black23(a)gmail.com> --- Created attachment 114493 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=114493&action=e… Bug 8976: Add the ability to sort subfields for the MARC frameworks This new enhancement adds the ability to change the default order the subfields. Both bibliographic and authority MARC subfield structure are taken into account. And so the item edition as well (in the different screens when item can be added/edited). This will answer the following needs that have been listed in the comments of the bug report: - $i in 7xx fields should be the first subfield in the sequence - 300 fields are sorted number first when cataloguers enter the letter fields first - 100 field, it's commonly $a, $q, $d. Test plan: 1. Edit a MARC frameworks, field 300 2. Resort the subfield (drag and drop the tab of the subfield) as you like 3. Save => Notice that the list of fields are displayed following the order you chose 4. Edit it again => The order is correctly kept! 5. Create a new bibliographic record 6. Notice that the subfields are order in the same sequence 7. Fill different subfields, not all 8. Save, edit again 9. Note that the subfields that have been filled are listed first, then the empty ones. But the sequence defined at the framework level is kept. 10. Do the same for an authority framework and create/edit an authority record 11. Modify item (952) subfields order 12. Create an item and confirm that the order is correct 13. Modify the ACQ framework, 952, modify the order of the subfield 14. Create a new order and confirm that the item form has the subfield ordered following the sequence defined at the framework level QA: Note that this patch is about bibliographic records only, next patches deal with authotiries and items. Sponsored-by: Orex Digital Signed-off-by: Michal Denar <black23(a)gmail.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8976] Default sequence of subfields in cataloguing editor
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8976 Michal Denar <black23(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #114345|0 |1 is obsolete| | Attachment #114346|0 |1 is obsolete| | Attachment #114351|0 |1 is obsolete| | Attachment #114352|0 |1 is obsolete| | Attachment #114353|0 |1 is obsolete| | Attachment #114354|0 |1 is obsolete| | Attachment #114355|0 |1 is obsolete| | --- Comment #22 from Michal Denar <black23(a)gmail.com> --- Created attachment 114492 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=114492&action=e… Bug 8976: Add marc_subfield_structure.display_order Sponsored-by: Orex Digital Signed-off-by: Michal Denar <black23(a)gmail.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8976] Default sequence of subfields in cataloguing editor
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8976 Michal Denar <black23(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 3150] Move emails for sending cart and list contents into notices tool
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3150 --- Comment #16 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Aleisha Amohia from comment #15) > Yup... What Joubu has said is just a longer way of saying what I said in my > comment :) so glad we're all agreed. Took me a little bit to get there :) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 3150] Move emails for sending cart and list contents into notices tool
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3150 --- Comment #15 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Yup... What Joubu has said is just a longer way of saying what I said in my comment :) so glad we're all agreed. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8976] Default sequence of subfields in cataloguing editor
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8976 --- Comment #21 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I agree with Jonathan in that we should never change the sequence of subfields in an existing bibliographic record - imported or already in Koha. MARC requires some subfields to be in a specific sequence that is not alphabetical or easy to guess. I am not sure how the item forms are build in several places - only that the ones in acq and serials are "different" and have not all features from the frameworks. Maybe worth checking those for a separate bug. But I think this one here aims mostly at bibliographic and authority records? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 25097] New: Add option to message_queue to allow for only specific sending notices
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25097 Bug ID: 25097 Summary: Add option to message_queue to allow for only specific sending notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The message_queue.pl currently will send all the messages queued up. It would be nice to have some control over which messages are to be sent. Example: We have libraries who only wanted to send 'hold notices' but not overdue, advance notice, etc during the covid-19 quarantine. And some that were the opposite - turn off hold notices, but send other generated notices. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 12430] Relevance ranking should also be used without QueryWeightFields system preference
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12430 --- Comment #93 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- It's likely that the tests should just expect undef instead of '' But better ask for confirmation ^_^ -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12430] Relevance ranking should also be used without QueryWeightFields system preference
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '20

17 Dec '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12430 --- Comment #92 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- Test plan works in 19.11.x but automated test doesn't [1] (t/Search/buildQuery.t) It works in 20.05.x Here is maybe the place to looks in the code. Does anyone understand the difference there or somewhere else that affect $limit_desc and $limit? 20.05.x: https://gitlab.com/koha-community/Koha/-/blob/8a9553c4ae62aa05d7d3529806d8f… 19.11.x: https://gitlab.com/koha-community/Koha/-/blob/608512179cf8f354ca76bab32e874… [1] Failed test: kohadev-koha@ec7b568b5d3d:/kohadevbox/koha$ prove t/Search/buildQuery.t t/Search/buildQuery.t .. 1/10 # Failed test 'Limit is correct' # at t/Search/buildQuery.t line 92. # got: undef # expected: '' # Failed test 'Limit desc is correct' # at t/Search/buildQuery.t line 94. # got: undef # expected: '' # Looks like you failed 2 tests of 13. # Failed test 'test weighted autotruncated' # at t/Search/buildQuery.t line 107. # Failed test 'Limit is correct' # at t/Search/buildQuery.t line 130. # got: undef # expected: '' # Failed test 'Limit desc is correct' # at t/Search/buildQuery.t line 132. # got: undef # expected: '' # Looks like you failed 2 tests of 13. # Failed test 'test* weighted autotruncated' # at t/Search/buildQuery.t line 144. # Failed test 'Limit is correct' # at t/Search/buildQuery.t line 167. # got: undef # expected: '' # Failed test 'Limit desc is correct' # at t/Search/buildQuery.t line 169. # got: undef # expected: '' # Looks like you failed 2 tests of 13. # Failed test 'test weighted not-autotruncated' # at t/Search/buildQuery.t line 181. # Failed test 'Limit is correct' # at t/Search/buildQuery.t line 316. # got: undef # expected: '' # Failed test 'Limit desc is correct' # at t/Search/buildQuery.t line 318. # got: undef # expected: '' # Looks like you failed 2 tests of 13. # Failed test 'one and two weighted autotruncated' # at t/Search/buildQuery.t line 330. # Looks like you failed 4 tests of 10. -- You are receiving this mail because: You are watching all bug changes.

1 0