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

[Bug 29268] New: Query used in Koha::Biblio->get_marc_host is incorrect
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '25

07 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29268 Bug ID: 29268 Summary: Query used in Koha::Biblio->get_marc_host is incorrect Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org After digging through this some more in relation to bug 27507 and bug 11175 I have come to the conclusion that I think the searches performed by get_marc_host are too simplistic/incorrect. First of all, both the 773 field and $w subfield are repeatable.. so we need to iterate for subfields as well as the field. Secondly, I don't think the search for (RCI)CN is correct.. this is what would appear in the 773 of the child, not how the 001 would be constructed in the host. What I believe we really need to do is as follows: 1. Iterate through 773 fields. 2. Iterate through subfield w's and looks for one of the following: 1a. (RCI)Controlnumber where the RCI matches the OrgCode syspref 1b. Fully numeric Controlnumber 3. Once we've found the form we're expecting from above iterations (1a in preference to 1b if both exist) jump out of the loops. 3. Produce the search string 'control-number=Controlnumber' for 1b. or `control-number=Controlnumber AND rci=RCI` if 1a is found. It may also be helpful to add the `OR control-number=Controlnumber` search to 1a to account for cases where OrgCode was added to new children but was is missing from the host? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 19859] New: Add option to return to the search result in authorities
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '25

07 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19859 Bug ID: 19859 Summary: Add option to return to the search result in authorities 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: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, It is imposible to return to hte result search when you edit an authorities in a record. When we want to edit an authorities in a record, we can clic on the tag editor. That option will open a search page. In this search page you can search authorities. If you clic on edit authorities that action will be open into the authorities module. If you clic on save, you stay in authorities module and you don't return on the search page of the tag editor. Because of that, if you had made some changes in the authoritie, you can't clic on choose for linking to the record. To recreate: Go to a record Edit an authoritie with tag editor Search an authoritie with this plugin Choose an authoritie and clic on edit authorities Clic on Save Notice that you still in the authorities modul and you can’t link this authoritie in your record. For make this link you have to "go back" two times ank clic on choose or make this search another time. Patrick. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 18595] New: Move C4::Members::Messaging to Koha namespace
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '25

06 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18595 Bug ID: 18595 Summary: Move C4::Members::Messaging to Koha namespace Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Bug 17499 adds Koha-objects for messaging preferences. -- You are receiving this mail because: You are watching all bug changes.

1 159

[Bug 36454] New: Staff - Provide indication if a patron is expired when creating an ILL request
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '25

06 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36454 Bug ID: 36454 Summary: Staff - Provide indication if a patron is expired when creating an ILL request Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com CC: katrin.fischer(a)bsz-bw.de, martin.renvoize(a)ptfs-europe.com, nick(a)bywatersolutions.com, pedro.amorim(a)ptfs-europe.com, rebecca.bradshaw(a)nnuh.nhs.uk, tomascohen(a)gmail.com Creating an ILL request, when staff adds a patron, there is no indication that the patron is expired, if said patron is indeed expired. Part of the problem tackling this, I believe, is that the 'create form' is ILL backend specific, so this should be tackled at each ILL backend level. Having said that, with bug 35570 in the pipeline, we could perhaps consider adding this little enhancement as a follow-up to that. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 47

[Bug 36117] New: Can svc/bib_profile be removed?
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '25

06 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36117 Bug ID: 36117 Summary: Can svc/bib_profile be removed? Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Is this used? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 25323] New: Patrons can act as their own guarantor
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '25

03 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25323 Bug ID: 25323 Summary: Patrons can act as their own guarantor 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: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When searching for a patron to act as a guarantor, if the guarantee's record is returned it can be selected, therefore becoming his/her's own guarantor. This makes no sense. To reproduce: 1) Create two users, a parent and a child both with the same surname (for example Parent Smith and Child Smith) 2) Edit the child record and under the Guarantor information, use the "Search to add" button to search for a guarantor. 3) Search for Smith. Both Parent Smith and Child Smith will be listed in the results. 4) Select Child Smith and save the user record. Child Smith is now the guarantor for Child Smith. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 26024] New: Purge undone of zebraqueue in cleanup_database.pl
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26024 Bug ID: 26024 Summary: Purge undone of zebraqueue in cleanup_database.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com Purge script misc/cronjobs/cleanup_database.pl with --zebraqueue DAYS will delete entries from zebraqueue table with done=1 We now start to use Elasticsearch only so entries of zebraqueue with done=0 stay in database. I propose we purge all entries in cleanup_database.pl. Even with zebra, if indexing does not occur after several days (30 by default), there is a problem and one need a full rebuild. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 32168] New: Editing date/datetime fields without the dateaccessioned.pl plugin can cause errors
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32168 Bug ID: 32168 Summary: Editing date/datetime fields without the dateaccessioned.pl plugin can cause errors Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When editing items that are date or datetime formatted without the dateaccessioned cataloging plugin it is quite easy to cause an error. To recreate: 1. Make sure some 952 field with dates (datelastseen, dateaccessioned ) are visible in the editor but make sure the dateaccessiond plugin is turned off. 2. Set the date format system preference to mm/dd/yyyy 3. Edit an item and attempt to edit one of the date fields to something in the correct dateformat, like 11/11/2018. 4. You get an error as Koha is expecting the SQL date type format of YYYY-MM-DD. I'm not sure how to best solve this. My first thought is that we should require the dateaccessioned.pl plugin on date fields. Or we could add a hint about format? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 20954] New: Add ability to set syspref overrides in SIP as we can in apache
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '25

02 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20954 Bug ID: 20954 Summary: Add ability to set syspref overrides in SIP as we can in apache 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com We should be able to set system preference overrides for SIP in a similar manner that we do in Apache. It would be great if we could specify those overrides on both a config level, and login level basis. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 32782] New: UNIMARC support
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '24

29 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32782 Bug ID: 32782 Summary: UNIMARC support Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major 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: 32030 I need UNIMARC equivalence for the following values: my $publication_title = $biblio->title; my $print_identifier = $record->subfield( '020', 'a' ) || $record->subfield( '020', 'z' ) || $record->subfield( '022', 'a' ) || $record->subfield( '022', 'y' ); my $online_identifier = $print_identifier; my ( $date_first_issue_online, $date_last_issue_online ) = $fix_coverage->( $record->subfield( '866', 'a' ) ); my ( $num_first_vol_online, $num_last_vol_online ) = $fix_coverage->( $record->subfield( '863', 'a' ) ); my ( $num_first_issue_online, $num_last_issue_online ) = ( '', '' ); # FIXME ? my $title_url = $record->subfield( '856', 'u' ); my $first_author = $biblio->author; my $embargo_info = ''; # FIXME ? my $coverage_depth = $title_url ? 'fulltext' : 'print'; my $notes = $record->subfield( '852', 'z' ); my $publisher_name = $record->subfield( '260', 'b' ); my $publication_type = ''; # FIXME ? my $date_monograph_published_print = ''; # FIXME ? my $date_monograph_published_online = ''; # FIXME ? my $monograph_volume = ''; # FIXME ? my $monograph_edition = ''; # FIXME ? my $first_editor = ''; # FIXME ? my $parent_publication_title_id = ''; # FIXME ? my $preceeding_publication_title_id = ''; # FIXME ? my $access_type = ''; # FIXME ? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32030 [Bug 32030] Electronic resource management (ERM) -- You are receiving this mail because: You are watching all bug changes.

1 26