ESciDoc Developer Workshop 2009-05-12

ESciDoc

Date: 12.05.2009 Start time: 16:00

Location: Karlsruhe, München (Video conference or TelCo)

Participants MPDL: Wilhelm Frank, Natasa Bulatovic

Participants FIZ: Harald Kappus,

=workshop=
 * Previous workshop
 * ESciDoc_Developer_Workshop_2009-05-05


 * Next workshops
 * ESciDoc_Developer_Workshop_2009-05-19
 * ESciDoc_Developer_Workshop_2009-05-26

=Agenda=

status v1.1 RC2

 * experiences?
 * Bugs?

Outcome

 * It is very important to have bugs fixed and delivered in a stable release
 * Until that time MPDL will work with build 501
 * The critical ticket of updating an item with a component has to be solved, but MPDL will not use nightly builds for this purpose - i.e. it has to be in a proper RC

bugs

 * Updates on items are without effect see: http://www.escidoc.org/jira/browse/INFR-288

Outcome

 * not important for 1.1
 * MPDL prefers to have each update creating a new version and the core service does not check if there has been indeed an update or not
 * FIZ will check what is possible and if feasible

Searching

 * custom stylesheet with build 501

Outcome

 * is not the indexing problem, is the filtering problem
 * input after VidCOnf: the problem was that in the eSciDoc properties file twice property with same name was defined. After this was removed, the indexing went fine. --Natasa 16:02, 12 May 2009 (UTC)

Group creation, role assignments
MPDL lacks the possibility that a user may create grants on own objects or on user groups created by a user.

What are the supported path expressions for policies for :


 * user groups
 * grants

To precise better for build 501 here is the state (actions below are only allowed to the administrator, but that is not fine, because then depositors would need to have administrator right to assign an audience or collaborator for own items):


 * info:escidoc/names:aa:1.0:action:create-grant
 * can be done by any logged-in user for own objects (path-expression exists as "grant:assigned-on:created-by") ?


 * info:escidoc/names:aa:1.0:action:revoke-grant
 * can be done by any logged-in user for grants she created (path-expression is grant:created-by? )


 * info:escidoc/names:aa:1.0:action:revoke-grants
 * can be done by any logged-in user for grants she created (path-expression is grant:created-by?)


 * info:escidoc/names:aa:1.0:action:retrieve-grant
 * can be done by any logged-in user for own grants and grants she created (path expression is ?)


 * info:escidoc/names:aa:1.0:action:create-user-group-grant, info:escidoc/names:aa:1.0:action:add-user-group-selectors, info:escidoc/names:aa:1.0:action:remove-user-group-selectors
 * all three above can be done by any user who can create user group for own groups (path expression is?)


 * info:escidoc/names:aa:1.0:action:revoke-user-group-grant, info:escidoc/names:aa:1.0:action:revoke-user-group-grants
 * can be done by users who created the user-group-grants


 * info:escidoc/names:aa:1.0:action:retrieve-user-group-grants
 * who can do this at present?
 * should be: members of the user groups, owners of the user group

=> can be done by each user who created the user group (for own groups), by administrator, and by all members of the user group
 * info:escidoc/names:aa:1.0:action:retrieve-user-group


 * administrator policy lacks definition of create-user-group action (is this actually on purpose)?

Outcome

 * MPDL will extend Moderator role to be able to assign collaborators and audience grants to groups and to be able to create groups
 * FIZ will implement the features after delivery of 1.1 (it will be extended as bug-fix for 1.1 as MPDL is critical with the timeschedule of 1.2 to wait for this feature).