Bug 39419 - Holds API treats 'expiration_date' as 'patron_expiration_date'
Summary: Holds API treats 'expiration_date' as 'patron_expiration_date'
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-21 19:40 UTC by Nick Clemens (kidclamp)
Modified: 2025-04-09 09:10 UTC (History)
3 users (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Clemens (kidclamp) 2025-03-21 19:40:13 UTC
This is going to have a related issue in Aspen, but I think the confusion starts here

Koha has two fields for hold expiration:
expirationdate - (usually) auto generated date set based no when holds on the shelf expire
patron_exiration_date  - the day the patron says they don't need the hold after

The API takes "expiration_date" and maps it to "patron_expiration_date"

This can be unclear for outside systems.

Aspen has a 'Default Not Needed After Days' setting which is assumed to be setting the automatic expiraton date, but in fact sets the patron date

We should allow either field to be set via the API
Comment 1 Nick Clemens (kidclamp) 2025-03-21 19:43:32 UTC
Aspen bug report: https://aspen-discovery.atlassian.net/browse/DIS-537