You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 25
Next »
TermPortal app have a number of roles, that affect both client app and server app capabilities. Currently TermPortal have 6 roles, but basically they can be divided into 3 types.
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IlBhdmVsIFBlcm1pbm92Iiwib3V0cHV0VHlwZSI6ImJsb2NrIiwibGFzdE1vZGlmaWVyTmFtZSI6IlBhdmVsIFBlcm1pbm92IiwibGFuZ3VhZ2UiOiJlbiIsImRpYWdyYW1EaXNwbGF5TmFtZSI6IiIsInNGaWxlSWQiOiIiLCJhdHRJZCI6IjM1MTgzMDAyOCIsImRpYWdyYW1OYW1lIjoiUm9sZXMiLCJhc3BlY3QiOiIiLCJsaW5rcyI6ImF1dG8iLCJjZW9OYW1lIjoiVXNlciByb2xlcyIsInRic3R5bGUiOiJ0b3AiLCJjYW5Db21tZW50IjpmYWxzZSwiZGlhZ3JhbVVybCI6IiIsImNzdkZpbGVVcmwiOiIiLCJib3JkZXIiOnRydWUsIm1heFNjYWxlIjoiMSIsIm93bmluZ1BhZ2VJZCI6MzUxODMwMDIzLCJlZGl0YWJsZSI6ZmFsc2UsImNlb0lkIjozNTIyNTYwMjMsInBhZ2VJZCI6IiIsImxib3giOnRydWUsInNlcnZlckNvbmZpZyI6eyJlbWFpbHByZXZpZXciOiIxIn0sIm9kcml2ZUlkIjoiIiwicmV2aXNpb24iOjMsIm1hY3JvSWQiOiI1ODhjY2QzMS1kM2NjLTQ2NjUtOWM4MS0xNjM2MjQzODU1YzMiLCJwcmV2aWV3TmFtZSI6IlJvbGVzLnBuZyIsImxpY2Vuc2VTdGF0dXMiOiJPSyIsInNlcnZpY2UiOiIiLCJpc1RlbXBsYXRlIjoiIiwid2lkdGgiOiIzNjEiLCJzaW1wbGVWaWV3ZXIiOmZhbHNlLCJsYXN0TW9kaWZpZWQiOjE2NTI3NjUyMzkwMDAsImV4Y2VlZFBhZ2VXaWR0aCI6ZmFsc2UsIm9DbGllbnRJZCI6IiJ9
|
Roles
| Write rights on |
|---|
| Term | Attribute |
| create | update | delete | create | update | delete |
| Type 1 | termSearch | No | No | No | No | No | No |
Type 2 | termProposer | Yes | Yes if 1 | Yes | Yes if 4 |
| termReviewer | No | Yes if 2 | No | No | Yes if 5 |
| termFinalizer | No | Yes if 3 | No | No | Yes if 6 |
| Type 3 | termPM | Yes | Yes | Yes | Yes | Yes | Yes |
| termPM_allClients | Yes | Yes | Yes | Yes | Yes | Yes |
Note that processStatus attribute has a special meaning and behaviour implemented, so that it is completely impossible to delete it for any role types , but it is possbile to update it from any value to any value for roles of Type 3, and is possible for roles of Type 2, but with the following limitations: 1. termProposer - can't update. 2. termReviewer can update only from unprocessed to only provisionallyProcessed or rejected. 3. termFinalizer - can update only from provisionallyProcessed to only finalized or rejected. |
- TermProposer-user can update/delete some term only if that term was created by that user
- TermReviewer-user can update some term only if that term is Unprocessed
- TermFinalizer-user can update some term only if that term is ProvisionallyProcessed
- TermProposer-user can update/delete some attribute only if that attribute was created by that user and all term(s) on that attribute's level are Unprocessed, so:
- If it's a term-level attribute - that term should be Unprocessed
- If it's a language-level attribute - all terms for that language should be Unprocessed
- If it's a termEntry-level attribute - all terms for that termEntry should be Unprocessed
- TermReviewer-user can update/delete some attribute only if all term(s) on that attribute's level are Unprocessed, so it's same as in point 4 but with no 'was created by that user'-requirement
- TermFinalizer-user can update/delete some attribute only if all term(s) on that attribute's level are ProvisionallyProcessed, so it's same as in point 5 but just other status used
|