MPDL AB Meeting 2009-01-29

MPDL  Restricted Access to MPDL

=Agenda=
 * Date: 29.01.2008
 * Participants: Natasa Bulatovic, Thomas Endres, Michael Franke, Tobias Schraut, Wilhelm Frank, Bastien Saquet, Markus Haarländer, Friederike Kleinfercher

Statistical data records

 * agree on schemas
 * check also: Talk:PubMan_Statistics and PubMan_Statistics
 * check also: Faces_Statistics
 * Bastien/Markus to provide some more input on current implementation (Bastien will also provide input for scope definitions)
 * Willy to check with Kristina if there are thoughts on Virr statistics

Outcome

 * New requirements bring to more complexity and data that need to be tracked for usage statistics
 * new statistical record for search criteria (check on alternative of: all search criteria in one record vs. record for each search criteria)
 * each solution/service may track own statistics
 * search&output service may track statistical data on its own in addition to statistical data tracked via PubMan
 * IP data are needed until land information
 * Statistics per OU, Persons - as an item can be associated with more than single OU / Persons we have talked of several alternatives:
 * each combination in separate statistical record (as many statistical records as persons in item)
 * all somehow in one statistical record
 * check the possibilty to aggregate aggregations
 * writing of statistical data should be changed to asynchronous in next release
 * Bastien&MarkusH will prepare for code discussion in 2 weeks

Cone service new requirements

 * move Persons back to escidoc repos?

Solution development

 * discussion on pubman deployment and how to approach it
 * discussion on solution properties and how to approach it
 * discussion on service locator issue and how to approach it
 * discussion on development of own policy templates and checking the possibilities to define policies on our own
 * background: more roles coming up with further solution developments

Outcome

 * First priority: deployment (of PubMan and FW on one JBoss)) and how to approach it (Check startup routines of services)
 * Second priority: properties and service locator
 * Policies will be approached at a later stage. Current solution with FIZ is sufficient.

Genre-specific mapping

 * discussion on re-setting, import problems
 * add extra attribute to hold the name of the class property of PubMan metadata set class in the XML configuration file may help?

Outcome:

 * Property binding will be done with extra attributes in XML configuration (default section)
 * Logic will be applied before save (switching away and back to a genre will not remove data)
 * import not in 4.1

Definition of TODOs

 * scope: until March 2009