MPDL AB Meeting 2009-08-19

MPDL  Restricted Access to MPDL
 * Participants: Michael Franke, Ulla Tschida, Wilhelm Frank, Gergana Stoyanova

Previous meeting

 * MPDL_AB_Meeting_2009-08-14

Assumptions

 * Trunk PubMan will be extended for ClusterJus
 * no separate Jus PubMan instance needed for fulfilling requirements
 * Assumption based on Overview by Michael on pro/contra for
 * one development trunk
 * separate instance, but one trunk
 * separate development

Current Specification and Input
Gergana prepared detailed specification on functional metadata sets needed, see [| detailed Spec]

In addition, she prepared an overview on new publication types needed, compared to current escidoc types, see here

A first overview on AA-issues (OAuth vs Shib) is also available (thanks Gergana)

Proposal for design in PubMan

 * Jus-specific Labels/Helptexts can be defined by user preferences
 * Jus-specific validation rules will be defined in their contexts
 * JUS can define their own genre-specific entry mask, which can be different to core PubMan entry mask. In addition, values for the drop-down lists will be defined in the genre-specific table.
 * this is true, right?--Ulla 11:06, 24 August 2009 (UTC)
 * --Gergana 11:23, 24 August 2009 (UTC) As far as I understood we can not change the order in the entry masks (Rupert told me this). But we can choose which fields to show, right?
 * Jus metadata will be stored in additional metadata record
 * Background: Three options for Genre handling are available:
 * just add new Jus-types to current escidoc types. Easy, but not sustainable and no generic feature.
 * Define discipline-specific Sub-Types for default eSciDoc Types, which inherites the metadata from parent type. Not feasible, might lead ot difficulties when semantic differences. In addition,not generic enough for other discipline-specifics to come.
 * Add discipline-specific record to the main escidoc record. Has advantage of being generic enough for any discipline-specifics to come, e.g. for Linguistic Literature - GeoCodes. Each item has at least escidoc record, optionally in addition a discipline-specific record. The DC Metadata are generated from escidoc record. Both records are indexed.

We checked this approach by commenting on the questions from last meeting

Outcome

 * Metadata
 * no Metadata extension necessary. Court info will be stored in source record
 * Subtitle and short title for citing of journals needed. Include in CONE also short title of journal for the autosuggest.
 * genre specific labels / helptexts
 * genre specific configuration has to be extended and made context sensitive
 * Cluster JUS will have own config file with their own entries
 * Gergana will do some research and testing for this
 * PubMan methods for message / label / tooltip reading has to be extended


 * Validation rules
 * no architectural change bcs they are already context sensitive
 * ClusterJUS has to take care for correct validation rules

Open Questions

 * Based on assumption, that we have separate record for discipline-specific metadata...what are consequences on
 * quick search
 * advanced search
 * view item version