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

[Bug 17867] New: Improve display of source (MARC21 773) in result list
by bugzilla-daemon＠bugs.koha-community.org 14 May '23

14 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17867 Bug ID: 17867 Summary: Improve display of source (MARC21 773) in result list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Currently only $t is shown. If there is no author in $a, the title goes in $a and there is no $t. We should also catch this case and show at least a and t. >From the XSLT: 928 <xsl:if test="marc:datafield[@tag=773]"> 929 <xsl:for-each select="marc:datafield[@tag=773]"> 930 <xsl:if test="marc:subfield[@code='t']"> 931 <span class="results_summary"> 932 <span class="label">Source: </span> 933 <xsl:value-of select="marc:subfield[@code='t']"/> 934 </span> 935 </xsl:if> 936 </xsl:for-each> 937 </xsl:if> Note: if there were multiple 773, the lable would be printed mulitple times. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 22428] New: MARC modification template cuts text to 100 characters
by bugzilla-daemon＠bugs.koha-community.org 12 May '23

12 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22428 Bug ID: 22428 Summary: MARC modification template cuts text to 100 characters 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 Target Milestone: --- When trying to update a field using a MARC modification template, it is impossible to put a value of over 100 characters. To reproduce: 1. Go to Tools > MARC modification templates 2. Click on 'New template' 3. Name your new template and click on 'Submit' 4. Click on 'New action' 5. Enter the following information in the form - 'Add new' - field(s): 856 y - with value: Organization-wide access - sign on to OnePass / Accès à l'échelle de l'organisation - Ouvrez une session (OnePass) 6. Click on Add action 7. Note that the text is cut in the displayed table 'Organization-wide access - sign on to OnePass / Accès à l'échelle de l'organisation - Ouvrez une ses' 8. Do a search to obtain a biblionumber 1. Make a search in the catalog 2. Click on the title to go to the detailed record 3. Click on the 'MARC' tab 4. The biblionumber is written next to MARC record: 5. Copy the biblionumber 9. Go to Tools > Batch record modification 10. In the 'List of biblionumbers...' text box, paste the biblionumber 11. Choose the template created at step 3 in the 'Modify record using the following template:' drop down menu 12. Click on 'Continue' 13. Click on 'Show MARC' to see the result of the modification (the added line is usually at the bottom, note that the text is still cut after 100 characters, so not only a display bug) 14. Click on 'Close' 15. Click on 'Modify selected records' 16. Click on the biblionumber to see the modified record 17. In the detailed record, the 856y field is under 'Online resources' (note that the text is still cut) I noticed that in the database, the field field_value in the table marc_modification_template_actions is limited to 100 characters. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 28126] New: Remove AllowPurchaseSuggestionBranchChoice from the Koha manual
by bugzilla-daemon＠bugs.koha-community.org 12 May '23

12 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28126 Bug ID: 28126 Summary: Remove AllowPurchaseSuggestionBranchChoice from the Koha manual Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: erohlfs(a)equinoxinitiative.org QA Contact: testopia(a)bugs.koha-community.org In version 20.11, we saw the introduction of a new System Preference "OPACSuggestionUnwantedFields" and the removal of "AllowPurchaseSuggestionBranchChoice" via https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23420 This is a request to remove the AllowPurchaseSuggestionBranchChoice description from the official Koha manual. https://koha-community.org/manual/20.11/en/html/systempreferences.html#allo… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 30213] New: Hide Delete (aka Priority) column when user only has place_hold permission
by bugzilla-daemon＠bugs.koha-community.org 12 May '23

12 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30213 Bug ID: 30213 Summary: Hide Delete (aka Priority) column when user only has place_hold permission Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com With the change to holds permissions in Bug 29540, the Delete (or Priority, with full holds permissions) column isn't useful and is misleading for users with only the place_hold permission. They don't have the option to change holds' priority using the column, and if they select 'del' on a patron to delete their hold, they get locked out for having insufficient permissions when they click the Update Hold(s) button. But this is misleading because they *can* delete an individual hold using the red X. It would be clearer if that entire column were hidden for users with only the place_hold permission. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 29252] New: Document the uses of 942c (MARC21)
by bugzilla-daemon＠bugs.koha-community.org 11 May '23

11 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29252 Bug ID: 29252 Summary: Document the uses of 942c (MARC21) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org There was a discussion on the mailing list about the reasons of 942c. See this thread : https://lists.katipo.co.nz/pipermail/koha/2021-October/056838.html >Good afternoon, > >I recall reading (in the Koha manual?) the explanation for why it is >advantageous to define Koha item type in the bib 942 field. I believe it >has to do with exporting records, or the scope of records that is included >when doing some type of report? I'm trying to locate that information >again, but can't find it for the life of me. > >Does this seem familiar to anyone? Thanks. > > >Tasha Bales ------------ >I can't find the information right now, though I know I've seen it somewhere. >My understanding is when importing a MARC record, 942$c is treated as the >item type in the bibliographic record, and 952$y is the item type >for the item record (assuming a 952 holding field was present). > >I have also observed that when you create a new item record from an >existing bib record, 942$c gets copied into the new item's type. So >it's helpful to make sure that the item type in the bib record was set >correctly when it was created (or imported). > >This wiki page talks about 952, but not 942: > >https://wiki.koha-community.org/wiki/Holdings_data_fields_(9xx) > >I'm sure someone more knowledgeable can correct this if I'm wrong. -------------------- >942$c - defines the type of material the bibliographic record represents, >sort of like it's GMD (general material description). Has no bearing on >circulation of material. Stored as marcxml in biblio_metadata. > >952$y - defines the item-level item, and is used mandatorily for Koha's >circulation rules which work as a permutation of (a) branchcodes (b) patron >categories and (c) item-level item types. Stored as itype column in items >table. > >Hope this helps >Indranil --------------------- >952$y is mandatory for circulation IF item-level_itypes is set to "specific >item". Otherwise, 942$c is used as the item type for circulation. > >Another thing that I have observed about 942$c is that it is indexed for the >search in the same way as 952$y. So if you have records without items (for >journal articles, websites or ebooks for example), these will still be >searchable through the item type filter. > >Also, if 942$c and 952$y are not the same in one record (for example, 942$c is >Book and 952$y is Reference), they will show in the results of a search for >either type. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 22839] New: Manual screenshots and description in Acquisition (Funds) are outdated
by bugzilla-daemon＠bugs.koha-community.org 11 May '23

11 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22839 Bug ID: 22839 Summary: Manual screenshots and description in Acquisition (Funds) are outdated Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: christian.stelzenmueller(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- The screenshots and the text ("To see all active funds you can click the checkbox next to ‘Show active and inactive’ above the funds table.") in the Manual for the funds in the section Acquisitions are outdated. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 29431] New: Hold queue does not consider expiration date
by bugzilla-daemon＠bugs.koha-community.org 11 May '23

11 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29431 Bug ID: 29431 Summary: Hold queue does not consider expiration date Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The holds queue does not take a hold expiration date into consideration. If a hold has an expiration date, the title will show on the queue as needed to be pulled, and when staff check it in, the hold is expired. For libraries that do not auto expire waiting holds, this is a problem. If a hold has an expiration date prior to the current date, it should not show as needing to be pulled, or have some sort of indicator the expiration date of the hold is passed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 27638] New: Allow exclusions on cancel_expired_holds
by bugzilla-daemon＠bugs.koha-community.org 10 May '23

10 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27638 Bug ID: 27638 Summary: Allow exclusions on cancel_expired_holds 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 It would be good to be able to exclude groups of holds from the cancel_expired_holds cron. Ideally, this would allow exclusion based on library, patron category, and/or item type. Ideally it would be set/edited from the staff client rather than the commandline. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 20751] New: Marc21: Show i for 776
by bugzilla-daemon＠bugs.koha-community.org 10 May '23

10 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20751 Bug ID: 20751 Summary: Marc21: Show i for 776 Change sponsored?: --- Product: Koha Version: 17.11 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 In 17.11 the marc21 776 field ( [15140] Add MARC21 776 to OPAC and staff display ) became visible in the OPAC and staff client. This was specifically for subfield $t and $w. It would be great if the $i could also be visible. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 26932] New: Importing staged bibliographic MARC records does not show a completed status if there are any item records to stage
by bugzilla-daemon＠bugs.koha-community.org 10 May '23

10 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26932 Bug ID: 26932 Summary: Importing staged bibliographic MARC records does not show a completed status if there are any item records to stage Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Created attachment 113025 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=113025&action=e… MARC with no item records Important: imported does WORK but the completed message never shows. It just hangs on 0% when importing. However if you give it some time and do a search, the imported record shows in search results. We see the completed message if importing a staged record that has no item records. We do NOT see the completed message if importing a staged record that DOES have item records. I've attached two sample records to test with. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6