Power User
Delete, Rename, Update BIE owned by others
Delete, Rename, Update Published BIEs
For example, when reusing BIE. Even though still experimenting with BIE, it has to be published first to be reused. But later may need to modify or delete that BIE b/c it is not good enough yet.
Update State from Published to Candidate, Edit
...
Role\Functionality | Read Production BIE | Copy BIE | Read & Copy non-Production BIE | Create/Edit BIE Not in Production State | Edit BIE in Production State | Express BIE (when in appropriate state and ownership) | Discard owned WIP BIE | Discard Production BIE, even unowned (orphaned BIE) | Transfer ownership when owned and in WIP state | Transfer ownership when not owned in any state | Uplifting BIE (that he can read) | Extend BIE globally |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Public End User Role: Require no login | Y (Maybe allow Architect End User to configure what BIEs are readable) | N | N | N | NN | Y | N | N | N | N | N | N |
Enterprise End User Role | Y | Y | Y | Y | N | Y | Y | N | Y | N | Y | N |
Architect/Admin End User Role | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
...
Role\Functionality | Read CC in production | Read CC in non-production | Create/Edit CC Not in Production State | Amend CC | Delete owned WIP CC | Restore deleted CC | Purge deleted CC | Transfer ownership when owned and in WIP state | Transfer ownership when not owned in any state | Uplifting CC or code list (that he can read) | Namespace Management |
|---|---|---|---|---|---|---|---|---|---|---|---|
Public End User Role: Require no login | Y | N | N | N | N | N | N | N | N | N | |
Enterprise End User Role | Y | Y | Y | Y | Y | Y | N | Y | N | Y | |
Architect End User Role | Y | Y | Y | Y | Y | Y | Y | Y | Y |
...
For End User on Developer/Standard BIE
Do we still need the notion of developer the BIE, because right now Express Packs are created by end user role? Developer users cannot have extension or use non-standard code list.
need to go back and think about whether some end users can express the CC schemasThis is more relevant to the use case where Express Pack is developed on the develop instance, pushed out to the oagiscore instance. What we want to allow the end user role on the oagiscore instance to be able to do with developer’s BIE.
Role\Functionality | Read & Copy Production BIEDeveloper BIE in Production | Copy Developer BIE Production => New BIE becomes End User BIE | Express developer BIE | Uplifting Developer BIE => New BIE becomes End User BIE | Read & Copy non-ProductionIEProduction BIE | Create/Edit BIE Not in Production State | Edit BIE in Production State | Express BIE (when in appropriate state and ownership) | Discard owned, WIP BIE | Discard Production BIE, even unowned | Transfer ownership when owned and in WIP state | Transfer ownership when not owned in any state | Uplifting BIE (that he can read) | Extend BIE globally | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Public User Role: Require no login | Y (Maybe allow Admin/Architect Developer to configure what BIEs are readable) | N | Y | N | N | N | N | N | N | N | N | N | N | N | |||||||||
Enterprise End User Role | Y => copied BIE becomes end user’s BIE | N | N | Y | Y | Y | Y | Y | N | Y | NY | NN | Y | N | Y => uplifted BIE becomes end user’s BIE | N | |||||||
Architect/Admin End User Role | Y => copied BIE becomes end user’s BIE | N | N | N | N | N | N | N | N | Y => uplifted BIE becomes end user’s BIE | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | N |
For End User on Developer/Standard CC
All End users can only read developer CCs and BIEs as it is now..
Role\Functionality | Read Published CC | Read non-pubished CC (i.e., CC in Working branch) | Create/Edit CC Not in Published state | Revise CC | Delete owned WIP CC | Restore deleted CC | Purge deleted CC | Transfer ownership when owned and in WIP state | Transfer ownership when not owned in any state | Release Management | Module Management | CC Expression |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Public End User Role | N | N | N | N | N | N | N | N | N | N | N | N |
Enterprise End User Role | Y | Y | N | N | N | N | N | N | N | N | N | N |
Architect End User Role | Y | Y | N | N | N | N | N | N | N | N | N | N |
For Developer on Developer/Standard BIE
Role\Functionality | Read & Copy non-Production BIE | Create/Edit BIE Not in Production State | Edit BIE in Production State | Express BIE (when in appropriate state and ownership) | Discard owned, WIP BIE | Discard Production BIE, even unowned | Transfer ownership when owned and in WIP state | Transfer ownership when not owned in any state | Uplifting BIE (that he can read) | Extend BIE locally and globally |
|---|---|---|---|---|---|---|---|---|---|---|
Standard contributor | Y | Y | N | Y | Y | N | Y | N | Y | N |
Standard Admin | Y | Y | Y | Y | Y | Y | Y | Y | Y | N |
For Developer on Developer/Standard CC
Role\Functionality | Read Published CC | Read non-pubished CC (i.e., CC in Working branch) | Create/Edit CC Not in Published state | Revise CC | Delete owned WIP CC | Restore deleted CC | Purge deleted CC | Transfer ownership when owned and in WIP state | Transfer ownership when not owned in any state | Release Management | Module Management | CC Expression |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Standard Contributor | Y | Y | Y | Y | Y | Y | N | Y | N | N | N | Y |
Standard Admin | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
For Developer on End User BIE and CC
Developers can only read end user BIEs and CCs as it is now.
Manage Account
Role\Functionality | Read End user Production BIE | Copy End User BIE => becomes developer BIE and any extensions are removed | Read & Copy non-Production End User BIE | Create/Edit End user BIE Not in Production State | Edit End User BIE in Production State | Express End User BIE (when in appropriate state and ownership) | Discard Production End User BIE, even unowned (orphaned BIE) | Transfer ownership when not owned in any state | Uplifting End User BIE (that he can read) |
|---|---|---|---|---|---|---|---|---|---|
Standard contributor | Y | Y | N | N | N | Y | N | N | N |
Standard Admin | Y | Y | N | N | N | Y | N | N | N |