One reorders the updates to the circulation and copy objects in O::A::Cat::AssetCommon->set_item_lost_or_lod to get around the stop_fines trigger on action.circulation updating the copy.
The second alters the acp_status_changed trigger on asset.copy to only fire if the old record's status_changed_time is null or equal to the status_changed_time in the new record. That should have no unforeseen consequences, right? ;)
Added a couple of commits to the rebase branch.
One reorders the updates to the circulation and copy objects in O::A::Cat: :AssetCommon- >set_item_ lost_or_ lod to get around the stop_fines trigger on action.circulation updating the copy.
The second alters the acp_status_changed trigger on asset.copy to only fire if the old record's status_changed_time is null or equal to the status_changed_time in the new record. That should have no unforeseen consequences, right? ;)