ESciDoc Developer Workshop 2009-03-10

ESciDoc

Date: 10.03.2009 Start time: 14:30

Location: Karlsruhe, München (Video conference)

Participants MPDL: Wilhelm Frank, Natasa Bulatovic

Participants FIZ: Matthias Razum, Steffen Wagner, Frank Schwichtenberg, Harald Kappus

=Previous workshop=
 * ESciDoc_Developer_Workshop_2009-03-03

=Next workshops=
 * ESciDoc_Developer_Workshop_2009-03-17

=Agenda=

Release v.1.1

 * date
 * feature set

Outcome

 * release date: Thursday, March 12th 2009
 * features: http://www.escidoc.org/jira/browse/INFR/fixforversion/10257

Release v.1.2

 * date
 * feature set

Outcome

 * release date: June 2009
 * features: http://www.escidoc.org/jira/browse/INFR/fixforversion/10258

Japanese Charset
So maybe, there's an incompatibility between my coreservice-version and the supplied patches. But that's just a guess. Try to clear that with Michael Hoppe via phone.
 * Installed the war-patches and config files to my local coreservice instance
 * Installed xpdf and pdftotext successfully
 * Jboss starts up successfully (no exception in server.log)
 * Created and released item with japanese pdf attachment sucessfully (no exception occured)
 * when searching for the item, an error occurred (Pubman Message: 404 Servlet SRWServlet is not available)

FIZ releases decision: Since the japanese search is included in the next FIZ build according to Michael Hoppe, is it better to wait for the delivery or do it on our own?

Outcome

 * available with Rrelease 1.1

Premis 2

 * concept/requirements from MPDL needed

relations between organizational units
see new consistent table at
 * PubMan_Func_Spec_Organizational_Unit_Management
 * sheduled for v1.2
 * status of concept (FIZ)

Outcome

 * concept document for structural relations delivered by FIZ
 * check if current implementation of content relations can be (re)used

OAI PMH

 * see docu: http://www.escidoc.org/JSPWiki/en/InfrastructureOaiPmh
 * feedback from MPDL needed
 * MPDL:
 * which metadata will be provided
 * how to ensure uniform metadata
 * how to enrich oai_dc (where/how to implement new transformations to oai_dc)

Outcome

 * available in release 1.2
 * MPDL to provide mappings to OAI-DC for all required metadata sets

Content Model

 * see concept and definition at ESciDoc_Content_Models
 * see implementation and example object at ESciDoc_Content_Model_Object
 * Status: not yet finalized

Outcome

 * restart activities

TOC

 * discussion at ESciDoc_Toc

Ontology Manager

 * see ESciDoc_Content_Relations