Enable API update of patron records to blank out expiry date
Sometimes we want to update a patron record and blank out a date in the expiry date field for a continuing staff member.
The patron API cannot do this - blank values are rejected as invalid JSON e.g.
{"expirationDate": " - - "}
{"expirationDate": ""}
{"expirationDate": "--"}
{"expirationDate": "null"}
All we can do is add a date, and for continuing staff we can only use the maximum possible date of 18 Jan 2038.
Enhance the API to accept a blank value in expiry date.
Bruce Eames
shared this idea
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Pam Skittino
commented
The year 2038 issue has been causing us problems for a few years now (even without the API)
-
Kathy Halloran
commented
We are working with a third party to created digital library cards. Part of the process will verify the identity of the user. If they are verified, we would like the resulting patron record to be created without an expiration date. If the identity can't be verified, we would like those records to have an expiration date.