ESciDoc Committer Meeting 2010-06-08

Date: 08.06.2010 Start time: 14:30

Location: Karlsruhe, München phone: +49-89-38602-223  VidCo-ISDN: 08938602595

Participants MPDL: Natasa Bulatovic, Wilhelm Frank

Participants FIZ: Steffen Wagner, Frank Schwichtenberg, Harald Kappus

Previous committer meeting
 * ESciDoc_Committer_Meeting_2010-06-01

Next committer meetings
 * ESciDoc_Committer_Meeting_2010-06-15
 * ESciDoc_Committer_Meeting_2010-06-22

=Topics=

PubMan

 * content download - issue in progress
 * validation - how-to- get schemas and upload/modify new schemas (solved)

outcome

 * validation is closed
 * check on content retrieval

v1.2

 * Release

outcome

 * working on documentation
 * release date is undefined

SemanticStoreHandler

 * is set to "deprecated"
 * MPDL uses spo for old content relations
 * Content relations to be discussed in the next VidConf (to be prepared)

outcome

 * Content relations 1:M instead of 1:1
 * current implementation and concepts to be checked and see possibilities to improve it
 * FIZ/MPDL to check the previous concepts and see what can be done

PIDs in the core-service

 * related issue see https://www.escidoc.org/jira/browse/INFR-907
 * whether core-service should validate the PID duplication at least locally (duplicate checking based on exact value)

Beside the formerly discussed limitations of checking the uniqueness only locally exists PID consturcts witch stay in conflict with this approach.

The infrastructure could not have all information to distinguish if a PID is an invalid dublicate or a valid. A Handle can carry multiple location of a resource and also qualifiy them. A valid (and feasible) Handle could aggregate all documents to a certain topic. Handle -> URL 1..URL n

Assume we have two Items escidoc:1 and escidoc:2. escidoc:2 has the same content of escidoc:1 but only in another language (escidoc:2 is_translation_of escidoc:1). Then would it be a valid, that escidoc:1 and escidoc:2 are tagged with the same PID.

others

 * eSciDoc-Colab Page setup
 * Alignment of tools and processes (e.g., Maven)
 * Improved and harmonized communication of eSciDoc
 * eSciDoc Blog
 * service names and classification
 * documentation of services
 * installation guides
 * eSciDoc Lab: Colab page gathering experimental modules
 * Exchange of staff members for specific developments or share development