[Koha-bugs] [Bug 17621] New: API: Should the 'update_on' Patron field really be a datetime?

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17621

            Bug ID: 17621
           Summary: API: Should the 'update_on' Patron field really be a
                    datetime?
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5 - low
         Component: Web services
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: martin.renvoize at ptfs-europe.com
        QA Contact: testopia at bugs.koha-community.org
                CC: hector.hecaxmmx at gmail.com,
                    jonathan.druart at bugs.koha-community.org,
                    lari.taskula at jns.fi, martin.renvoize at ptfs-europe.com,
                    tomascohen at gmail.com
        Depends on: 16276, 17607
            Blocks: 17620

Bug #17607 highlighted that all other date fields in the Patron response are
simply 'date', whereas update_on is a date-time (without a timezone).

We should assess whether it's actually necessary for the update_on field to
record the timestamp as opposed to just a date, and if it required we should
ensure we record and return the timezone detail along with it.


Referenced Bugs:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16276
[Bug 16276] When automatically deleting expired borrowers, make sure they
didn't log in recently
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17607
[Bug 17607] Fix patron definition in Swagger
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17620
[Bug 17620] Fix format of date/data-times in Swagger definition
-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.