Itamar Tzadok

I'm happily not trying to convince anyone in anything. I'm not against the whole thing. I'm just offering another perspective while taking a break from improving my plugins so that I will actually want them. Whatever makes us happy.

And with that ability comes also the ability for a moderator to not remove (and even add) blatantly pr-itory ratings. And who will moderate the moderators?

Can only submit 1 entry (new, no-repeat)

set max-entries to 1.

Edit certain fields in the entry

Not possible in the Database module.

In the Dataform you can add multiple views with different subsets of fields and make some views unavailable to participants. Participants could have a simplified view which displays only the fields they are allowed to edit. Managers would have another view with all the fields. Denying editing of some fields is also possible by setting the number of edits of the field to 0, in which case the field won't be editable for a participant while editing the entry.

Participants can view only their entry

In the Database module enable require approval and don't approve anything. This of course will prevent you from using the approve tag for approving entries for 'office use only'.

In the Dataform you can achieve the 'view own entry only' effect by a designated 'group mode' called 'separate participant'. You are then free to use the approve tag for internal purposes.

Notes

With the entry comments as the natural candidate feature for this behavior.

Afaict, not possible in the Database module if you don't want participants to see the comment, because if you enable comments they will be accesible to the participant.

Possible in the Dataform by adding the comments only in the managers' view(s).

Alternately, you could use the Moodle Notes engine. You don't have actitvity context there, so the notes are not specific to this Database/Dataform activity. But depending on your detailed requirement it could still work for you with the notes in the course or site (or manager) context.

Revoking

By unapproving and approved entry.

hth

b/c it was just a namespace for the object in the array of records returned from your sql query. You should be able to see a userid column in data_records. That's the user id of the entry author. Isn't that what you are looking for?