Hello PaILS/SPARK is on 3.13 since November and we have not seen any issues with the mark item lost triggers or staff having the ability to mark items as lost. I will note that all of our circulation permission groups have this permission set at the Consortium level so that they can mark items outside their org units as lost to help facilitate resource sharing. The two permissions are: MARK_ITEM_LOST- According to the permissions working groups' testing notes this one doesn't seem to do anything. SET_CIRC_LOST- According to the same notes, this one seems to be the one that actually allows a user to mark an item as lost [cid:8130e881-7eed-46f5-8090-009595ad8294]Elizabeth Davis (she/her), Program Manager Pennsylvania Integrated Library System (PaILS) | SPARK (717) 256-1627 | elizabeth.davis@sparkpa.org<mailto:katherine.dannehl@sparkpa.org> support.sparkpa.org<https://support.sparkpa.org/> | support@sparkpa.org<mailto:support@sparkpa.org> ________________________________ From: Evergreen-general <evergreen-general-bounces@list.evergreen-ils.org> on behalf of Morgan, Michele via Evergreen-general <evergreen-general@list.evergreen-ils.org> Sent: Monday, February 24, 2025 12:19 PM To: Evergreen Discussion Group <evergreen-general@list.evergreen-ils.org> Cc: Morgan, Michele <mmorgan@noblenet.org> Subject: Re: [Evergreen-general] hoping for collective insight regarding problems with lost status after upgrade Hi Beth, Like Terran, we do not have action triggers that mark items Lost, but we do mark items Long Overdue via trigger. We are on 3.13 and the triggers have been running fine. I tested marking an item Lost from a patron's Items Out tab on our 3.13 test system and it also worked as expected. I would tend to agree with Terran that it could be a permissions issue. Bug 2018491<https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.launchpad.net_evergreen_-2Bbug_2018491&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=j4SWsMDXRVOGlMb-EfMRIp9IjAos-OG-ewOKBUjTNh8&m=E3zAA_EElenxmlzF8CYJYTPXyL4KhWmO9ZPtkvor-YWnsumuQ1ria_5lax_M--8N&s=8o6dhyBVAlWiDSxB_SPB8dcxwyl2TR4lmyXDADhHung&e=> tightened permissions on items, so it could be that staff permissions need to be adjusted. For the Mark Lost action triggers, I would recommend checking the triggers' Parameters. The trigger should have an 'editor' parameter, the value should be the database id of a user who has permission to update items. Hope this is helpful! Michele -- Michele M. Morgan, Systems Support Specialist North of Boston Library Exchange, Danvers Massachusetts mmorgan@noblenet.org<mailto:mmorgan@noblenet.org> On Thu, Feb 20, 2025 at 4:53 PM Terran McCanna via Evergreen-general <evergreen-general@list.evergreen-ils.org<mailto:evergreen-general@list.evergreen-ils.org>> wrote: We don't mark this Lost through an action trigger (we just do Long Overdue) but we do it manually and haven't had any problems. Perhaps there was a permissions change between those two versions that you need to apply? Are you seeing any useful errors in the browser console log? On Thu, Feb 20, 2025 at 2:41 PM Beth Longwell via Evergreen-general <evergreen-general@list.evergreen-ils.org<mailto:evergreen-general@list.evergreen-ils.org>> wrote: Fellow Evergreen users, We upgraded from 3.7 to 3.13 in January and since then are not able to mark things lost manually (action does nothing) and action-trigger jobs to mark items lost end in error. The fact that others are not experiencing this (to our knowledge), I'm left wondering if it is a system configuration issue on our end. Have any of you experienced anything like this? Are any of you using action-triggers to mark items long overdue after x number of days and then marking it lost after another x number of days? Thanks in advance for any ideas or insight you can provide. Beth Ross Systems Manager Sage Library System _______________________________________________ Evergreen-general mailing list Evergreen-general@list.evergreen-ils.org<mailto:Evergreen-general@list.evergreen-ils.org> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general<https://urldefense.proofpoint.com/v2/url?u=http-3A__list.evergreen-2Dils.org_cgi-2Dbin_mailman_listinfo_evergreen-2Dgeneral&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=j4SWsMDXRVOGlMb-EfMRIp9IjAos-OG-ewOKBUjTNh8&m=E3zAA_EElenxmlzF8CYJYTPXyL4KhWmO9ZPtkvor-YWnsumuQ1ria_5lax_M--8N&s=J-UkfGsxUfZIaBu99ZTIlqNg8_5R-J2ZR7k12i8_F5k&e=> _______________________________________________ Evergreen-general mailing list Evergreen-general@list.evergreen-ils.org<mailto:Evergreen-general@list.evergreen-ils.org> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general<https://urldefense.proofpoint.com/v2/url?u=http-3A__list.evergreen-2Dils.org_cgi-2Dbin_mailman_listinfo_evergreen-2Dgeneral&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=j4SWsMDXRVOGlMb-EfMRIp9IjAos-OG-ewOKBUjTNh8&m=E3zAA_EElenxmlzF8CYJYTPXyL4KhWmO9ZPtkvor-YWnsumuQ1ria_5lax_M--8N&s=J-UkfGsxUfZIaBu99ZTIlqNg8_5R-J2ZR7k12i8_F5k&e=>
