Bug 12077 - Give superlibrarian ability to remove selected patron fine history.
Summary: Give superlibrarian ability to remove selected patron fine history.
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-11 21:49 UTC by Christopher Brannon
Modified: 2023-07-15 18:45 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2014-04-11 21:49:30 UTC 
Would like to see a way for the superlibrarian to remove line items in patron fine history.  Either through manual manipulation with checkboxes, or through a batch process.  This would be particularly helpful in purging old data.  But in particular, we need a better way to get rid of unwanted credit on a patron account.

Christopher
Comment 1 Katrin Fischer 2020-01-05 13:43:00 UTC 
For the unwanted credit, does the new 'void' and credit related features solve the issue?
Comment 2 Christopher Brannon 2020-06-26 20:17:24 UTC 
(In reply to Katrin Fischer from comment #1)
> For the unwanted credit, does the new 'void' and credit related features
> solve the issue?

No.  We still end up with items we can't resolve on our end of things.  We still end up asking ByWater to remove credits or line items that should not be there.  There are some libraries that are not allowed to fix mistakes with credit, writeoffs or voids.
Comment 3 Katrin Fischer 2023-07-15 18:45:28 UTC 
(In reply to Christopher Brannon from comment #2)
> (In reply to Katrin Fischer from comment #1)
> > For the unwanted credit, does the new 'void' and credit related features
> > solve the issue?
> 
> No.  We still end up with items we can't resolve on our end of things.  We
> still end up asking ByWater to remove credits or line items that should not
> be there.  There are some libraries that are not allowed to fix mistakes
> with credit, writeoffs or voids.

Is this still the case with the work on applying and paying out credits?