ESciDoc Developer Workshop 2009-03-03

ESciDoc

Date: 03.03.2009 Start time: 14:30

Location: Karlsruhe, München (Video conference)

Participants MPDL: Wilhelm Frank, Natasa Bulatovic

Participants FIZ: Matthias Razum, Steffen Wagner, Harald Kappus

Previous workshop

 * ESciDoc_Developer_Workshop_2009-02-17

Next workshops

 * ESciDoc_Developer_Workshop_2009-03-10

=Agenda=

Main topics
NOTE: Topics where no Outcome is given have not been discussed.

Japanese Charset

 * feedback from MPDL needed

Outcome

 * MPDL will provide some more input, seems sent patch to have been overlooked, as it was mixed with the new index requirements

Shibboleth

 * Status at MPDL

Outcome

 * MPDL have set-up shibboleth, Ldap
 * integration works without problems
 * waiting for user-details attribute shib enablement to test further

Premis 2

 * concept/requirements from MPDL needed

Outcome

 * MPDL works also on related topic, will provide more info
 * Mapping of version history to Premis2 metadata important
 * Separate issue, Premis2 for ingestion/origin metadata

Filter issues and authorization

 * Discussion, reported tickets
 * http://www.escidoc.org/jira/browse/DEV-581
 * fixed in 1.0.1, 1.1
 * http://www.escidoc.org/jira/browse/DEV-584
 * fixed in 1.1
 * 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.


 * 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
 * Status Update?
 * fixed in 1.1
 * MPDL created database triggers and re-created the indexes. Also we recreated several new indexes (that fit our queries). Is FIZ interested for the code?
 * 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
 * Status update?
 * fixed in 1.1


 * Other filter issues, important for sorting criteria
 * see ESciDoc_Developer_Workshop_2008-11-18
 * sorting by author name, or source title etc.
 * see ESciDoc_Developer_Workshop_2009-01-27
 * see http://www.escidoc.org/jira/browse/DEV-624
 * see http://www.escidoc.org/jira/browse/DEV-625

Outcome

 * Tickets fixed in 1.1 should also be in the 1.0.1 bug-fix
 * Newly created tickets, regarding filters/sorting schedule communicated, see above DEV-624, DEV-625 comments in JIRA

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

 * MPDL will make a small workaround in eSciDoc Admin solution
 * password change and email-after-creation
 * need XACML policy change

SuperSuperUser / Reset Tool

 * scheduled for v1.1
 * in work

Outcome

 * will be delivered with 1.1

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
 * MPDL feedbak:
 * Concept seems fine, some questions/comments, wording were changed on the page.
 * Implementation plan?

Outcome

 * Agreed on concept

relations between organizational units
see new consistent table at
 * PubMan_Func_Spec_Organizational_Unit_Management
 * sheduled for v1.2
 * status of concept (FIZ)

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.
 * please see concept http://colab.mpdl.mpg.de/mediawiki/ESciDoc_User_Account_Filter
 * MPDL checked the concept
 * Proposal has been made that the user account filter actually allows filtering for all attributes of the grant
 * The delivery should return the xml of the grant object (NOTE: not the xacml policy)

Outcome

 * concept agreed
 * possibly the retrieveUserGrants method in the user account will have same result as current filter result

OAI PMH

 * see docu: http://www.escidoc.org/JSPWiki/en/InfrastructureOaiPmh
 * feedback from MPDL needed

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

 * MPDL agreed on automatic indexes
 * MPDL will provide FIZ with a list of compound index names
 * Further on, for new compound indexes MPDL can change the XSLT independently

LTA Aspects

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

File checksum

 * File checksum calculation
 * MPDL to provide checksum scenarios

Outcome

 * Possible to set checksum calculation on Fedora content datastream level
 * Can be done any time after file creation
 * Minimum requirement for MPDL is to have the checksum of files with release
 * MPDL will still provide concept, was only shortly cross-check

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