Difference between revisions of "PubMan Func Spec Visibility"
| Line 44: | Line 44: | ||
|width="100pt"|'''Item status''' | |width="100pt"|'''Item status''' | ||
|width="200pt"|'''Access level of component''' | |width="200pt"|'''Access level of component''' | ||
|width=" | |width="250pt"|'''Who may access''' | ||
|- | |- | ||
|'''pending''' | |'''pending''' | ||
| Line 92: | Line 92: | ||
|'''restricted - private''' | |'''restricted - private''' | ||
|Depositor (only if owner) <br> | |Depositor (only if owner) <br> | ||
Moderator (QARole) <br> | |||
Privileged Viewer | |||
|- | |- | ||
|released | |released | ||
|'''restricted - audience''' | |'''restricted - audience''' | ||
|Depositor (only if owner)<br> | |Depositor (only if owner)<br> | ||
Moderator (QARole) <br> | |||
Respective Usergroup / Organizational Unit<br> | |||
Privileged Viewer | |||
|} | |} | ||
===Assign visibility level for component(s)=== | ===Assign visibility level for component(s)=== | ||
Revision as of 09:25, 30 March 2009
WORK IN PROGRESS!!!
Institutional Visibility Scenario[edit]
Visibility for items[edit]
Item visibility in PubMan depends on item status and user role:
| Item status | Who may access |
| pending | Depositor (only if owner) Collaborator |
| submitted (as well submitted, in re-vision) | Depositor (only if owner) Moderator (QARole) |
| released | any user |
| withdrawn | any user (only with known eSciDoc ID) |
Visibility for item components[edit]
There are two levels of visibility for components in PubMan:
- "public" and
- "private" (is to be renamed "restricted").
By default, component visibility level is set to "public" during easy and full submission.
For "restricted" there are two possibilities:
- "private" and
- "audience".
For both visibility level, "private" and "audience" it's possible to provide an embargo date. If a user is not the owner and does not have special rights to access the component(s) of an item, the respective component(s) is/are not visible to the user until embargo time is over.
Component Visibility in Pubman depends on item status, access level of component and user role:
| Item status | Access level of component | Who may access |
| pending | ||
| pending | public | Depositor (only if owner) Collaborator |
| pending | restricted - private | Depositor (only if owner) Collaborator |
| pending | restricted - audience | Depositor (only if owner) Collaborator |
| submitted | ||
| submitted | public | Depositor (only if owner) Moderator (QARole) |
| submitted | restricted - private | Depositor (only if owner) Moderator (QARole) |
| submitted | restricted - audience | Depositor (only if owner) Moderator (QARole) |
| released | ||
| released | public | all users |
| released | restricted - private | Depositor (only if owner) Moderator (QARole) |
| released | restricted - audience | Depositor (only if owner) Moderator (QARole) |
Assign visibility level for component(s)[edit]
- As mentioned above, the system default visibility level for components is "public".
- The user wants to change the visibility level.
- The user chooses component visibility level "restricted".
- The user chooses, if the restricted access should be "private" or "audience".
- The user chooses the visibility level "private". Any user with user role privileged viewer for the item context can now access the item component.
- The user chooses the visibility level "audience".
- The user can choose a user group from the list of user groups displayed. These user groups are based on organizational unit level. More than one organizational unit can belong to a user group. For the future, organizational units and single users can be mixed within a user group.
- Any user within the chosen user group(s) can now access the item component.
- The visibility level for a component can be changed by the owner of the item and a user with QA role.
Collaboration scenario[edit]
The Collaborator is a user role that can be assigned to give user access on context level and item level. Access on component level will be possible in the future.
The Collaborator is split in two roles:
- Collaborator who has only rights to view items in all states
- Collaborator who has rights to view and modify
Definitions and user role descriptions[edit]
Definition of used terms[edit]
| Term | Definition |
| Item | In PubMan an item contains all metadata and its attached files describing a special type of document which is stored in the respository. |
| Content | Content is only the binary content (simply the file) which is uploaded to PubMan. |
| Component | Component can contain also some metadata and a pointer to the content. The content in eSciDoc can be internal managed (what in pubman is called "File"), or externally referenced (what in pubman is called "Locator"). In core services i.e. in the components.xsd schema of eSciDoc, this is known as "storage" property of the component. |
| Context | Context are the administrative units for management of the publication items. One or more organizational units are responsible for a context. |
Definition of mentioned user roles[edit]
| Term | Definition |
| Depositor | Role that when granted allows to create items in the repository and manage items (including components and their content) he/she created in accordance with the overall workflow rules. |
| Moderator | QARole
Is responsible for the quality assurance of the data. |
| Collaborator | Two different types of collaborators: collaborater-viewer & collaborator-modifier.
Role that when granted allows access and/or modify the containers, the items, their components and the internally managed content independently of item state. |
| Privileged Viewer | Role that when granted allows to access all components and their content of a released item in one context/collection independently of visibility. |