Hi folks,
Do you have naming rules for your LEO (Lists/Extractions/Output Sets)? Wordly emails and pages? Scheduled reports?
If you do what are they and how are you enforcing these?
Enquiring minds need to know.
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.
I agree, it would be great to have a longer list name and a description field. On the ideas board there is one for adding a description field to notes. You can go here to upvote the idea:
https://community.tessituranetwork.com/ideas/i/ideas/add-a-description-or-notes-field-to-lists
T.C.
I'm late to the party on this one, but while our consortium maintains naming conventions in most parts of the system, this is one area where we let users go wild and name lists, extractions, output sets, and scheduled reports in any manner that works for them. (Our consortium members may have internal naming rules for their LEO if they wish, of course.)
This approach works for us because, as Carol mentioned, we regularly maintain the LEO & scheduled reports, inactivating unused ones, deleting inactive ones after a certain period of time, etc.