Nomeclature and nameing rules

My thought is that some of this (having to have naming conventions for lists) is based on constraints from Tessitura as it was many years ago. (I started using Tessitura in 2004.) The real issue is how much do you share lists between users?  If you don't share them, then "most of the time" (won't guarantee all because I haven't checked each one), when there is a report parameter for a list, it will show you YOUR lists first.  This is accomplished by having this in the "order by clause" part of the parameter setup:  CASE WHEN created_by = dbo.fs_user() then 0 ELSE 1 END, list_desc

If you have access to edit report setup, you can see this for both lists and output sets in the "Execute an Output" set report.

And the other part of this is if you click on the chicklet for the list parameter, it will open up the list of lists screen, with the "my lists only" checkbox selected as a default.  (If anyone knows how to change this default, I'm all ears.)  

I'm considering having naming conventions mostly so people don't forget what they created the list for (and we can both tell if they can be inactivated/deleted).  The other option is to use an approach like the one Katie Lachance-Duffy has created to clean up old lists.  Here's a link to that discussion:  https://community.tessituranetwork.com/topical_groups/database-managers-tessitura-community/f/discussions/31892/protocols-for-list-extractions-output-sets/83311#83311

My thought is that some of this (having to have naming conventions for lists) is based on constraints from Tessitura as it was many years ago. (I started using Tessitura in 2004.) The real issue is how much do you share lists between users?  If you don't share them, then "most of the time" (won't guarantee all because I haven't checked each one), when there is a report parameter for a list, it will show you YOUR lists first.  This is accomplished by having this in the "order by clause" part of the parameter setup:  CASE WHEN created_by = dbo.fs_user() then 0 ELSE 1 END, list_desc

If you have access to edit report setup, you can see this for both lists and output sets in the "Execute an Output" set report.

And the other part of this is if you click on the chicklet for the list parameter, it will open up the list of lists screen, with the "my lists only" checkbox selected as a default.  (If anyone knows how to change this default, I'm all ears.)  

I'm considering having naming conventions mostly so people don't forget what they created the list for (and we can both tell if they can be inactivated/deleted).  The other option is to use an approach like the one Katie Lachance-Duffy has created to clean up old lists.  Here's a link to that discussion:  https://community.tessituranetwork.com/topical_groups/database-managers-tessitura-community/f/discussions/31892/protocols-for-list-extractions-output-sets/83311#83311

We are definitely "cleaning up" old LEO as well.

We do "share" lists in that we have a distributed team that are in charge of their own opening night segments. Part of coordinating those huge events is hunting down the many stakeholder lists.  The look up criterion for Lists is limited, and it's be helpful to have some nomenclature that is clear for returning seasons and easy to guess

Thanks for the case statement - that's useful.