ESciDoc Developer Workshop 2009-05-26

ESciDoc

Date: 26.05.2009 Start time: 14:30

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

Participants MPDL: Natasa Bulatovic

Participants FIZ: Harald Kappus

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


 * Next workshops
 * ESciDoc_Developer_Workshop_2009-06-02 might be skipped because of holiday
 * ESciDoc_Developer_Workshop_2009-06-09
 * ESciDoc_Developer_Workshop_2009-06-16

=Agenda=

RC2 1.1 Build

 * when we will get the next build
 * FIZ --> the RC2 was released on Friday, May, 22nd 2009

OU history graph

 * discussion on result format
 * support history of event when this happened? (split, join, spinn-off, affiliation etc.)

Outcome

 * events/dates/metadata related to relation objects issue
 * discussion should be revived as implementation is scheduled for 1.2
 * graph result is separate issue, discussion should be revived

RELS-EXT datastream as managed content (vs. inline XML)

 * MPDL needs solution as soon as possible as FACES albums/VIRR containers are critical
 * https://fedora-commons.org/jira/browse/FCREPO-492

Outcome

 * FIZ will provide stable version 1.1 where rels-ext will be created as internally managed datastream after original 1.1 is stabilized and marked as "productive"

Admin Tool

 * Initial requirements SuperSuperUser Reset Tool Discussion
 * see also http://www.escidoc.org/jira/browse/INFR-601


 * At present seems there is no possibility to have selective recache and reindex of objects.

Outcome

 * both FIZ/MPDL have ideas and requirements on what is the Admin Tool
 * can be discussed further

OAI-PMH

 * does not run on escidoc-core but in Fedora container
 * FIZ deploys all under same JBoss as escidoc-core (Rozita will provide more info)
 * OAI-provider can not be downloaded
 * issues resolving, will come in next days (Fedora delivers wrong timestamp)
 * Fedora/eSciDoc uses cache that is build via batch process on special time-frame
 * OAI-provider delivers only data which are in the cache and not those indeed based on requested date
 * delay of caching is anyway needed, behaviour is based on Fedora and therefore the bug is still in

Fedora 3.2

 * FIZ plans to use this version of Fedora, but is not properly tested
 * can be switched to new Mulgara, but Mulgara interface has to be tested as well (1.2 - August)