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

[Bug 31109] New: Add ability to lock bibliographic record or alert staff when another user is in the same bibliographic record
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '24

27 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31109 Bug ID: 31109 Summary: Add ability to lock bibliographic record or alert staff when another user is in the same bibliographic record Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When a cataloger is in bibliographic record-making changes, it would be nice to alert other staff (if they happen to be in the same bibliographic record) with a message box to indicate another staff member is also making changes. Additionally, allow staff to view the bibliographic record but not make changes if another staff member is also in the bibliographic record. This is a concern for larger consortiums that share records to have some sort of fail-safe method of making sure edits by any staff are saved. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 58

[Bug 26716] New: Allow specifying where to insert new fields in MARC Modification Templates
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '24

27 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26716 Bug ID: 26716 Summary: Allow specifying where to insert new fields in MARC Modification Templates Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org Currently newly-added fields are stuffed at the end of the record, after 999. Bug 24480 is changing that to insert them in numerical order. However, as the methods on MARC::Record illustrate, there are two other ways that people want to insert fields: grouped by hundreds, so that instead of adding a new 502 after any existing 502s you add it after every existing 5xx field, or, before or after a specific other field. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 25905] New: REST API: create endpoint for importing OAI-PMH records from external OAI-PMH clients
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '24

26 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25905 Bug ID: 25905 Summary: REST API: create endpoint for importing OAI-PMH records from external OAI-PMH clients Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au Following on from previous work on #10662 and koha-plugin-oaipmh-import, I'm now thinking that it would be best to have a REST API endpoint for importing OAI-PMH records in the Koha mainstream. This would give libraries assurance that the core OAI-PMH ingest functionality will be in the main codebase and get Koha community support. For now, I'm still planning to keep my planned OAI-PMH harvester/client as a plugin/third-party dependency, but completion of this work will allow Koha libraries to use any OAI-PMH harvester they choose to ingest records into Koha. This could be with a Perl cronjob using HTTP::OAI, or it could be a Golang daemon, or whatever. Lots of possibilities. Anyway, I've got a lot of this work done already in koha-plugin-oaipmh-import, so I'll look at re-organising it to fit into Koha proper. It'll be in my own time, so I don't have a timeline for it, but it is on my TODO list. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 29308] New: Regression: NewItemsDefaultLocation should not be applied to items.permanent_location
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '24

26 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29308 Bug ID: 29308 Summary: Regression: NewItemsDefaultLocation should not be applied to items.permanent_location Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl 21.05 made changes to NewItemsDefaultLocation that break the intended use of the feature. In 20.05 and earlier versions, the value in NewItemsDefaultLocation was only put in items.location. Items.permanent_location would be set to the items' intended eventual location, allowing it to later be updated using UpdateItemLocationOnCheckin. In 21.05, the value from NewItemsDefaultLocation is written into BOTH items.location and items.permanent_location, thereby breaking the usage with UpdateItemLocationOnCheckin. To recreate: - have shelving locations PROC and GEN - set NewItemsDefaultLocation to PROC - find or create a bib - add an item, do not select a shelving location - add a second item, select shelving location GEN - use SQL to confirm location and permanent_location (select itemnumber, barcode, location, permanent_location from items where biblionumber=X) - first item has location=PROC, permanent_location=PROC - second item item has location=GEN, permanent_location=GEN Were you to follow the same test plan on 20.05: - first item has location=PROC, permanent_location=NULL - second item item has location=PROC, permanent_location=GEN -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 26391] New: patron import tool notes info is incorrect
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '24

26 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26391 Bug ID: 26391 Summary: patron import tool notes info is incorrect Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 29904] New: Serials: Clear 'Automatically set to late' when changing status
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '24

26 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29904 Bug ID: 29904 Summary: Serials: Clear 'Automatically set to late' when changing status Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Yes it takes about half a second to clear it, but wouldnt it be marvelous when Koha would do it rightaway? And if we do this a million times, we win 500.000 seconds ! 138 hours ! We could signoff so much more patches :) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 29442] New: Show DefaultClassificationSource selection on Classification Sources page (classsources.pl)
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '24

25 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29442 Bug ID: 29442 Summary: Show DefaultClassificationSource selection on Classification Sources page (classsources.pl) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com On the classification sources page in Admin, it would be handy to have the selection from the DefaultClassificationSource visible somehow. Maybe a simple line of text at the top of the page, with a link to the system preference? Or some sort of icon or highlighting in the Classification Sources table? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 26122] New: Update item NotForLoan status when checking out to a statistical patron
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '24

24 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26122 Bug ID: 26122 Summary: Update item NotForLoan status when checking out to a statistical patron 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I've also filed bug 25847 for comparable functionality with the shelving cart. It'd be great if the syspref UpdateNotForLoanStatusOnCheckin was used when checking an item out to a statistical patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 33066] New: We need a KohaTable Vue component
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '24

24 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33066 Bug ID: 33066 Summary: We need a KohaTable Vue component Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Depends on: 23991 The way we deal with DataTables in Vue component is not nice, especially when we need to add buttons/link in the cell and interact with the rest of the Vue app from there. When I started to work on Vue last year there was no good solution from DataTables, now there is a Vue component. It is not perfect, you still cannot add Vue component in the DT component, but it brings something to follow. Agustin implemented something on theke/import_source_vue, but he went too far, and it will need to rewrite the whole ERM module. Additionally he didn't provide a solution that has the same features as what we have now. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23991 [Bug 23991] Move SearchSuggestion to Koha::Suggestions -- You are receiving this mail because: You are watching all bug changes.

1 159

[Bug 20511] New: Seasonal prediction just in the staff language
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '24

24 Sep '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20511 Bug ID: 20511 Summary: Seasonal prediction just in the staff language Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: hagud(a)orex.es QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com The seasonal (season, day and monthn) prediction it doens't change according the locale defined in the patterns, the pattern uses always the language of the staff user interface. If you create a pattern with staff user language in spanish, it doesn't matter you configure the locale.. the serialq it will be in spanish. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 45