Currently there is an inconsistency with the level at which `WhenLostChargeReplacementFee` and `WhenLostForgiveFine` can be set when compared to the complimentary `RefundLostOnReturn` rule. For consortial installations, all these rules should apply at the same level, be that system or branch level.. I propose to move the two 'system' level preferences into 'branch' level by migrating them into the circulation rules area.
Good idea! Moving them onto the circ rule page will make them easier to find and making them customizable per branch would make lots of folks happy.
+1
+1 I reckon this function is sought after for a lot of libraries. In fact, one of our clients asked about excluding certain item types from this preference. Hence, it would be optimal to include it the main circulationmatrix so it can be customizable based on branch, patron category and item type.