Happy New Year everyone.
Our consortium has been on Tessitura for 18 years and lots of lists, extractions, and output sets (l/e/o) have been created by users at the various organizations during that time. Occasionally there has been some cleanup done by users, but many of the l/e/o remain in the system with a portion of those created by users who no longer work in the consortium. We have asked users to clean up and delete any old l/e/o, but we want to establish some clear guidelines for how long these are kept and have a regular procedure in place to reduce the number of outdated l/e/o.
At the Database Managers’ meeting last month, I posed this question and got some great feedback, such as having time limits for how long l/e/o are kept with periodic review (such as end of FY), naming conventions to easily identify evergreen items, reassigning l/e/o when a person leaves an organization. I also wanted to hear what others are doing to keep l/e/o from getting out of hand and if anyone has policies/guidelines in place.
Appreciate any feedback.
T.C.
So our l/e/o ( ) are a bit out of hand. We have a current project with the super user group that is
There are somethings that are business critical that we're putting a saftey fence around, and to be honest we need to back up the logic behind those things for safety
Part of our ongoing Data Strat's Hygiene plan is an annual LEO maintenance
Also that's a great point re: Nomenclature
The way I've dealt with the "save" ones in the past is to create a folder called "KEEP" or "MISSION CRITICAL" (or however you refer to them). If someone wants it saved, it's their responsibility to move them to that folder. Anything not in that folder is subject to the delete/deactivate rules. Also, I would check via SQL before doing the Delete/Deactivate to make sure the list wasn't referred to in another list or extraction. And if an output set was only referred to in a deleted/deactivated list, it could also be removed.