ESciDoc Developer Workshop 2009-02-17

ESciDoc

Date: 17.02.2009 Start time: 14:30

Location: Karlsruhe, München (Video conference)

Participants MPDL: Wilhelm Frank, Natasa Bulatovic

Participants FIZ: Harald Kappus

Previous workshop

 * ESciDoc_Developer_Workshop_2009-02-10

Next workshops

 * ESciDoc_Developer_Workshop_2009-02-24 skipped (Fashing)
 * ESciDoc_Developer_Workshop_2009-03-03

=Agenda=

Main topics
NOTE: Topics were Outcome is not written are not discussed

Filter issues and authorization

 * Discussion, reported tickets
 * http://www.escidoc.org/jira/browse/DEV-581
 * http://www.escidoc.org/jira/browse/DEV-584
 * Not reported, as we could not reproduce but very strange
 * there was duplicate entry in the cache in table list.properties
 * checking the cache insert/update procedures?
 * behaviour concequence: the server.log reported errors in sql query (more than 1 row retrieved where 1 row was expected in subqueries of filters), the data requested with the filter were delivered by the filter method, with no exception, but not sorted nor filtered indeed.

Outcome

 * FIZ will check the queries and work further on optimization
 * MPDL reported it will be important to have it delivered with next release, due to mass data expected (migration of data from eDoc)
 * both teams agreed on having in filtered properties values up to 2000 chars (filters will be only possible by values max to 2000 characters). This will be done automatically during population of the filter cache
 * the filter indexes will the be recreated without substring function
 * regarding duplicate entry issues: MPDL will monitor if that appears again, FIZ will check the filter delivery procedures to report exceptions in this case
 * in next release filters by role should work by role-id and not by role-name to make the filters consistent

New: Extension to log-in and authorization

 * Local user management: extension to log-in page
 * create account
 * users should receive an email for created account
 * change password feature
 * forgotten password feature

Outcome

 * issue is serious and has to be discussed when Matthias is back
 * MPDL reported that at present we are using local user database until LDAP/Shibboleth solution with additional user attributes is ready
 * MPDL will in addition cross check this with Malte

xml:base attribute (SOAP)

 * http://www.escidoc.org/jira/browse/DEV-583

Outcome

 * According the xLink standard xml:base attribute can appear with each element where there is relative xlink
 * Both teams agreed to go with the standard
 * MPDL minimum requirement: to have this attribute delivered with components and with item element also in SOAP representation
 * Use case: exporting of native XML

SuperSuperUser / Reset Tool

 * scheduled for v1.1
 * in work

Outcome

 * in progress, no date for release yet

Digilib

 * Status by MPDL
 * had to explicitly configure the digilib parameters in escidoc-core.properties
 * digilib.scaler = http://localhost:8082/DigilibServer/Scaler
 * digilib.digimage = http://dev-coreservice.mpdl.mpg.de:8080/DigilibClient/greyskin/digimage-neu.jsp
 * escidoc.core.digilib.digicat-url = /DigilibClient/greyskin/digicat.jsp


 * without those params --> HTTP connection failed
 * changing some scaler values in the URL sometimes causes an
 * java.lang.IllegalStateException: getOutputStream has already been called for this response
 * requires refresh of page

Steffen:
 * going to check the getOutputStream failure
 * review the installation guide on wiki to make required configurations more clear (http://www.escidoc.org/JSPWiki/en/DigilibService)

Handling of additional user attributes

 * FIZ is preparing a concept
 * status?
 * Please see concept http://colab.mpdl.mpg.de/mediawiki/ESciDoc_User_Account_Attributes

Outcome

 * MPDL will check the concept

relations between organizational units
see
 * PubMan_Func_Spec_Organizational_Unit_Management,
 * Talk:PubMan_Collections_and_Organizational_Units
 * Talk:PubMan_Func_Spec_Organizational_Unit_Management
 * http://www.escidoc.org/issueManagement/show_bug.cgi?id=558 (and attached presentation)
 * sheduled for v1.2
 * MPDL will check tables, as it seems there are some inconsistencies
 * status

Outcome

 * MPDL had no time to go through the specification, will do so as soon as possible

retrieve information from granted privileges

 * FIZ is preparing a concept
 * more examples Faces_Browse_and_Display, Faces_Browse_and_Display, see also some other use cases on the same page.
 * status?
 * please see concept http://colab.mpdl.mpg.de/mediawiki/ESciDoc_User_Account_Filter

Outcome

 * MPDL needs to check the concept and comment on it

OAI PMH

 * see docu: http://www.escidoc.org/JSPWiki/en/InfrastructureOaiPmh

Outcome

 * MPDL needs to check the concept and comment on it

Release date

 * status

Outcome

 * Not yet known
 * Issues with the build process

Search and Administrative searches

 * Solr - issue considered?
 * MPDL feedback for indexing scenarios
 * see new rules at Talk:PubMan_Indexing

Outcome

 * FIZ will check the concept and eventually comment
 * The concept has double purpose: to specify precisely the indexes, but also to enable standardization in creation of metadata records by MPDL solutions
 * FIZ tested the possiblity to provide a URL to the indexing component
 * it is possible
 * FIZ will provide the stylesheet
 * MPDL will be able to change the stylesheet or point to another stylesheet(via corresponding escidoc.property)
 * at the time being, the stylesheet is generic for all data
 * in future we need to work on possibility to provide an indexing stylesheet respective to the metadata schema and/or content model

LTA Aspects

 * Premis v.2
 * MPDL will provide proposal
 * Status: not yet ready

File checksum

 * File checksum calculation
 * MPDL to provide checksum scenarios

Content Model

 * see concept and definition at ESciDoc_Content_Models
 * see implementation and example object at ESciDoc_Content_Model_Object
 * Status: not yet finalized

TOC

 * discussion at ESciDoc_Toc

Ontology Manager

 * see ESciDoc_Content_Relations