Best Practices: List Maintenance & Hygiene

I created a utility a few years ago to manage infrequently used lists. It’s on TASK in the Shared Reports workspace under the name “Manage Lists Utility.”

Here’s the description:

Manages infrequently used lists unless the list is in LTRX_PERMANENT_LISTS.  Options to:

 ·         Inactivate lists that haven’t been used in a given number of days

·         Inactivate lists owned by inactive users. 

·         Delete inactive lists that haven’t been used in a given number of days. 

·         Delete active lists with 0 members or which are in a Testing folder

I schedule the report to run on a monthly basis, and it keeps our consortium’s lists much cleaner. It also makes upgrades a little easier since we can remove deprecated List Manager elements that are no longer used by those one-time-used lists.

~Katie

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of John Moskal II
Sent: Tuesday, December 22, 2015 11:43 AM
To: Catherine Lachance-Duffy
Subject: Re: [Tessitura Technical Forum] Best Practices: List Maintenance & Hygiene

I would also be highly interested in what others are doing here as I really do not have any big ideas in this area and would love some input.

The one thing that I do currently do is to just reuse the same two lists over and over for one time, random pulls.  I call them "Random One Use" and "Random Two Use" and it has kept the number of lists that I personally create down to a minimum since these are merely temporary placeholders (I have been working here for over 5 years and the number of lists that I have created can still fit all onto one screen).  I have two in case I am working on two things at once or need to compare things; the system could easily be modified to include a third placeholder if needed, but thus far I have not needed one.

That said, most of everything that I do involves just random pulls once that I will not ever need again so this system works well for me.  On the other hand, that is just me, and there are hundreds of lists created by other staff members that pay no attention to inactivating and/or deleting them after the fact (my placeholder solution has not yet caught on with the rest of the organization at this point in time).  Thus my interest in this thread.

I created a utility a few years ago to manage infrequently used lists. It’s on TASK in the Shared Reports workspace under the name “Manage Lists Utility.”

Here’s the description:

Manages infrequently used lists unless the list is in LTRX_PERMANENT_LISTS.  Options to:

 ·         Inactivate lists that haven’t been used in a given number of days

·         Inactivate lists owned by inactive users. 

·         Delete inactive lists that haven’t been used in a given number of days. 

·         Delete active lists with 0 members or which are in a Testing folder

I schedule the report to run on a monthly basis, and it keeps our consortium’s lists much cleaner. It also makes upgrades a little easier since we can remove deprecated List Manager elements that are no longer used by those one-time-used lists.

~Katie

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of John Moskal II
Sent: Tuesday, December 22, 2015 11:43 AM
To: Catherine Lachance-Duffy
Subject: Re: [Tessitura Technical Forum] Best Practices: List Maintenance & Hygiene

I would also be highly interested in what others are doing here as I really do not have any big ideas in this area and would love some input.

The one thing that I do currently do is to just reuse the same two lists over and over for one time, random pulls.  I call them "Random One Use" and "Random Two Use" and it has kept the number of lists that I personally create down to a minimum since these are merely temporary placeholders (I have been working here for over 5 years and the number of lists that I have created can still fit all onto one screen).  I have two in case I am working on two things at once or need to compare things; the system could easily be modified to include a third placeholder if needed, but thus far I have not needed one.

That said, most of everything that I do involves just random pulls once that I will not ever need again so this system works well for me.  On the other hand, that is just me, and there are hundreds of lists created by other staff members that pay no attention to inactivating and/or deleting them after the fact (my placeholder solution has not yet caught on with the rest of the organization at this point in time).  Thus my interest in this thread.