[Koha-bugs] [Bug 34883] New: Regression in Patron Import dateexpiry function
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Fri Sep 22 13:06:38 CEST 2023
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34883
Bug ID: 34883
Summary: Regression in Patron Import dateexpiry function
Change sponsored?: ---
Product: Koha
Version: 22.11
Hardware: All
OS: All
Status: NEW
Severity: minor
Priority: P5 - low
Component: Patrons
Assignee: koha-bugs at lists.koha-community.org
Reporter: jake.deery at ptfs-europe.com
QA Contact: testopia at bugs.koha-community.org
CC: gmcharlt at gmail.com, kyle.m.hall at gmail.com
Hello all,
We are seeing issues in our import_patrons.pl which is causing issue for our
academic customer base.
In versions prior to 22.11, running import_patrons.pl would cause the
dateexpiry to either:
— get set based on the contents of the dateexpiry in the CSV file; or
— get left as the value already in Koha
This worked well for our academics, because they could opt when to update the
dateexpiry rather than sending them over every night (e.g. if a student exited
a course early, they could be expired in the LMS to prevent them from accessing
the services).
In 22.11, the update-expiration and expiration-from-today flags have been added
to the script. I believe the logic behind these flags is to update the
dateexpiry based on enrolment plus user category duration, or today plus user
category duration. This probably works great for most libraries, but it isn't
necessarily desirable for Colleges.
The option still exists to set dateexpiry from the CSV, by not passing the
aforementioned flags. However, the dateexpiry now gets set to the following,
when using this:
— get set based on the contents of the dateexpiry in the CSV file; or
— get left as the value already in Koha
As you can see, this is a clear regression. Could we please look to remediate
this, so I can pass on some good news to our affected customers?
Many thanks,
Jake Deery
PTFS Europe
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
More information about the Koha-bugs
mailing list