Summary: | MarkLostItemsAsReturned - map to Lost-status instead of context where the transaction took place | ||
---|---|---|---|
Product: | Koha | Reporter: | Klas Blomberg <klas.blomberg> |
Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | bugzilla, george, gmcharlt, holly, jrobb, kyle.m.hall |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Klas Blomberg
2019-04-26 10:05:59 UTC
Would love to see something like this implemented. It makes a lot of sense to tie what a status does to the status itself rather than what page you are on when you apply the status. It'd be great to be able to define or override default behaviors of individual statuses including things like: - Charge replacement price on application? - Check in item on application? - Clear status on check-in? - Allow holds on item with this status? - Hide items with this status in the OPAC? This is still something libraries are interested in, especially if it could open up possibilities for a multiple step process via the longoverdue cron. Example: a library wants to keep long overdue items on patron checkouts, but automatically remove very long overdue items 30 days=long overdue lost 90 days=lost billed MarkLostItemsAsReturned: long overdue lost = no lost billed = yes |