ESciDoc Developer Workshop 2008-04-09

ESciDoc

Date: March 09.04.2008

Location: Karlsruhe, München (Video conference)

Participants MPDL: Natasa Bulatovic, Wilhelm Frank, Michael Franke

Participants FIZ: André Schenk, Torsten Tetteroo, Michael Schneider, Harald Kappus, Matthias Razum

Start time: 15.30 09.04.2008

Item lists, filters and authorization issue

 * discussion on the proposal sent by MPDL (the proposal is only a draft and a basis for discussion and a prototype).
 * issues regarding the scope of the filters: properties/metadata only or also with full-text contents?
 * authorization: is a tripple store sufficient to support the authorization requirements?
 * further development of the proposed model - understanding synchronization issues

Outcome

 * temporary solution will be delivered in 2-3 weeks (for filter methods only, cached complete item XML)
 * currently the prototype works, synchronization is not yet established
 * In the prototype the policies are incorporated in the SQL
 * in meantime check other solutions for full/selectable item lists that work with properties/metadata
 * FIZ will provide more information on technical solutions and other evaluated solutions i.e. Virtuoso


 * Check: institutional visibility (TODO better desc)

Synchronization of technical environment

 * move to JBoss 4.2.2
 * move from SRU (CQL) 1.1 to SRU (CQL) 1.2
 * support for Java 1.6
 * TomCat version bound to Fedora?

Outcome

 * Move to JBoss done (is it customized? .. par jars must be customized and new jars must be created)
 * not so nice... http client, staxparser - 2 different woodstocks implementations... (its faster implementation)
 * still not possible on single JBoss instance
 * CQL ... Why requirements? (better syntax, sorting ... syntax is bad) - according recommendation from Dev is not recommended
 * support for Java 1.6 (Fedora dependent ...from one to another build with fedora works or not )... (officially its not tested)
 * TomCat version - Fedora is deployed in separate Tomcat - and is not version independent

Regular problems (most important issues)

 * deletion of a component and item integrity exception
 * Outcome: is it only a bug or a logical issue as well? To make sure that deletion of a component is version specific. Also to check the searching.


 * versioning of container (new input?)
 * No new input - severe bug, but not a show stopper comparing to item lists (FIZ). It anyway has to be resolved very soon (MPDL). 


 * security - allow modification of user passwords for users (provide method, as it is already automatically set-up)
 * see Natasa's email from 18.03.2008 (sent to Frank, Torsten, cc:Mathias), content placed below:
 * we need to give access to the framework interfaces to users who are using them
 * these are accessible on our servers via 8080 port
 * we can not prevent anybody who is reading the API specification for interfaces - and somehow obtains the IP address to our FW servers to ruin all data (as all passwords are actually written in each API specification - and that is not nice, as the only option to change the password for a certain user is to go directly to escidoc database).
 * can you please remove passwords from any future versions of API specification or enable password change method as soon as possible  (not sure if the last versions of the FW are already there)
 * also in the escidoc aa schema there are users such as "indexer" (or inspector, not certain right now) ... what happens if we change these passwords? does the change of the password for "roland" has some implications to the FW functionality?''


 * Outcome:


 * update method for password change is allowed for sysadmin for all users and for each user his/her own password.
 * predefined passwords for predefined users are removed in actual build 0.159 - FIZ will provide patch for build 0.159, we should check if searching index is sufficient for only public components

Next FW releases

 * In May we will move to last build (schema changes as well) of the FW
 * how stable we can expect it would be (i.e. how well it has been already tested internally Focus: SOAP interfaces)?
 * Should be relatively stable - DANS had already tested later versions thoroughly


 * issue from previous 2 topics (Syncronization, Regular problems) can already be resolved by then?
 * Should be possible to provide 1 step of item list - filters, components, container versioning, passwords update method


 * new schema changes planned? (exception: known about TOC schema)
 * not planned for longer time yet for existing


 * status: component metadata (are metadata of the component versioned? how it affects item version?)
 * versioned, new item version is created. (214 build)


 * status: organizational unit handler (integrity checks discussed before, status transitions implemented?)
 * implemented. No automatically update of users activity flag

Organizational/Communication

 * notification mechanisms on crucial changes (change log)
 * RSS feed can be implemented from project pages
 * ''to improve the communication - also video conferences are improvement of communication
 * information that is to be used as a preparation of the Agenda - can be placed on Agenda page or on Agenda/Discussion page).

''MRA in discussion with MDR - how this kind of roadmap should look like - there is a preliminary version of the roadmap in the Wiki (listed features under short, mid, long term features). MPDL can provide other feedback.''
 * clarification of the roadmap (2008)