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

[Bug 24222] New: Simplify interface for adding/changing mappings
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24222 Bug ID: 24222 Summary: Simplify interface for adding/changing mappings 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: mkstephens(a)lancasterseminary.edu All search fields are in a single group and are not marked as being strictly for authorities or bibliographic records. On the search engine configuration page, when adding mappings to either the bibliographic records tab or the authorities tab, all search fields are available from the drop down menu at the bottom of the page. It would be really nice if there was a way to distinguish between the two groups of search fields so that these drop down menus would only show the fields for that record type. An alternative might be to reconfigure the way this page displays. Show the tables in a collapsed view based on search field. Expand a search field to see its mappings along with an empty field with "+ Add". This solution would allow a user to add mappings under the appropriate search field without having to manually select the field from a drop down.This would also make it easier to double-check to make sure you're entering the correct mapping since you'd be entering it in context, instead of at the bottom of a long list. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 24894] New: Allow configuration of search dropdowns
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24894 Bug ID: 24894 Summary: Allow configuration of search dropdowns Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently, we can customize the indices included in the basic and advances search dropdowns via jQuery. It'd be great to have some more user-friendly interface for this. It might make sense to tie it into the Elastic search engine config page, or to make it its own system preference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 26298] New: If MaxItemsToProcessForBatchMod is set to 1000, the max is actually 999
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26298 Bug ID: 26298 Summary: If MaxItemsToProcessForBatchMod is set to 1000, the max is actually 999 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org So this is similar to bug 10163, but I don't think it's the same thing. I noticed that if you have 1000 in MaxItemsToProcessForBatchMod, and you try to process 1000 items, there's an error message "Too many items (1000): You are not allowed to edit more than 1000 items in a batch." The message itself is a bit confusing because 1000 is not "more than" 1000. And you're probably thinking "well, just put 999 items in your file and voilà!", but if you batch modify using the reports, the options are 10, 20, 50, 100, 200, 300, 400, 500, and 1000. If you have a lot of batches to do, the difference between 500 and 1000 is double the work. To reproduce: 1- Set MaxItemsToProcessForBatchMod to 1000 2- Go to Reports 3- Make a report for itemnumbers that will give you at least 1000 items (ex. SELECT itemnumber FROM items) 4- Save and run the report 5- In "Rows per page", choose 1000 6- Click on "Batch operations with 1000 visible records" > Batch item modification 7- Notice that the item modification form isn't there and that the message says "Too many items (1000): You are not allowed to edit more than 1000 items in a batch." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 24903] New: Special characters like parentheses in numbering pattern cause duplication in recievedlist
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '21

10 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24903 Bug ID: 24903 Summary: Special characters like parentheses in numbering pattern cause duplication in recievedlist Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 CC: colin.campbell(a)ptfs-europe.com Just an example 2016 (No. 12); 2017 (No. 3); 2017 (No. 2); 2017 (No. 1); 2017 (No. 4); 2017 (No. 5); 2017 (No. 6); 2017 (No. 7); 2017 (No. 8); 2017 (No. 9); 2017 (No. 10); 2017 (No. 11); 2017 (No. 12); 2018 (No. 1); 2018 (No. 2); 2018 (No. 3); 2018 (No. 4); 2018 (No. 5); 2018 (No. 6); 2018 (No. 7); 2018 (No. 12); 2018 (No. 9); 2018 (No. 10); 2018 (No. 11); 2019 (No. 1); 2019 (No. 2); 2019 (No. 2); 2019 (No. 4); 2019 (No. 3); 2019 (No. 5); 2019 (No. 6); 2019 (No. 7); 2019 (No. 11); 2019 (No. 7); 2019 (No. 8); 2019 (No. 8); 2019 (No. 9); 2019 (No. 9); 2019 (No. 11); 2019 (No. 9); 2019 (No. 8); 2019 (No. 7); 2019 (No. 6); 2019 (No. 5); 2019 (No. 4); 2019 (No. 3); 2019 (No. 2); 2019 (No. 1); 2018 (No. 12); 2019 (No. 9); 2019 (No. 8); 2019 (No. 1); 2018 (No. 12) Each edit adds at the end since the parentheses break the regex. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 24842] New: Automatic serials missing list feeding does not work when the numbering sequence includes regexp specific characters
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '21

10 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24842 Bug ID: 24842 Summary: Automatic serials missing list feeding does not work when the numbering sequence includes regexp specific characters Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com We can encounter this issue, when we choose to automatically feed the serials missing list of a subscription (Manual history is uncheck in the subcription planning form). When setting or removing the missing status to a serial issue in the staff interface, the process in the code of adding the issue numering sequence or removing it from the missinglist is based on some regular expression. It's not uncommon that librarians use characters like parenthesis in this sequence, for exemple to add year detail : No 236 (2019) We can even fall upon + or * characters. The consequence is that they are interpreted by the regexp as capturing characters rather then litterals and this causes the process to fail. The result is the creation of multiple doubles in the missing list. This patch aims to solve the problem Test plan : To go faster, choose an existing subscription, click on "Edit/Edit as new(duplicate)" Uncheck Manual history and go to next page Choose whatever simple config for this new subscription Exemple : Frequency : 1/month Subscription length : 12 Subscription start date : 01/01/2020 Subscription end date : nothing Numbering pattern : Volume, number Last value volume :2019 number : 1 Click on "Hide advanced pattern" then "Modify pattern" In the "Numbering formula pattern" zone, add parenthesis around {X}: Vol({X}), No {Y} or an other critical character like + : Vol ({X}), No {Y} + suppl. Fullfill the "Pattern name" : MyTest Save as new pattern Test prediction pattern Save subscription 1) Receive one or two issues on this subscription 2) For the next expected one, set to any missing status rather than arrived one 3) Go to check the missing list in the summary tab of subscription : you can see that the issue had not been added to the list. Install the patch 1) go back to Receive page and set the expected issue as missing. 2) go back to check the missing list : now the issue number is in the list 3) go back to Receive page and set the last missing issue as arrived. 4) go back to missing list : the issue had been removed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 20238] New: Show description of ITEMTYPECAT instead of code in itemtypes summary table
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '21

10 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20238 Bug ID: 20238 Summary: Show description of ITEMTYPECAT instead of code in itemtypes summary table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial 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 When working with grouped item types using ITEMTYPECAT authorised values, looking at the item types table, it shows the code, not the description. On editing an item type, we show the description - so there is some confusing mismatch there. Both should show the description. To check: - Add a value to the ITEMTYPECAT authorised value category - Edit an item type and pick that value as search category - Save - Verify the code shows up in the table, but not the description -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 23816] New: Password Enhancements
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '21

09 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23816 Bug ID: 23816 Summary: Password Enhancements 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: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Allow specified categories to be exempt from the system preferences of "Require Strong Password" and "Minimum Password Length". The goal is to force staff to have long complex passwords while simultaneously allowing patrons to have non-strong, shorter passwords if they wish. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 112

[Bug 26252] New: Allow patron_emailer.pl to select notice branch from report
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '21

09 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26252 Bug ID: 26252 Summary: Allow patron_emailer.pl to select notice branch from report 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org One of the options when running patron_emailer.pl is to select which branch's notice you want to use. As it is now, that choice applies to your whole list of patrons. It'd be great if the cron could be told to look at branchcodes in the report to select a notice for each patron. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 23682] New: Add ability to manually import EDI invoices as an alternative to automatic importing on download
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '21

09 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23682 Bug ID: 23682 Summary: Add ability to manually import EDI invoices as an alternative to automatic importing on download Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some library would like to delay the importing of invoices until a time of their choosing. The invoices should be imported into the database as they do now, but the invoice processing should be skipped. Instead, any invoice file with a status of 'new' should have an 'Import' button to process the invoice. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 23019] New: Ability to create 'matching profiles' when importing records
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '21

09 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23019 Bug ID: 23019 Summary: Ability to create 'matching profiles' when importing records 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: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- This development will allow you to have the ability to create “matching profiles” for use on the “Stage MARC Records for Import” screen. This would make it possible to choose a profile rather than manually filling in each of the fields for record type, encoding, record and item matching rules and actions each time a batch of MARC records is imported. For example, we might create “matching profiles” for different vendors or formats, and it would save time to select the appropriate profile (maybe from a drop-down list on the page) and have the fields populate automatically. Specs: Ability to set up profiles and save them while working in the Tools->StageMarcRecords module. Ability to manage/edit profiles in the Admin area (similar to Record->Matching Rules). Create an API to pull the profile data into Import Tool when selected on the Import Screen. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 93