ESciDoc Committer Meeting 2009-10-20

Date: 20.10.2009 Start time: 14:30

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

Participants MPDL: Natasa Bulatovic, Michael Franke

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

Previous committer meeting
 * ESciDoc_Committer_Meeting_2009-10-13

Next committer meetings
 * ESciDoc_Committer_Meeting_2009-10-27 skipped
 * ESciDoc_Committer_Meeting_2009-11-03 skipped
 * ESciDoc_Committer_Meeting_2009-11-10

=Topics=

exchange staff and know-how
Agreed: in general the process has to be open and not only via emails. Colab and/or mailing lists may be used for all participants.

AdminTool

 * Steffen started with an email
 * Admin Tool Ideas

outcome

 * see Admin Tool Ideas page

DbCache

 * brainstorm first steps
 * XML native DB (e.g. eXist supports XACML, REST-style Web services API, SOAP, WebDAV, and the Atom Publishing Protocol. Check http://www.rpbourret.com/xml/ProdsNative.htm? for more details)
 * pure Lucene?
 * Lucene/Solr?
 * Authorization issues
 * Performance issues

Outcome
Define/distinguish between:
 * caching of data to produce long lists
 * searching/filtering with authorization
 * check technical requirements again
 * performance
 * number of items neccessary at once
 * streaming options for large lists

Wiki, Blog

 * status
 * check-out interesting application of a Blog, might be useful for eSicDoc?

Outcome

 * would be good by end of the year
 * hyperspace is interesting application, will be checked and structure can be agreed

Migration of Containers

 * need to fix Bug 666

outcome

 * Input: ESCIDOC_RELS_EXT is managed content
 * migration of current containers (MPDL): fine to migrate last version only
 * check with other users
 * New requirement: purging of versions (new requirement)
 * background: as there would be many files, for each new version of the container created in the filesystem
 * may not be storage space issue, but backup issue
 * proposal: to implement purging of versions (up to a selected version, based on user decision) (released versions can not be purged)

Content Model

 * migration for PubMan needed

Outcome

 * current solutions are not affected with the content model modifications
 * stylesheets for cmodels can be defined in cmodels (or referenced in cmodels)
 * MPDL has all different types of items/containers created with different content models (no migration problem)

Outcome

 * Schema changes
 * new methods
 * filters (additional CQL-based interfaces)
 * changes to the DB cache require a new DB schema

=Follow up Topics of Meeting München= http://colab.mpdl.mpg.de/mediawiki/ESciDoc_Developer_Workshop_2009-07-29/30
 * no discussion this week

Fundamental changes

 * 1) merge representations of REST and SOAP (see Committer_Meeting_2009-10-13)
 * 2) Replace atomistic model for Items/Components with compound model and RELS-INT
 * 3) dropping SOAP?
 * 4) Drop latest-version section from object representation (see Committer_Meeting_2009-10-13)
 * 5) set title directly (see Committer_Meeting_2009-10-13)
 * Replace DB-Cache with asynchronous Lucene Index and/or Object Database
 * synchronous Lucene Index
 * Persistent data objects in rel. DB
 * Remove mapping of "escidoc" MD-record to DC record in Components
 * Get rid of content-model-specific properties

Specifics

 * Search and administrative search
 * Admin Tools development
 * Large sets of data ingest
 * how to avoid downtime to recache and reindexing
 * Trying to add/remove members to a very large container fails with 500 Internal eSciDoc System Error
 * in Work

others

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

Planning

 * short-term 6 months

=Long term issues=

Release 1.2

 * a first release candidate is scheduled for mid of october

PubMan clean-Up

 * beginning of november the MPDL-solutions (like PubMan, Faces,....) will run in the same JBoss as the core services

Outcome

 * Info:next PubMan release (begin November) will run in same JBoss with core-service
 * current dev version can be downloaded and tried

Topics for joined development

 * start the two groups

eSciDoc Colab

 * domain-redirection for the eSciDoc-colab
 * set up the colab and move the eScoDoc pages from MPDL colab