MPDL AB Meeting 2009-08-06

MPDL  Restricted Access to MPDL
 * Participants:Thomas Endres, Michael Franke, Tobias Schraut, Wilhelm Frank, Julia Kurt, Gergana Stoyanova, Ulla

Previous meeting

 * MPDL_AB_Meeting_2009-07-20

Overview JusCMS
Zusammenfassung Anforderungen
 * General purpose and requirements of the project
 * relevant pages:

Zuordnung der Anforderungen an PubMan und Contens

Architekturkonzept


 * Short presentation of current status by Gergana


 * Urgent open issues for Ulla:
 * Possibility to set specific DC:subject class as user preference?
 * Requirement not relevant any longer. (Feedback Gergana).
 * Possibility to change order of steps/groups/fields in Easy and Full submission?
 * GUI table for ClusterJus will include specific doc-types and MDs, but no possibilities to change order of steps/groups/fields!
 * Possibility for jus-specific GUI/lables for e.g. Export lable?
 * In general no. But alternative a): pro context kann spezifische lables definiert werden, gelten dann aber für alle user, die ein item aus diesem context aufrufen. alternative b): have separate instance of PubMan core and change resource bundle for local instance accordingly. Final decision depends on Design and pro/contra lists for having local instances. (TBD in technical workshop 7th sept)
 * Possibility for jus-specific Help-Texts? E.g. in field edition include also instalment: 3.Auflage, 4.Lieferung.
 * Final decision depends on Design and pro/contra lists for having local instances. (TBD in technical workshop 7th sept)
 * Possibilty to split groups in the GUI, but has the same type in backend: e.g. as Publication-Type Handbook and Collected Edition in the Pull-Down for Publication Type, but the item will be stored only as Collected Edition. No need for retrieving of Handbook, because it will be fetched in a group (see JUS-specific groups below).
 * separate document types should be stored separately.
 * When delivering PubMan XML via Rest for JUS-specific groups (currently 9 groups: Herausgeberschaften, Monographien und andere selbstständige Publikationen, Aufsätze etc.. Examples)=> do we deliver the JUSCMS-Genre Type? (I assume yes)... see Gerganas table
 * JUS specific document types will be stored separately in PubMan and can be delivered separately.
 * Relevant preselection of values for every publication type? E.g. for journal article only a journal can be a source, no Pull-down is needed. The same case we have for role (one or two roles), Identifier and some dates.
 * Depends on final design. GUI Types müsssen erhalten bleiben (e.g. Pulldown bleibt Pulldown), aber default Einstellungen sind möglich.
 * Is this a correct assumption for Contens-task?: Contens needs to store the time stamp of the last query for each page, to be able to get a list of added/modified items back (i.e. based on pubman system date ). Details should be discussed at 2nd of september telco.
 * Is this correct assumption? The language flags needed for specific MD fields (cf Gergana) is this already specified by Gergana, incl. ) need to be implemented again. Contens needs to interpret these language flags (i.e. controlled list of language values). Language flags for specific PubMan fields will then offered on core pubman, can be "switched on/off".
 * Local Tags:
 * depositor as well as moderator is able to specify local tags
 * possibility for automatic grant of local tags? => theoretically possible. Final check of Yearbook implementation when institutes go productive.
 * limited number of local tags per item? no
 * limited number of characters for local tags? no
 * Abstract: number of characters? When the abstract is longer than X signs, then upload the file.
 * field not limited.
 * IP-Range for file access possible? E.g. every PC from the institute-network can read the file.
 * Depends on LDAP..still unclear, how/if possible.

Next Steps JusCMS

 * 2nd september videotelco@MPDL:
 * finalize requirements
 * crosscheck architectural concept and questions
 * JIRA how-to
 * preparations for Heidelberg workshop
 * Preparation of technical meeting in Heidelberg on 7th Septembre
 * provide sample XML file of Pubman item (rich one)
 * local installations - pro/contra
 * Explain difference of local installations and separate development tracks
 * LDAP/Shib vs OAuth
 * Presentation architectural concept
 * Explain our concept of testing enviroments (our testing instances/interfaces, possible link to contens 3.0. test instances)
 * Presentation of 3 challenges: during submission, during search, define per context

ToDos for MPI PL

 * namespace changes in R6
 * MPI PL: change scripts for website feeds
 * postponed