ESciDoc Developer Workshop 2009-01-27

ESciDoc Was moved from 2009-01-27 to 2009-01-29

Date: 29.01.2009 Start time: 14:00

Location: Karlsruhe, München (Video conference)

Participants MPDL: Wilhelm Frank, Natasa Bulatovic

Participants FIZ: Harald Kappus, Rozita Fridman, Steffen Wagner, Andre Schenk

Previous workshop

 * ESciDoc_Developer_Workshop_2009-01-20

Next workshop
=Agenda=
 * ESciDoc_Developer_Workshop_2009-02-03

Stable release

 * Japanese search
 * Institutional visibuility
 * Group handler

SuperSuperUser / Reset Tool

 * status on user, who is able to delete any object (or list of objects --Natasa 15:37, 23 January 2009 (UTC)) in any state
 * new AdminTool with 3 Actions (this can be used by a SuperSuperUser only)
 * recache
 * Only deleted objects (list of objects) --Natasa 15:37, 23 January 2009 (UTC)
 * reindex
 * Only deleted objects (list of objects) --Natasa 15:37, 23 January 2009 (UTC)
 * delete Objects, accepts a list of ObjIds and an Option for reindex/recache no checking for inconsistency will be made, Components and Content of Items will be deleted
 * object types to be concerned:
 * items (and components)
 * containers
 * contexts
 * orgunits
 * -->MPDL: Priority needed
 * We really need this feature asap, but also we need the high-priority features listed below. Therefore, maybe FIZ would be able to make a proposal. --Natasa 15:37, 23 January 2009 (UTC)

improvements

 * Issue postponed before end of the year, due to Andre absence: see http://colab.mpdl.mpg.de/mediawiki/ESciDoc_Developer_Workshop_2008-11-18#Filter_issues
 * allowing sorting by multiple metadata values (very important, already complains)
 * allowing sorting by multiple filter criteria
 * case sensitivity in filters

new Features for V1.2
complete Liste of features (see roadmap) Priorities are needed

Handling of additional user attributes

 * using LDAP or Shibboleth for authentification, attributes may be deliverd.
 * these attributes will be kept by the framework also when the user ins't logged in any more.
 * Next time he/she loggs in all old attributes are discarded and the new set is kept
 * Related Issue: User - Person linking possibly only via srel, but ignored during input Bugzilla issue 705
 * These attributes will be delivered in the retrieve method of user
 * -->MPDL: Priority needed
 * see input below --Natasa 15:27, 23 January 2009 (UTC)

relations between organizational units

 * related Issue: relations between organizational units Bugzilla issue 709
 * -->MPDL:
 * Usage and useCases are needed to understand the enhancement
 * which relations arre needed
 * --Natasa 15:26, 23 January 2009 (UTC)concretely specified use cases do not exist yet, see
 * PubMan_Func_Spec_Organizational_Unit_Management,
 * Talk:PubMan_Collections_and_Organizational_Units
 * http://www.escidoc.org/issueManagement/show_bug.cgi?id=558 (and attached presentation)

retrieve information from granted privileges
e.g item/container X
 * retrieve list of objects for which user has been granted with role X
 * retrieve list of roles which user has been granted on item/container X
 * the latter shall return also the roles which are granted to the context of
 * -->MPDL: Priority needed
 * Usage and useCases are needed to understand the enhancement
 * see FACES use cases on Album management and album sharing/unsharing Faces Album Management --Natasa 15:21, 23 January 2009 (UTC)
 * Proposal:
 * Invent method that displays for one user all his grants with information about the scope (context,container..)
 * method takes a filter as parameter (filter for one or more roles, filter for one or more scopes) --Mih 12:23, 29 January 2009 (UTC)

complete List of Features V1.2
Priorities and requirements are needed
 * NEW: Handling of additional user attributes
 * we will not be able to switch from local user database to LDAP until this is resolved as there are additional issues also with OrgUnits and group handler. We need first to talk internally within a team on this issue --Natasa 15:19, 23 January 2009 (UTC)
 * NEW: relations between organizational units
 * Schedule (MPDL): April 2009 (FIZ: March 2009) --Natasa 15:06, 23 January 2009 (UTC)
 * NEW: retrieve information from granted privileges
 * Schedule (MPDL): Asap (Faces R3.5) (FIZ: February 2009) --Natasa 15:06, 23 January 2009 (UTC)
 * Administrative Searches
 * Schedule (MPDL): April 2009 (FIZ: March 2009) --Natasa 15:06, 23 January 2009 (UTC)
 * Technical Metadata Extraction
 * If this is about integration of JHove handler, we have closed and discarded this issue. See Workshop 13-01-2009 --Natasa 15:06, 23 January 2009 (UTC)
 * Organizational Unit Tree
 * MPDL is fine with current list, the tree was add-on idea developed in discussion and it is indeed for MPDL at present not too important. So i would switch this priority to "low", and monitor further requirements. --Natasa 15:06, 23 January 2009 (UTC)
 * Searching in Albums
 * MPDL miscomunicated due to internal misunderstanding. Concrete Faces use case talks about searching within list of albums (i.e. within released albums, but only by album metadata. At present this is not needed. Please consider it as low for now - as we are not certain how will further Faces(NIMS case: Diamonds) and VIRR use cases develop. (probably similar technical issue as for searching for tags.) --Natasa 15:06, 23 January 2009 (UTC)
 * OAI-PMH sets
 * MPDL specified the requirements, see links to requirements page, but we are not certain and have not received any explanation on what is possible to be done by core services in terms of specification of sets etc. We need to re-discuss this issue from several aspects. --Natasa 15:06, 23 January 2009 (UTC)
 * Ontology Manager
 * we have agreed FIZ to provide some more input on how/where we will store relation ontologies, so these are not indeed part of the source code only. MPDL proposed to use eSciDoc PURL domain for addressing. I think on the rest we have agreed. But please clarify here better what is meant with this topic. See also outcomes at Relation ontology and content relations clarification
 * Searching for Tags
 * MPDL at present has only a feature of local tags, but they are part of the item. Therefore, we do have the primary use-case implemented via content-model specific properties.
 * MPDL&FIZ agreed that Tags are to be created as items with separate content model and related to both sides of the "relation object". This discards the need to have separate relation object. Thus local-tags can be searchable as any other item.
 * when dealing with this approach, we could think in future about use case such as "search within tags/related objects" -> but not yet. Therefore this point can be put for now as "normal" priority. I also think that we have agreed on implementation together with Frank/Harald on some previous VidConf (link to be put in here) --Natasa 15:15, 23 January 2009 (UTC)


 * Default Metadata
 * closed discussion for now. See outcome at ESciDoc_Developer_Workshop_2009-01-13 . We would certainly however like to clarify what gets into the filter cache (all metadata records or only eSciDoc metadata records?) --Natasa 15:17, 23 January 2009 (UTC)
 * Colaborator-modifier role
 * see outcome VidConf 13-01-2009 at ESciDoc_Developer_Workshop_2009-01-13
 * rule based role grant is to be researched as at present is not possible
 * Collaborator role is implemented, can retrieve the item and may retrieve the content of the components
 * Collaborator can be defined for ctx, cnt, item, component
 * New role: Collaborator modifier may modify items, containers, components in same manner as depositor


 * more/other features needed?
 * will be prepared and communicated for next VidConf! --Natasa 15:31, 23 January 2009 (UTC)

Shibboleth adoption

 * status at MPDL

Content Model

 * see concept and definition at ESciDoc_Content_Models
 * see implementation and example object at ESciDoc_Content_Model_Object

TOC

 * discussion at ESciDoc_Toc

Ontology Manager

 * see ESciDoc_Content_Relations

OAI-PMH

 * MPDL: set up requirements for sets
 * MPDL link to requirements: PubMan_Func_Spec_Export/OAI_Data_Provider
 * FIZ: information on current implementation status and implemented features

Fedora FOXML handling

 * Fedora memory problem
 * use a heap size of more than 1 or 2 GByte as a work around
 * FIZ will try to talk to Fedora people that some of the problems could prevent MPDL from using fedora in a production environment
 * MPDL proposes common meeting FIZ/Fedora/MPDL to discuss about possible resolutions