Nomeclature and nameing rules

With Lists we have a rule that people put their initials at the front of the list, although between control grouping and list categories, and the general need of the users to name their lists so that their function is clear for their own purposes those are not the most problematic to sort.  Likewise for Output Sets.  Not a lot of people do Scheduled Reports, so again, Control Grouping and filters make those easy enough to navigate, even with three orgs in our Consortium.

Naming Conventions and generally sorting and organizing data has become a big concern of my since we expanded into a consortium.  I had hope that Tessitura Consulting would be able to give us some kind of checklist or recommendation, but they cannot.  I've been building a document of different data items to assess whether they need control grouping, whether they should be partially or wholly shared by consortium members or whether we need naming conventions (a surprising amount of stuff is not control grouped, or is control grouped but still displayed to users regardless of control group in various contexts).

I suspect usage cases do very a bit, but I do thing a properly comprehensive document (mine is still nowhere close) should be possible.  You know, "This is Control Groupable, this is not, this can be organized with Categories/Types/Groups, you should use naming conventions with these in order to split/sort/describe them, in a consortium be sure to" and so on.

With Lists we have a rule that people put their initials at the front of the list, although between control grouping and list categories, and the general need of the users to name their lists so that their function is clear for their own purposes those are not the most problematic to sort.  Likewise for Output Sets.  Not a lot of people do Scheduled Reports, so again, Control Grouping and filters make those easy enough to navigate, even with three orgs in our Consortium.

Naming Conventions and generally sorting and organizing data has become a big concern of my since we expanded into a consortium.  I had hope that Tessitura Consulting would be able to give us some kind of checklist or recommendation, but they cannot.  I've been building a document of different data items to assess whether they need control grouping, whether they should be partially or wholly shared by consortium members or whether we need naming conventions (a surprising amount of stuff is not control grouped, or is control grouped but still displayed to users regardless of control group in various contexts).

I suspect usage cases do very a bit, but I do thing a properly comprehensive document (mine is still nowhere close) should be possible.  You know, "This is Control Groupable, this is not, this can be organized with Categories/Types/Groups, you should use naming conventions with these in order to split/sort/describe them, in a consortium be sure to" and so on.