MPDL Developer Meeting 2010-12-07

MPDL

Previous Meeting

 * Previous meeting 2010-11-30

Next Meeting

 * Next meeting 2010-12-14

Agenda

 * PubMan migration
 * first feedback from FHI, Kernphysic
 * second test import is needed
 * waiting for feedback from other 3 institutes
 * check the batch updater for fixing of data on live


 * PubMan Run
 * qa-snapshot - testing is critical
 * release if first test is successfull and labels are ready


 * Linguistic Literature Blog
 * data transformation (new test) next week
 * next week WPBlog developer (external)
 * important to have a smaller set of valid data (already modified)
 * important to have test WordPress installation enabled


 * Living Reviews migration from AEI Golm to GWDG
 * not discussed


 * Faces/Imeji
 * no development


 * VIRR
 * no development
 * new MAB mapping/transformation has to be defined
 * 500000 images expected
 * re-index and re-cache critical


 * eDoc (RZG-srv02.zim.mpg.de) migration to GWDG
 * is a very old server
 * cvs repository to svn repository test migration (including history)
 * test environment in preparation


 * Other activities:
 * preparation of DigiLife cycle, Diliah, Dariah
 * DFKI - develop DIliah - Digital Library Assistant - GUI to see co-authors, publications with same subjects - can be integrated into eSciDoc - so they directly access our existing Lucene index and get information (Java/Flex -> when finished a link on PubMan)
 * DigiLifeCycle - to set-up a playground for upload of data by the institutes - check for VM resource availability - test-virr?


 * NIMS Ingestion
 * ingest a lot of data in live PubMan
 * library material (splitted PDfs - each max 50 MBs)
 * metadata by end of the week
 * SWORD 6.2 to run with live


 * JIRA upgrade done due to security issue
 * test instance for PubMan enabled


 * Workshops/Conferences
 * Jboss workshop
 * January 2011 - ca. 20.01
 * http://www.netways.de/en/de/home/
 * JSF conference - would be good to prepare JSF 2.0 for new or existing solution to gain some experience upfront

Other - not discussed

 * 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
 * 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 - not discussed

 * 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 - not discussed

 * 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 - not discussed

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

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