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.
A few Ideas on this exist, but I've added a more comprehensive one (including links to the others):
community.tessituranetwork.com/.../better-management-for-old-lists-and-extractions-segmentations-and-output-sets