Group list building

Hi

Is there a way to create a list that all users from a specific user group could edit without making everyone a manager of the group (that would give too many permissions most users don't need)? 

Back story - we have an attribute for a set of patrons (donors, subs and those with certain constituencies) that grants them access to our streaming library. The attribute is maintained using a list and the Manage Attributes utility that is scheduled to run nightly.  Our Box Office also uses access to the streaming library as a service recovery item. The problem we are running into is that they can add the attribute, but it gets erased nightly because the patrons they are giving it to do not meet the list criteria (the utility is set to "Delete All, Add to list only" so that patrons who no longer qualify fall off). My thought is to have a manual list that Box Office staff can add/delete the patrons they are giving the attribute to manually and I can reference that list in the list I use to assign the attribute. 

Thanks
Jess Levy
San Francisco Opera

Parents
  • Jess,

    Not exactly what you were asking, but a semi-similar solution that occurs to me is if you could instead simply create a separate folder for these lists.  Then, either manually edit the SQL for your attribute list or else create a sort of custom list manager element for list folders (off the top of my head I am not certain that can be done, but I have done some pretty creative things there, so maybe).  Worst case scenario, you could create a custom list element that references a custom view that simply links list_no, customer_no and list_category (I think that is what the database calls the different list folders).  But that would allow each Box Office member to maintain their own list (and it would not matter if they duplicated between them) and still accomplish your goal.

    Hope that helps, or at least inspires a different solution!

    John

Reply
  • Jess,

    Not exactly what you were asking, but a semi-similar solution that occurs to me is if you could instead simply create a separate folder for these lists.  Then, either manually edit the SQL for your attribute list or else create a sort of custom list manager element for list folders (off the top of my head I am not certain that can be done, but I have done some pretty creative things there, so maybe).  Worst case scenario, you could create a custom list element that references a custom view that simply links list_no, customer_no and list_category (I think that is what the database calls the different list folders).  But that would allow each Box Office member to maintain their own list (and it would not matter if they duplicated between them) and still accomplish your goal.

    Hope that helps, or at least inspires a different solution!

    John

Children
No Data