Forum OpenACS Development: What were the contents of priv_email, priv_name etc.?
1... nobody should see it except admins
3... registered users
Is that correct? I couldn't find anything on the web where the semantics of these columns are explained.
Tillmann: Since we've never honored them, I don't think it matter what they might have once stood for. Let's figure out what we want them to mean, and do it for the first release possible (given resources).
I think we'll want something along this axis:
- never show
- show to registered users
- show to other members of this subsite
- show to admins
- never show
perhaps eliminating a few of them.
So these were the initial semantics:
0 means "show to everybody"
5 means "show to other registered users"
9 means "show to nobody except maintainers"
Lars: yeah I don't say we have to copy them, I was just looking for inspiration, assuming that there might have gone some thought into it by aD already.
I think 'never show' and 'show to admins' is redundant, at least if you mean site-wide admins, since those could always look into the db directly anyway. 'Show to other members of subsite' makes a lot of sense though - I wonder if 'show to admins of subsite' would be needed too.
I think assigning it integers with some gaps in it for future or site-specific extensions would be good, as well as making it scalar (is that the correct word?) so that higher values always mean more restricted, with 0 as lowest value 'show to all', so that comparisons like $priv_email>$privacy_threshold will always work regardless of later extensions.
May I suggest one more level of privacy: "show only to co-member", with "co-member" I mean one who is a member of at least one group in which I'm a member too.
But I think the initial thought behind the numbering scheme was that sites could insert their custom privacy levels if they wanted to, and if the display proc would be nicely centralised then that would be easy.
Apart from that - what level of group/subgroup membership do you mean? All users of a site are part of the same group - Registered Users - for example, which would make the privacy level useless.
The level of groups I was thinking of, is clubs or classes as in a .lrn environment. I don't know how this could be implemented, I'm not familiar with openacs4 API and data-model. At Uned, we have a acs3 site in which we configured this privacy level so students may share their personal data (email, address, phone, etc.) only with their classmates. Also, the privacy level chosen for email can be different then the one chosen for address or phone.