Bug 22780 - MarkLostItemsAsReturned - map to Lost-status instead of context where the transaction took place
Summary: MarkLostItemsAsReturned - map to Lost-status instead of context where the tra...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-26 10:05 UTC by Klas Blomberg
Modified: 2023-09-22 19:37 UTC (History)
5 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Klas Blomberg 2019-04-26 10:05:59 UTC
Syspref MarkLostItemsAsReturned is mapped to the context where you make the transaction - Holds to pull list, longoverdue cronjob et.c.
I can't see any logical reason for this!

I think it would be better to map to Lost-statuses:
Lost = don't mark as returned
Longoverdue = don't mark as returned
Lost and paid for = mark as returned
et.c.
Comment 1 Jason Robb 2023-06-29 17:49:05 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?