Standardisation of naming practices for getter/setter functions

[helenginn]

I'll start this issue as a comment thread to highlight instances where the naming practice isn't standardised for methods/functions which follow a similar theme. It doesn't really matter too much what the standard is, as long as the functions follow the same naming protocol.

Generally naming protocols should follow these rules:

• methods involving an object type always has the same name for the object (ideally without abbreviation unless the name gets ridiculously long) - e.g. ModelDataPair (preferred) over MDP, not to be interchanged with the "hidden" concept of CollectionHasDataset or CHD.
• Getter functions either always start with get or never start with get (as long as its consistent)
• Setter functions always start with set
• Functions that deliver the size or a count of something always follow the same naming practice, e.g. for a given Object, we have objectSize() or numObjects() or objectCount() and this format is used throughout all the mulch code.
• • Perhaps you need to distinguish between counts of something from the database, so for example to know how many Collections you have, you'd have another name databaseObjectCount, for example for getting the total number of collections.

[helenginn]

In Collection.h we have a lot of size-based naming discrepancies, such as getCHDsVectorSize(), countChdIds() (there should only be one of these?).

• and getCountPids which doesn't specify an object that I'm counting.