Talk:ESciDoc Access Rights

Meeting 19th march 2009: Consequences on eSciDoc Access rights on Enduser-features / "institutional visibility"

View item

• type of access/visibility should be visible to all users
• Improvement sorting: sort by items with attached fulltexts. within fulltexts, sort by visibilities (future development)

Admin solution (user roles, context)

• extend use case create user: assign him either role audience or role collaboratr for specific context
• extend use case create context: assign property "collaboration" for a complete context (i.e. all items in this context will be accessible/visible to all collaborators roles)
• extend use case/new use case: create user group (all org unit users, specific account users)

QA - modify item

• Visibility internal: can be accessed by QA role, but not viewed/opened by QA role. Does this make sense? Might be improvement for later. (not R5)
• Possible improvement for standard workflwo: owner can always modify his own items, independent from state of item. (not R5)
• Basic user info: Collaboration can be provided by
  • a) providing access for collaborators for specific items or
  • b) provide access for collaborators for all items in a specific context.
  • collaborators can access items during all states (from pending to released).
  • Is it technically possible that collaborators can modify the collab item while pending, submitted, in revision, released? If yes, we need to define for which states.

all items (and its components) which have property as "collaboration item"

• • b) all items in context which has property "collaboration
• Do we need QA workspace for Collaborator, as he can access and modify?=> Proposal simple solution: No need for own workspace. The items, where I have access to as collaborator, should be listed under "my items". In addition, we need filter method to sort by "my own items" (i.e. i am depositor/owner) and "items for which i am collaborator". If filtering is not possible, we have to add specific icons(or similar) for the two types of items (i.e. my items or collaborator items)
• How to mark item as being accessible for collaborators or remove this possibility?: On view item page, we include new tab "collaboration". On this tab, QA role and Owner can see the item log (or parts of it, where collaborators have accessed and modified) and can add or remove the possibility for collaborators to access/modify this explicit item.In this context, he needs to have an info-button (link to context-sensitive help collaboration) to explain what does role collaborator mean.

In case the role for collaboration has been defined for the complete scope of a context, the item property "collaboration item" cannot be removed. In this case, an information has to be displayed that "collaboration" has been defined for complete scope.

Audience

Audience is

• a user role
• a file visibility
• allows specific users to access released items and their components with file visibility "audience".
• The depositor/owner has no possibility to check the respective users/user groups with "audience rights" during submission. This has to be agreed on beforehand.

Todos:

• New use cases?
• Modify existing use cases?
• update PubMan Action Matrix

Related ToDos:

• PubMan Copyright => Update submission?
• Look-up services => Update view item?

Enhanced Scientific Documentation

Quality Assurance

Publication Management