ESciDoc Developer Workshop 2008-09-09

ESciDoc

Date: 09.09.2008 Start time: 14:30

Location: Karlsruhe, München (Video conference)

Participants MPDL: Natasa Bulatovic, Michael Franke

Participants FIZ: Harald Kappus, Michael Hoppe, Frank Schwichtenberg, Matthias Razum

=Agenda=

Last Video conference outcome

 * available at ESciDoc Developer Workshop 2008-09-02

Critical issues & discussion on pre-release 1.0

 * Outcome form last meeting
 * FIZ will offer bug-fixes for stable releases in future (separate branch)
 * new features will be part only of developer releases
 * new stable releases will contain new features and all bug fixes done to previous stable releases
 * MPDL will develop on stable releases (and would expect bug fixes for the stable releases)
 * MPDL development on developer releases (at own risk :)
 * There is a possibility to have a stable release before 1.0
 * MPDL will check the bug-fixes from 3.0.3 and 3.0.4 and will provide FIZ with a wish-list from those bug-fixes, features for the intermediate stable release (i.e. either 3.0.3 or 3.0.4)
 * FIZ will provide migration procedures from one to another stable release
 * migration procedures should be (for test purposes) provided in advance (before next stable release is fixed) to enable MPDL to test the migration
 * Release 1.0 is planned end of September


 * For MPDL it is absolutely necessary to have as soon as possible fixed the following:
 * 639 Description of removeMembers method is missing in Container Handler API docu
 * 636 spurious 409 on item creation
 * 637 Content download
 * 558 Enable searching of organizational units/ or retrieve List of organizational unit objects for selected starting organizational-unit
 * 559 Add member to container corrupts container object after approx. 50 new members added


 * Migration of first data collections from eDoc


 * Update/discussion

Outcome

 * 639 Description of removeMembers method is missing in Container Handler API docu
 * Implemented
 * 636 spurious 409 on item creation
 * Both teams agreed not too critical for pre-release 1.0 (but for 1.0)
 * 637 Content download
 * Critical, by end of the Week (earliest Thursday, FIZ will give information if this can be
 * Input from MPDL - this bug was not identified before, we got it first time with build .303 - MPDL will provide more info on latest stable release (build.297), if this is happening there
 * 558 Enable searching of organizational units/ or retrieve List of organizational unit objects for selected starting organizational-unit
 * Implemented
 * 559 Add member to container corrupts container object after approx. 50 new members added
 * New Fedora patch exists, we need to see how it will be delivered to MPDL. )


 * FIZ will provide info on Thursday if 637 is resolvable and if it is not MPDL will have to decide if we wait for 638 resolution and pre-release then, or we have pre-release first and wait for 637 bugfix
 * First possible pre-release date (not considering 637) - Monday
 * The pre-release is a blocker for MPDL development and new solution releases (as these issues are essencial part of new features)

Discussion on release 1.0

 * Issues so far:
 * 623	extraction from a private content
 * 612   Digilib integration not working
 * 595   Digilib Client leads to a crash of Fedora Repository
 * 398	New method: revoke grants or all grants of a user needed
 * 323 Release R3: sorting requirements for item lists (very important (as soon as possible, but depends on filter functionality in fact - search sort indexes are fine, we actually do not have filters with provided sorting criteria)
 * 574 item creation fails with xml parser error related to mass creation of items (rel 1.0, but we first check on migration)


 * Ingestion of data

Outcome

 * 323 will probably not be fully functional, agreed to revive discussion on this topic (on Colab)
 * 398 will be delivered for 1.0
 * Problems with resources on 398 and institutional visibility (as institutional visibility requires more time and both teams realized will not be delivered as part of 1.0, 398 will be prioritized - as it would take 2-3 days of work)
 * ingestion interface will be part of 1.0 (method where we can ingest items/containers with item/container.xml, in desired workflow status - pending, submitted, released and if needed with already assigned PIDs).
 * other tickets from above will be resolved with 1.0

TOC Handler

 * Outcome of last meeting (in short)
 * TOC relation will be created as structural relation
 * Container handler should provide a method with which we are able to retrieve references to Container TOC objects
 * additional content relations can be created from Container to TOC object (in this case, new content relation should be included in changed ontology file and sent to FIZ)
 * srel schema change necessary


 * When can we expect the implementation of these issues (rel 1.0?)
 * Not certain if Willy created tickets related to TOC handler incosistency before he went to vacation: TOC items should not be retrieved via Item handler or vice versa (we were able to create TOC items via Item handler, then update them via TOC handler etc.) TOC handler should be restrictive to TOC resources only - ItemHandler should not deal with TOC resources.

Outcome

 * For core service release 1.0 it is important to have TOC handler fully functional (including the structural relations)
 * Ehnancements and bugs should be reported (will be considered after core service 1.0 release)
 * Update 10.09.08, Ticket created, see Bugzilla 647

Institutional Visibility

 * new feedback provided on the Institutional visibility requirements discussion page
 * discussion on next steps

Outcome

 * MPDL to sketch some idea on Role-based or other concept
 * what is the purpose of visibility
 * has to be taken care for performance issues as well
 * input given for test implementation of proposal from MPDL
 * performance is critical when sorting takes place and taking care of the policies
 * MPDL proposal was not complete
 * MPDL would like to get information on how these are at present implemented
 * FIZ will send MPLD original presentation adopted with the currently implemented concept in use


 * There is a confusion of what is meant with "private" visibility vs. "private+internal set of users" visibility

Start JBoss with PubMan EAR

 * current situation/status (new input from MPDL?)

Outcome

 * MPDL will work on this issue in October
 * There is a possibility to have this issue already resolved with next PubMan release, but not before October

Miscelaneous
(The search module should use a new library for building up a cql-tree. )
 * super user to wipe-out (delete) all objects independent on their status
 * Using Java 1.6 can be an issue for running PubMan and core services under same JBoss?

Outcome

 * super user issue will be considered after core services 1.0
 * Java 1.6 upgrade can be considered after core services 1.0 - so far no critical issues, the only blocker was Fedora. Current Fedora version is working with Java 1.6 so would not be an issue
 * FIZ proposed (and MPDL is interested) in having single JBoss where Fedora, core services and solution run. It is possible to run Fedora in JBoss without TomCat container. FIZ will put the documentation on eSciDoc project pages.

Next eSciDoc Workshop

 * Proposal München, 14-15.10.2008

Outcome

 * update from 11.09.2008
 * Workshop will be held in München, 14-15.2008.