MPDL AB Meeting 2008-08-21

MPDL  Restricted Access to MPDL

Agenda
Participants: Natasa Bulatovic, Thomas Endres, Wilhelm Frank, Michael Franke, Tobias Schraut Date: 21.08.2008

Last meeting

 * Outcome available at MPDL_AB_Meeting_2008-08-14

Martinsried
To have some benefits for the MPDL of the planned mass upload (1,000,000 items) of items into an ascidoc core in Martinsried there should be some clarification on how to proceed this test.


 * possible extensions of mass upload test for MPI Biochem, Martinsried to be written in a log file, for example:
 * time for ingesting one single item with component
 * memory consumption
 * which items should be ingested? PubItems? Perhaps for later test of Pubman with 1Mio of items?


 * what should we test afterwards
 * search (then fulltexts should be also uploaded)
 * filters
 * performance in general

Outcome

 * 1 image and 1 pdf will be used as components
 * Components “internal-managed” as xlink:href to local file
 * Publication metadata should be used to have a testbed for Pubman later
 * Tracking:
 * Operation statistics (already there): What operation? How long did it take? Was it successful?
 * Memory status (over time)
 * SNMP/MRTG (Firewall?)

Mulgara
Several issues currently are complicating the development of the Controlled Named Entities Service. What can be done?

Outcome

 * Investigate on other Triple stores

Faces
Faces: It is not possible to search for item metadata inside containers
 * Regarding searching within Albums

Outcome

 * Use case should be postponed until FIZ delivers needed functionality

Documentation
In the current code, documentation is poor. Enterprise Arcitect documentation is somewhat behind.

Outcome

 * Re-introduce Checkstyle to generate JavaDoc
 * AB will think on what documentation is needed
 * During this topic we realized that we need to:
 * revive the Code Review: Let’s start with new functionalities first
 * check on possibility for additional support position (for core services, solution installations)


 * TODO: define procedure


 * First draft - wish list (priority to be defined later) - to be discussed to next AB meeting
 * Service description in Colab, linked to Test instance of a service (test/demo servers)
 * Component diagrams for services and their dependencies
 * Sequence (esp. for data flows) or communication diagrams for service compositions
 * HowTo for developers and development environment, deployment etc.
 * Links to documentation of core services should be prominently placed
 * Immediate action: enable linking from PubMan download page to PubMan Portal on Colab (assigned already to Julia)

see eSciDoc_Technical_Documentation/Wish_List