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

[Bug 22371] New: MARC bibliographic framework plugin to generate Cutter-Sanborn
by bugzilla-daemon＠bugs.koha-community.org 09 May '21

09 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22371 Bug ID: 22371 Summary: MARC bibliographic framework plugin to generate Cutter-Sanborn Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: italo.barbosa.brasileiro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- The plugin (.pl) generates the Cutter-Sanborn code, and will be added to the list of plugins intended for the fields in MARC bibliographic frameworks. To use the plugin, it is necessary to associate it with the Cutter field in the framework. By clicking on the Cutter field, the plugin generates the Cutter code, from the values entered in the fields 100$a (Personal name), 110$a (Corporate name) and/or 245$a (Title statement). An initial version of the plugin was created, which operates as follows: 1) Use the field 100$a to generate the Cutter, and adds the first letter of the title (245$a) to the end of the Cutter code; 2) If field 100$a is not filled, use field 110$a and add the first letter of the title (245$a) to the end of the Cutter code; 3) If none of the fields 100$a or 110$a are filled, the cutter is generated from field 245$a, without adding the first letter of the title to the end of the code. Some observations: - To fill the Cutter, simply click on the field and the cutter is displayed. - If none of the fields are filled, the cutter is not generated. - It is important to fill the indicator 2 of field 245 with the number of characters used by the article preceding the title of the work (if any). The blank spaces also count. If the indicator 2 is not filled, the plugin understands that the value is 0. - For fields with special characters, the following list of characters is currently considered: ãâáàÃÃÂÁÀÉÊéêÍÎíîóõôṌÕÔṌÚÛúûçÇÑñ -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 27855] New: Allow embedding extended_attributes on /patrons routes
by bugzilla-daemon＠bugs.koha-community.org 07 May '21

07 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27855 Bug ID: 27855 Summary: Allow embedding extended_attributes on /patrons routes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 39

[Bug 28002] New: Add optional extended_attributes param to POST /patrons
by bugzilla-daemon＠bugs.koha-community.org 07 May '21

07 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28002 Bug ID: 28002 Summary: Add optional extended_attributes param to POST /patrons Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com Bug 27853 highlighted some patron's shouldn't be created through the API if they don't satisfy the mandatory extended attributes requirements. Solving it is not possible without adding a new parameter and proper handling to the current route. This bug proposes to add that parameter. It is based on the work done in bug 23666 and its tree. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 23666] New: Add API route for additional patron attributes
by bugzilla-daemon＠bugs.koha-community.org 07 May '21

07 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23666 Bug ID: 23666 Summary: Add API route for additional patron attributes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: kugler_stefan(a)hotmail.com Add API routes to manage additional patron attributes. A simple implementation could only allow a modification of all attributes en bloc, eg: GET /patrons/{patron_id}/attributes Get all additional attributes POST/PUT? /patrons/{patron_id}/attributes Create/overwrite additional attributes DELETE /patrons/{patron_id}/attributes Delete all additional attributes A more granular implementation could be eg: GET /patrons/{patron_id}/attributes/{code} Get additional attribute "code" PUT /patrons/{patron_id}/attributes/{code} Overwrite additional attribute "code" DELETE /patrons/{patron_id}/attributes/{code} Delete additional attribute "code" To be discussed: How to handle repeatable attributes with multiple values. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 58

[Bug 27853] New: POST /patrons doesn't enforce mandatory extended attributes
by bugzilla-daemon＠bugs.koha-community.org 07 May '21

07 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27853 Bug ID: 27853 Summary: POST /patrons doesn't enforce mandatory extended attributes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com If there are extended attributes types that are mandatory, the POST /patrons route should fail if the request doesn't meet this requirement. Unfortunately, we have no way (yet) to pass extended attributes on the POST. So to solve this bug, we need to add a way to pass extended attributes along with the patron object. I propose: POST /patrons { "first_name": "Tomasito", ... "extended_attributes": { "SHOW_BCODE": [ 1 ], "COURSES": [ "ALGO1", "DATABASES" ] } } I choose to force them to be arrays for simplicity (they can be repeatable), but we can check the data type on the controller (i.e. if ( ref($extended_attributes) eq 'ARRAY') { # loop case } else { # scalar case } ). I'm open for opinions. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 14957] Write protecting MARC fields based on source of import
by bugzilla-daemon＠bugs.koha-community.org 07 May '21

07 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 --- Comment #333 from Jonathan Druart <jonathan.druart+koha(a)gmail.com> --- (In reply to Jonathan Druart from comment #331) > I know librarians can have weird needs but, should we really offer the > "custom" preset? I am reading the tests right now and some combinations are > doing funky stuffs. Maybe we could simplify the UI if we stick to the only 1 > "action" column with the predefined ones? (not considering this question a > blocker, but I would be happy to get an answer). See the "warning"s and "fixme"s from the last patch please. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14957] Write protecting MARC fields based on source of import
by bugzilla-daemon＠bugs.koha-community.org 07 May '21

07 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 --- Comment #332 from Jonathan Druart <jonathan.druart+koha(a)gmail.com> --- Created attachment 120705 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=120705&action=e… Bug 14957: Improve readbility of tests Not saying that they were not readable before, but I had to do some changes to compare the before/after records and it was easier that way. Feel free to obsolete if you disagree. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 19787] New: Adding system preferences to disable the screen messages for SIP flags in Self-Checkout
by bugzilla-daemon＠bugs.koha-community.org 07 May '21

07 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19787 Bug ID: 19787 Summary: Adding system preferences to disable the screen messages for SIP flags in Self-Checkout Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com These screen messages are known to confuse users, especially when they are just informative and don't require action. I'll be creating a new system preferences tab for SIP in Administration and adding a bunch of new system preferences to enable whether the screen messages for each flag are displayed or not. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 12169] Improve reliability of sip_shutdown script
by bugzilla-daemon＠bugs.koha-community.org 07 May '21

07 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12169 Kyle M Hall <kyle(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kyle(a)bywatersolutions.com --- Comment #15 from Kyle M Hall <kyle(a)bywatersolutions.com> --- Package install already have this type of functionality. Good to see it available for non-package installs! Only open question is that of an upgrade path. I think upgrade notes will be needed. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12169] Improve reliability of sip_shutdown script
by bugzilla-daemon＠bugs.koha-community.org 07 May '21

07 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12169 --- Comment #14 from Kyle M Hall <kyle(a)bywatersolutions.com> --- Created attachment 120703 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=120703&action=e… Bug 12169: Fix SIPconfig.xml, restore missing end tag Signed-off-by: Kyle M Hall <kyle(a)bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

1 0