Bibliomation's hook is already active, and we have a different granularity set, so we wouldn't want the script to override that.
Not adding a sign-off tag just yet because IF THEN ELSE statements in SQL are new to me, so I'd appreciate a more experienced eyes on it.
Editing to add this has been tested on a 3.9 database with Bibliomation data, and seems to do the job in both scenarios (skip the UPDATE queries if hook is already active, and run the UPDATE queries if not).
Here is a sign-off branch that includes a check to see if the hook is already active, and skips the update if it is:
https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ jwoolford/ lp1705333_ au_created_ passive_ setting_ with_check
Bibliomation's hook is already active, and we have a different granularity set, so we wouldn't want the script to override that.
Not adding a sign-off tag just yet because IF THEN ELSE statements in SQL are new to me, so I'd appreciate a more experienced eyes on it.
Editing to add this has been tested on a 3.9 database with Bibliomation data, and seems to do the job in both scenarios (skip the UPDATE queries if hook is already active, and run the UPDATE queries if not).