Hello! I'm wondering about best practices for list management and overall organization. For long-time users, do you delete old lists that you won't be using again?
We've been on Tessitura for less than 2 years, and it's already getting a bit cumbersome to wade through hundreds of lists, all created for specific purposes (i.e. a pre-show email, or a specific show's target list).
Jean Leonard said:For long-time users, do you delete old lists that you won't be using again?
Years ago we agreed to housekeep lists and exts that haven't been modified and/or promoted in 25+ months. This has worked out well here.
Chris, by "housekeep" do you mean you delete outdated lists, or do you assign them to an archive folder? Curious here since our list manager is pretty cumbersome too. Some of our more manual lists may not have been updated in 25+ months but still get referenced, so I feel I always need to tread a bit lightly.
Michael Buffer said:do you mean you delete outdated lists
Yes. A while ago I ran a trace while I deleted a List and an Ext in the client, and wrote SQL code to match.
Michael Buffer said:or do you assign them to an archive folder?
My code explicitly spares a few from the axe, but if I wanted something more systematic for this, I think I'd set up an exclusion List Category, and advise users to set Lists to that to be sure favorites were spared.
Michael Buffer said:so I feel I always need to tread a bit lightly.
If I wanted to hide some to see if anyone noticed they were missing, without actually deleting them, I'd set them to a sysadmin control group.
Great advice, thanks, Chris!
We don't clear out our lists, but we have quite a structured system for labelling them so it's still easy to sort through.the name of the list is usually DEP YEAR PURPOSE DETAIL. ie, MKT22 eDM pre-concert matinee 1Then its easy to filter by which department made the list, which year it was made, and if it was related to a specific concert :)