Thanks for testing Michele, and for pointing out about the upgrade issue. After discussing, Mike will work on a change that should preserve customizations and follow what was called for in the spec anyway:
"During upgrade, if the Action Trigger Event Definitions for the biblio.format.record_entry.print or biblio.format.record_entry.email hooks exactly match stock seed data from previous versions of Evergreen, they will be completely replaced by the new Event Definition Group, Group Member, and Event Definitions seed data.
Otherwise, existing biblio.format.record_entry.print and biblio.format.record_entry.email Event Definitions will become members of new Event Definition Groups as "Brief" Members, with ownership of each Event Definition Groups set to match those of the converted Event Definitions. The converted Event Definition Group Members will not have the sortable flag set. The upgrade will then add a new Full Member to each of the new Event Definition Groups."
Thanks for testing Michele, and for pointing out about the upgrade issue. After discussing, Mike will work on a change that should preserve customizations and follow what was called for in the spec anyway:
"During upgrade, if the Action Trigger Event Definitions for the biblio. format. record_ entry.print or biblio. format. record_ entry.email hooks exactly match stock seed data from previous versions of Evergreen, they will be completely replaced by the new Event Definition Group, Group Member, and Event Definitions seed data.
Otherwise, existing biblio. format. record_ entry.print and biblio. format. record_ entry.email Event Definitions will become members of new Event Definition Groups as "Brief" Members, with ownership of each Event Definition Groups set to match those of the converted Event Definitions. The converted Event Definition Group Members will not have the sortable flag set. The upgrade will then add a new Full Member to each of the new Event Definition Groups."