Lost billing amounts should be more configurable

[Dan Wells]

When an item is marked lost, the user is typically billed for the item. In Evergreen, they can either be charged the amount recorded in the item object, or if that value is blank (or zero), charged a default price (controlled by settings).

Our library averages out the cost and charges a flat rate of $50.00, an option not currently possible without mass-altering our item records.

Code is in progress.

[Dan Wells (dbw2)]

Branch for review:

working/user/dbwells/min_max_item_pricing

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbwells/min_max_item_pricing

[Remington Steed (rjs7)]

Added one commit for release notes. That makes two commits total. I also rebased to master and fixed one merge conflict in the data seed values file.

working/user/rsteed/min_max_item_pricing

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/rsteed/min_max_item_pricing

[Dan Wells (dbw2)]

Since (in retrospect) it wasn't obvious what my branch does if you only look here, here's the commit message:

In addition to a 'default' price when price is missing or zero, we can also accommodate a range of prices by saying it should be at least 'X' and not more than 'Y'. This also allows you to effectively set a fixed price for all lost items by setting min and max to an equal amount.

[Jeff Godin (jgodin)]

Looks good, and has recently come up in conversation on IRC as another library had need of this feature.

I'll try to get this tested and possibly in master sometime this weekend.

[Jeff Godin (jgodin)]

Rebased against current master to resolve minor conflicts due to other permissions being added, stamped upgrade script as 0854 and bumped all permission IDs as needed.

Cherry picked with signoff and pushed to master.

Thanks, Dan, Remington, Calvin!