ESciDoc Developer Workshop 2008-11-04

ESciDoc

Date: 04.11.2008 Start time: 14:30

Location: Karlsruhe, München (Telefon conference)

Participants MPDL: Wilhelm Frank, Natasa Bulatovic

Participants FIZ: Harald Kappus

=Agenda=

Previous workshop

 * ESciDoc_Developer_Workshop_2008-10-28

Next workshop

 * ESciDoc_Developer_Workshop_2008-11-18

Bug 678 Case sensitivity in filters
http://www.escidoc-project.de/issueManagement/show_bug.cgi?id=678
 * is non case sensitive behavior the default for all properties and metadata?

Outcome

 * first test with lowercase function in the SQL queries
 * if the performance is not seriously affected then do not put metadata/properties all in lower case
 * otherwise probably all metadata/properties should be created as lowercase

Bug 677 Sorting slows down the search to very big extent
http://www.escidoc-project.de/issueManagement/show_bug.cgi?id=677
 * is it OK if we invent new indexes for sorting? name of the sorting-indexes will be name of the index prefixed with sort. (eg sort.escidoc.title). I we agree, i can deliver the bugfix for build 326 and RC 1.0

Outcome

 * bug fix for build 326 (and later for RC1.0) will be delivered
 * MPDL agrees with creation of new indexes
 * ToDo: check with Michael on evtl. fix for admin tool as well

Last Video conference outcome

 * available at ESciDoc Developer Workshop 2008-10-28

Repository Reset Tool
when creating the proposed "quick-and-dirty" solution:
 * there might be dependencies between objects to be deleted (e.x. container <-> item) should they be solved or ignored?
 * strategy
 * 1) retrieve a list of objects using an existing method
 * 2) delete these objects in a loop by calling a method always with one object-ID

Outcome

 * for quick/dirty solution on items:
 * delete objects and all relations from the object (i.e. where object is a source)
 * later we have to think on proper integrity rules
 * for OUs/Ctx
 * Ous will be deleted even if there are children
 * users of the reset tool have to make sure to do it in the proper order
 * later we have to think on proper integrity rules
 * strategy is fine
 * will be good if step 2 is performed in a method that takes as input list of IDs
 * no need to abort procedure if operation of delete failed (i.e. due to non-existing ID)
 * just to create a log after each call to this procedure that gives info on ObjID deleted, oBjID for which deletion failed

Roadmap

 * see Roadmap Infrastructure

Concepts
supply links to the related colab-pages.

Content Model

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

JHOVE integration

 * discussion at ESciDoc_JHove_Integration

Default MD-Records

 * discussion at ESciDoc_Metadata_Records_Manipulation

TOC

 * discussion at ESciDoc_Toc

Ontology Manager

 * see ESciDoc_Content_Relations

OAI-PMH

 * MPDL: set up requirements for sets