Open kaligrafy opened 1 week ago
For the admin user, do we want to put some role, because right now admin is too broad of a type ?
For the admin user, do we want to put some role, because right now admin is too broad of a type ?
Yes we do, eventually, none of us should be admin, but we should all have permissions of some kind. We have all the framework for this and we have interviewer/validator roles, but we stopped there as it was enough at the time and didn't get time to work on it...
Sounds good for the renaming. But is that exhaustive enough? What about the case of somebody visualizing the audits (in the summary
page) and just setting the interview as valid/invalid, complete/incomplete, questionable? This process does not require correction and we may not want all users who can do that to actually have the permission to correct the interview?
You think of OD surveys, but there are many others where we may just want to manually [in]validate them without giving right to edit.
I think we can still do better renaming and separating users/permissions
Roles/permissions and renaming are 2 separate things anyway.
New proposition:
interview Base process for all interview types
a. respondentInterview
b. assistedInterview
realTimeValidation
audit (process) & auditReport (group of results) & auditResult (single result) & auditCheck (single validation/check)
review (manual)
correction (manual)
enhancement (automated)
respondent
interviewer
auditor (system role)
reviewer
corrector
admin
interview
├── respondentInterview (respondent)
│ └── realTimeValidation
└── assistedInterview (interviewer)
└── realTimeValidation
system-auditor
└── audit
└── auditReport
reviewer
└── review
corrector
└── correction
└── realTimeValidation
admin
└── monitoring
└── export
@tahini Waiting for our review :-)
Proposition for renaming classes, attributes and actions, plus users categories:
Naming conventions
Interview manipulation by use case:
Users:
Please discuss if you agree, and if not, propose better (If you don't like a name, propose a better one :-) )