MPDL Developer Meeting 2010-10-12

MPDL

Previous Meeting

 * Previous meeting 2010-10-05

Next Meeting

 * Next meeting 2010-10-19

PubMan

 * institutes migration see PubMan and migration
 * check migration activities with SVM-DEV
 * the slots starts middle of Nov (1-8 institutes)
 * in meantime NucPhys migration and the LingLit script
 * PID Cache population
 * PubMan Installer
 * will be announced
 * JusCMS extensions go in 6.2?
 * waiting input from Malte
 * Run is started
 * calculated up to 7 weeks - check the Candidates vs Real release in run team
 * most critical is YB
 * waiting on feedback from NIMS
 * try to accelerate the feeback
 * Tests needed
 * no time - concept shall be defined in details
 * batch numbers...

Imeji

 * Imeji in JIRA as separate project
 * demonstrator only - closure this week
 * Imeji Workshop - 22.10.2010 HU Berlin see http://www2.hu-berlin.de/mediathek/wiki/index.php?title=Imago_Mediathek
 * Faces - prod
 * checking the problem of instability - assumption Apache/Jboss connector

VIRR

 * information on data to be ingested

Other

 * eSciDoc Days
 * From MPDL Malte, Natasa, Katrin, Juliane, Michael, Markus, and Kristina will participate
 * Problems with Archiva
 * Problems stay for version 1.3.1 as well, 99% of processor load for an java process, no idea what it does. Possible solutions:
 * New archiva instance on vm30 for testing purposes (archiva or SuSE environment problem on vm16?)
 * Other Build Artifact Repository Manager can be used instead of Archiva: Sonatype Nexus. More stable, has less performance issues, better supported, etc. GPL for basic version.


 * Release log pages: after release is closed - see PubMan_6_1/ReleaseLog
 * test server not functioning properly (must be set-up by Mid September)
 * PubMan versions on migration, peer serviers - what are the current versions there?
 * migration and peer shall have up-to-date state as other versions do have bugs

Services

 * PID - central service vs solution specific vs core service specific
 * transformation - one instance
 * CoNE - one instance
 * in general all common services are to be revised

Testing

 * high prio
 * reduce manual testing (start asap)
 * think how best to develop integration tests (services, solutions etc.)
 * may be related to decision on splitting of services as completely separate in deployment


 * e.g. PubMan testing
 * transformations
 * submissions
 * search (not critical)


 * demonstrator - run - to Selenium tests?
 * set-up the framework for testing first?

Core service

 * test coverage
 * java client api
 * when best to start testing it?

Appservers
Activities to bring solutions to
 * Jboss 4-5-6
 * Glassfish
 * other