ESciDoc Developer Workshop 2009-05-05

ESciDoc

Date: 05.05.2009 Start time: 14:30

Location: Karlsruhe, München (Video conference)

Participants MPDL: Wilhelm Frank, Natasa Bulatovic

Participants FIZ: Harald Kappus,

=workshop=
 * Previous workshop
 * ESciDoc_Developer_Workshop_2009-04-28


 * Next workshops
 * ESciDoc_Developer_Workshop_2009-05-12
 * ESciDoc_Developer_Workshop_2009-05-19

=Agenda=

VidConf 12.05
is going to visit the MPDL. The appointment is scheduled from 14:00 to 16:00. MPDL will not be able to use the VidConf room. Teleconf or postpone?
 * on Tuesday 12th May 2009 the Vicepresident of the MPG

Outcome
 * we stick with may 12, but start at 16:00, VidCo or TelCo or - if nothing to discuss - just skip it
 * natasa an harald wil communicat in the morning of may 12.

status v1.1 RC2

 * next build 501 on eSicDev6 / Samba

Outcome
 * MPDL will use Build 501 and replace the ear when RC2 is ready, (Wednesday or Thursday)

Open bugs

 * http://www.escidoc.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10012

VidCo on 23.6.

 * we might need to shift this Workshop
 * 24. in the afternoon? No new Info

Outcome
 * no change, Vido will be held 23.6. as usual

Release v.1.2

 * release date: August 2009
 * features: http://www.escidoc.org/jira/secure/IssueNavigator.jspa?requestId=10013

Prio 1

 * (1)assign Collaborator-modifier role to all containers in the tree below a selected container
 * (1)Handling of additional user attributes
 * we need a place to store external person ids in a user account
 * (1)Migration from v1.1 to v1.2 and related topics
 * (1)Language for Filter Methods
 * or administrative search (Solr?) other solution?
 * (1) Backup/Restore procedures productive readiness
 * see ESciDoc_Developer_Workshop_2009-03-24
 * (1) Other productive readiness issues
 * enable incremental recache/reindex (i.e. ingesting of new data should not recache/reindex complete repository)

Prio 2

 * (2)Ontology Manager+Searching within Tags
 * ESciDoc_Developer_Workshop_2008-12-02
 * Talk:ESciDoc_Content_Relations
 * Talk:ESciDoc_Content_Relations
 * (2)Surrogate objects
 * (2)Organizational Units don't need to be unique (within a parent)

Prio 3

 * (3)Content Model / Content type definition schema
 * (?)Create separate SQL scripts for user account initialization to support different needs of eSciDoc users