ESciDoc Developer Workshop 2009-06-23

ESciDoc

Date: 23.06.2009 Start time: 14:30

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

Participants MPDL: Natasa Bulatovic

Participants FIZ: Steffen Wagner, Michael Hoppe, Harald Kappus

=workshop=
 * Previous workshop
 * ESciDoc_Developer_Workshop_2009-05-19


 * Next workshops
 * ESciDoc_Developer_Workshop_2009-06-30
 * ESciDoc_Developer_Workshop_2009-07-07

=Agenda=

next VidCo
30.06.2009, at 10:00 am

Migration Tool

 * status of tests at MPDL

Outcome

 * No tests run so far at MPDL as MPDL has been using dev versions (done migration on their own)
 * Report from Matthias: external Partner had run migration successfully

Fedora 3.2

 * FIZ plans to use this version of Fedora, but is not properly tested
 * can be switched to new Mulgara, but Mulgara interface has to be tested as well (1.2 - August)

Outcome

 * 3.2 will be integrated into new dev versions after all tests run properly

Example Objects for PubMan

 * In order to run proper tests on our side as well as providing a set of useful example objects for PubMan users, we would like to add a set of PubMan-compatible example objects to the software distribution of the eSciDoc Infrastructure, including necessary roles and policies.
 * Can MPDL provide such a set of objects (OU, Context, Items, ContentModel, ...)?

The MPDL can provide such a set, the question is, is it necessary? the pubman_installer will create such an initial dataset on the coreservice instance. But If you need it for internal tests for example, of course I can send it to you. --Tom Endres

Outcome

 * Set of MPDL objects esp. on Organizational Units is needed
 * Input Matthias: PubMan should deal with any organizational units (not only those described with MPDL metadata) without need to change the code or JibX transformation
 * ToDo: MPDL check consequences and possibilities, first suggestion may be: additional metadata record

PubMan in same JBoss as Core Services: Status

 * After eSciDoc Days, we received several inquiries for re-uses of PubMan in other institutions. We still have to explain them that in order to run PubMan, they need to install two instances of JBoss. This is always a major issue for potential users. Malte told me last September that Tom would start working on this soon.
 * As far as I gathered, this task has still not been tackled? Any news on this?

No progress on that topic, since all the work is now spent on the pubman_installer. But I think if the installer is finished, one jboss should be the next step of course. --- Tom Endres

Outcome

 * MPDL is aware of things that need to be changed, but it can only approach it from August 2009
 * Both Teams have to define/agree as well:
 * which version of JBoss to use (what is possible)
 * Solutions run with standard JBoss while core-service uses patched JBoss (changed libraries)
 * it possible to use not-patched version of JBoss?
 * whether to switch to Glassfish (considerations started at FIZ)
 * suggestion: input gather at Application servers evaluation for eSciDoc

User group handler enhancements

 * see issues
 * http://www.escidoc.org/jira/browse/INFR-715
 * http://www.escidoc.org/jira/browse/INFR-716
 * http://www.escidoc.org/jira/browse/INFR-717
 * http://www.escidoc.org/jira/browse/INFR-718

Outcome

 * to be able to retrieve grants of user (directly on indirectly via User group), the proposal is to implement it in UserHandler.retrieveCurrentGrants
 * other issues will be implemented with 1.2
 * MPDL to send link to use cases

Replacement of dummy PIDs

 * batch update of all existing FOXML objects (RELS-EXT datastreams)
 * prerequisites and constraints!?

Outcome

 * No constraints foreseen by FIZ
 * Proposal: to write into version history of object one new line with the information on modifications