MPDL Developer Meeting 2011-09-06

MPDL

Previous meeting 2011-08-30 Next meeting 2011-09-13

AWOB

 * 1st AWOB Demonstrator Release - End of September
 * Liferay Simposium on October 18-19, Frankfurt, Germany

DIGITIZATION LIFECYCLE

 * 1st Demonstrator Release in the middle of October

DARIAH

 * setting up Dariah Development Environmen:
 * Jira
 * LDAP
 * Confluence

IMEJI

 * Implementation Phase until the end of this week

current release levels

 * All levels (dev/test/qa/live/r/nims) run on escidocadmin.mpdl.mpg.de on vm21 - due to chain of release dependencies
 * Uses Python 242 and Turbogears (v. 1.0.4.x) as main python framework
 * Will not work (due to framework dependencies) on later python versions
 * due to requirement to run on Python 2.4.2, vm40 is still running SLES 10 - the only vm still on SLES10

We had hoped that the new java-based console in Escidoc Core-Services 1.3.1 would remove the need for this application, but it doesn't run stably and doesn't support groups. So we will continue to need escidocadmin for a while longer ...

escidocadmin currently consists of

 * Escidoc client framework for REST access to:
 * "aa" (useraccount, group, privilieges)
 * OU (organisational unit)
 * context
 * Item - this isn't used in escidocadmin
 * container - this isn't used in escidocadmin
 * A (quite small) web application (about eight pages, implemented with TG1 as controller, Kid as Template / View framework

Can someone give me a link or description of how the client framework was used by Robert for testing escidoc coreservices in the past ?

1. No migration
Keep everything as it is, only make the most urgent bug fixes. Advantage: quick and easy. Disadvantage: it doesn't work with core-services 1.3.1, and we don't solve the release dependency problem

2. Migrate to Python 2.6.x and Turbogears 2.1.x

 * already investigated in virtualbox environment. The migration of Kid templates to Genshi templates looks easy
 * Disadvantage: not yet finished. I estimate several weeks work.
 * Advantage: We solve the release dependency chain (and I get better at python). Also: Turbogears includes an extensible authentication/authorisation framework (repoze.what / repoze.who). This means that Escidocadmin could implement the model, rather than needing a local sqllite database as at present. This is "cleaner" but would require more programming effort

3. throw away the web appliciation, use a command-line based client
Advantage. slightly less work than 2, and we preserve the use of the client framework. Disadvantage: Less easy to use, more to test.

====

Other

 * New JRebel license
 * GreenHopper license
 * Bonfire license - decision needed by next week (who to contribute: volunteers from developers and SvM needed.
 * Input from NBU: yes, would be good to have it, see also e-mail to eSciDoc-Dev list from NBU on 20.07)
 * PubMan Days
 * eSciDoc Days

Next moderator

 * Natasa