ESciDoc Developer Workshop 2008-05-27

ESciDoc  Restricted Access to eSciDoc group

Date: May 29.05.2008

Location: Karlsruhe, München (Video conference)

Participants MPDL: Natasa Bulatovic, Wilhelm Frank

Participants FIZ: Frank Schwichtenberg, Harald Kappus, Michael Schneider

Start time: 14:00 28.05.2008

=Agenda=

Remove some methods
we would like to disable the following methods: Outcome MPDL uses some of them but will replace them the methods will be disabled in the next developer build (this week)
 * retrieveItemRefs
 * retrieveContainerRefs
 * retrieveMemberRefs
 * retrieveOrganizationalUnitRefs

Status and related message
For withdraw comment see ESciDoc_Withdraw_Comment.

see Issue 528 and 525 http://www.escidoc-project.de/issueManagement/show_bug.cgi?id=528 http://www.escidoc-project.de/issueManagement/show_bug.cgi?id=525

Outcome a solution was derived and will be part of the next stable build
 * see http://colab.mpdl.mpg.de/mediawiki/ESciDoc_Withdraw_Comment
 * the related changes of the XSDs should be done imediatelly to be part of the next developer build
 * the enhacement itself will come after that build

Update methods

 * allow for client to provide update comment (not mandatory)

Outcome it's important, but there are a lot of problems to be solved before development can start. It should be discussed on a colab-page

Descriptive metadata in Component

 * What happpens with the metadata in the component if an item is withdrawn? Are they visible or not?
 * Because only components binary content is restricted if withdrawn, the component metadata are visible in the current implementation. Frank 13:37, 13 May 2008 (CEST)


 * See input on ESciDoc_Withdraw_Comment


 * Discuss if it makes sense to deliver component metadata within item.xml or only component properties for each component.
 * eSciDoc metadata record of the component should have the metadata as described at http://colab.mpdl.mpg.de/mediawiki/Talk:PubMan_File_Properties#Outcome. TODO: check if file-size is provided by the FW during retrieval or not (not necessarily to be stored as extra metadata in that case). Metadata schema will be provided during the week.

Outcome
 * MPDL will provide the schema during the week

Technical metadata in Component

 * consider automatic creation of technical metadata for the component if the format is one of supported JHove service formats.--Natasa 13:30, 28 May 2008 (CEST)

Outcome
 * right now there is a stand-alone service which uses JOVE to create such matadata it is NOT integrated in OM up to now this will come later
 * the technical metadata should be created in the infrastructure on "create" and "update" of binary data
 * FIZ will start a colab page containing the existing information
 * MPDL will comment and specify which metadata should be used

Release R3 PubMan
We would actually have some serious points to help us deliver the R3 to the pilots (those can be actually part of the agenda):

- 0.159 patch for:


 * UTF-8 updates (http://www.escidoc-project.de/issueManagement/show_bug.cgi?id=524)
 * component visibility =private (ticket in Bugzilla) (http://www.escidoc-project.de/issueManagement/show_bug.cgi?id=500)
 * component add/remove when item is released (http://www.escidoc-project.de/issueManagement/show_bug.cgi?id=502)
 * component removal (older versions broken) http://www.escidoc-project.de/issueManagement/show_bug.cgi?id=488

So far these are important issues, because we are offering these features and version history preview, item logs to the users.

Status: Solved with patch. 'Status update: One ticket re-opened, see http://www.escidoc-project.de/issueManagement/show_bug.cgi?id=521 - was not originally on the list of these bugs as it seemed to came-in again with the patch :).--Natasa 12:48, 26 May 2008 (CEST)

Outcome
 * all bugs are fixed

usage of builds

 * future usage of beta and developer builds at MPDL
 * problem with bugfixes for not current builds
 * not certain if this is the problem indeed and if we should discuss it in detail. The bug-fixes were important as the complete schemas in the FW have been changed. We were not able to deliver a solution release that is incorporating new schema changes and additional functionalities. As both sides hope schemas will have no dramatical change in next year or two probably is not a bigger issue. --Natasa 12:51, 26 May 2008 (CEST)

Outcome
 * for starting the new development, MPDL will use the lates available developer build by end of this week or start of next week
 * after that build MPDL will allways upgrade to a new stable release as long as no big changes in XSDs take place
 * in between MPDL will use developer builds if needed

Proposals for Further Topics

 * LTA and Premis metadata

Ouptcome MPDL will check and provide a draft using premis 2