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

[Bug 28579] New: Typo: No record have been imported because they all match an existing record in your catalog.
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28579 Bug ID: 28579 Summary: Typo: No record have been imported because they all match an existing record in your catalog. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org koha-tmpl/intranet-tmpl/prog/en/modules/acqui/addorderiso2709.tt:31 No record have been imported because they all match an existing record in your catalog. I think this should either read: "no records have" or "no record has"? -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 27735] New: Upload/Manage files that are not associated with items or patrons
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27735 Bug ID: 27735 Summary: Upload/Manage files that are not associated with items or patrons Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org It might be necessary to have images that are inserted in various places through admin or jquery that are not associated with items or patrons. It would be helpful to have a tool to upload, manage, or delete images from the Koha system that we can use on the site. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 27689] New: Kiki
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27689 Bug ID: 27689 Summary: Kiki Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: bugs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: jancokasusemongko(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 27693] New: Add ability to sort ElasticSearch configuration tables
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27693 Bug ID: 27693 Summary: Add ability to sort ElasticSearch configuration tables Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr Being able to sort the tables in search engine configuration could be very useful. That way it would be easier to check different settings, like which field are a "String" or "Date" type (search fields tab), which field are facetted, we can sort by Marc field to check the index used (biblio tab), etc. A personnal reflexion : I never understood why these tables have a drag and drop option ? Is there a secret use never found out ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 27705] New: Unfold facet groups
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27705 Bug ID: 27705 Summary: Unfold facet groups Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org A great option could be to have an option to unfold the group facet "ITEMTYPECAT". If I use the example given in the manual : it's great to filter on "Movies" items, but I don't have a Blu-ray player, I would be happy to unfold the "Movies" category to only select the "DVD" item type ! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 27722] New: Eliminate 'All' as an option from display location in OPAC and Koha news
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27722 Bug ID: 27722 Summary: Eliminate 'All' as an option from display location in OPAC and Koha news 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When the Koha News tool was just for OPAC News and 'librarian interface' all was a good option. Now that we have 10+ content areas options 'All' is just confusing. It should be eliminated as an option. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 27721] New: Circulation Workflow (Statuses)
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27721 Bug ID: 27721 Summary: Circulation Workflow (Statuses) Change sponsored?: --- Product: Koha Version: 19.11 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 It would be great if there were some kind of centralized workflow for processing items that would allow libraries to handle items the way they need to at each branch. Right now we have rules, and then we have statuses. There are some workflows for statuses peppered throughout the preferences, but nothing centralized, and far too limiting. I think some of these settings could be centralized through a common workflow interface, similar to (or maybe combined with) UpdateItemLocationOnCheckin, and be given some better flexibility. Please understand that I am just throwing this out there for a discussion. Some of these ideas might be redundant and might even be too complex a change for Koha. But, for the sake of discussion and brainstorming, what if we could define common triggers and actions, and allow libraries to combine these with common elements? Basically, it would be great to have a framework in which we could define what elements would trigger what kind of actions, and in what order. Here is where I am coming from. We have a library that would like to create a status for lost items that are in collections. Easy enough. We would like to make sure that when the item status is changed from long overdue to lost and in collections that the fee is not removed. We would also like it if an item with this status were checked in at some or all libraries, it would pause the check in with a message stating that it is in collections, are you sure you want to check this item in? Maybe we just simply need more status preferences? But, it seems we have a few peppered through the settings as it is, and it would be great if we had these in a central framework where we could see them all and prioritize them and have more options as to how they work. Does this status charge? Does it refund? Should it be confirmed? Should it block? Should it reroute? Should it notify a staff member? Should it go to a staff member for processing? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 3591] [OMNIBUS] "Family administrator" account for OPAC
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3591 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|"Family administrator" |[OMNIBUS] "Family |account for OPAC [OMNIBUS] |administrator" account for | |OPAC -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 32703] New: Patron category defaults to top pick if existing category no longer an option
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32703 Bug ID: 32703 Summary: Patron category defaults to top pick if existing category no longer an option Change 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We have added new patron categories and specified that some categories are now only for certain libraries. If a patron has one of the now restricted categories, when you edit the patron, they are automatically changed to the first unrestricted category in the list. This changes the patron category unexpectedly when editing the patron. If a patron is edited, and the category they are in is no longer valid, it should default to a blank selection and force you to choose a new category. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 10662] Build OAI-PMH Harvesting Client
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10662 --- Comment #318 from Koha Team University Lyon 3 <koha(a)univ-lyon3.fr> --- Hi, here are some news of KohaLa's thoughts. We would like to use an existing OAI-PMH harvester and 2 of them seem to be good candidates : - Catmandu harverster - HTTP::OAI::HARVESTER module Both are in perl. At the moment, we thought that the second could be a better choice because it's more up to date and we don't necessarily need to use Catmandu. What we would like is to use all the import tools already existing in Koha (XSLT, Record matching rules, MARC modification templates, Stage marc for import, Manage MARC overlay rules). We would like to add a OAI-PMH setting (like Z39-50 / SRU) in the staff interface with URL, SET, XML Format, authentication login, biblio/authority records, deleted records handling, email for logs, XSLT file, encoding, items handling, profile import. Every harvesting would be scheduled only via the cronjobs. We are currently trying to propose specifications during the next 2 days (KohaLa hackathon). Don't hesitate to give us feedback on these first ideas. Sonia -- You are receiving this mail because: You are watching all bug changes.

1 0