Overview of object owner/creator/group state ???

Hi,

Can anyone describe or provide a link to a systematic overview of object owner/creator/group state ?

I'm embarking on setting up administration for my creations and I am considering the concept that admin commands should work for:
- owner
- creator (so I can come to the rescue, hopefully not too often)
- administrators (to cater for more than one person helping to host the system - based on the owner putting admin keys into a notecard)
- groups??? - is it possible to use this

I'm not exactly sure under what circumstances objects & packages of objects could have their owner/creator (groups?) changed? For example can I be sure I would always be the owner of systems I sell? Plus any traps here?

Cheers
Greg

Creator *shouldn't* change - but does sometimes, mainly after odd crashes. It's unpredictable for objects, although more predictable for skins - you need to select make new body part from the right click menu to have yourself listed as the creator. You can, of course, hard code your access by your name/key rather than relying on llGetCreator() which will save a bit of memory and avoid the issue.

Owner reflects the current owner (or group if deeded to a group) I can 100% guarantee that if you sell it (except to yourself) you'll no longer be the owner.

Groups - objects rezzed by default belong to the group you're in when you rez them. You can change that through the general tab in edit and set group. If you're an officer you can also deed the object to the group - that means the group becomes the official owner. People can (possibly only officers?) take deeded objects back into inventory and rerez them without them being group deeded any more - although it's possible this is not expected behaviour.

Hope that covers what you want.

Thanks Eloise - helped me out - also Googled and got this link which helped too. So it would seem best not to rely on creator as one point.

In terms of a mechanism to identify administrators for systems, what do people generally do, and in particular would use of groups be a good option? (i.e. instead of editing a notecard). I'm thinking the notecard approach may in fact be easier and less prone to error, plus there would need to be a notecard setting for the group name anyway (i.e. if you sell 10 versions of the same system each owner would need to setup their own group).

Cheers
Greg