User:Nicole/eDoc at MPDL

=eDoc at MPDL: Basic Ideas=

eDoc Policy
This collection contains material created by the MPDL Team about its services, projects and areas of activities as a scientific service unit of the Max Planck Society.

This is the default text. Every department is welcomed to extend it to their needs.

Material to be deposited

 * All material that is communicated outside the MPDL (at least one participant of the audience is a non MPDL member)
 * internal material of general interest is deposited on the MPDL share drive
 * All sensitive data has to be removed (staffing, business internals etc.)

Access Levels

 * Original version: 	Institute level access
 * PDF version:		MPG wide access or Public access

Publication with multiple authorship

 * To be only deposited in the collection of the corresponding author (who is named first).

Copyright
Use of the "German Creative Commons Licences by" (CC by) http://i.creativecommons.org/l/by/3.0/88x31.png is strongly recommended by Laurent.

Keywords/Classification
Under discussion if there should be keywords/classification for the MPDL or not. The information provision department is working on a keyword list for their department.

Collections

 * Research and Development
 * German e-Science Conference
 * Information Provision
 * Staff

Affiliations

 * Max Planck Digital Library
 * Staff
 * Press and Public Relations
 * Project Coordination
 * Metadata, Interoperability
 * Open Access Policy
 * Digital Collections
 * Research and Development
 * Software Development
 * User Interface Engineering
 * Digital Editions
 * Service Management
 * Information Provision
 * User Interfaces (“Zugangssysteme”)
 * Information Management
 * Information Resources
 * German e-Science Conference

Functions
Staff

Moderator:	all

Manager:	?

Authority:	Laurent Romary

R&D

Moderator:	Katrin Gashi (substitute: ?)

Manager:	?

Authority:	Laurent Romary

Information Provision

Moderator:	Maggie Schinner (substitute: Tina Planck)

Manager:	Günter Schönfeldt

Authority:	Laurent Romary

Workflow for Staff

 * each stab member is requested to enter his/her publication data in eDoc himself/herself.
 * each stab member is responsible for the formal quality assurance of his/her publication data. Therefore each stab member has moderator rights and should tick the box "accepted".
 * each stab member has to make sure that no duplicates of his/her publication data exist in eDoc (to check all collections of MPDL). In case there is a duplicate and duplicate is stored in the collection of Information Provision or Research and Development but belongs to the collection of the stab, one has to get in touch with the Moderators of R&D or ScIP for deletion.

Workflow for R&D

 * The Moderator enters data for all members and accepts the entry.
 * The Moderator is responsible to recommend entries for the Yearbook.
 * If someone within the team is interested in entering his/her own data s/he can get an account as MetaData-Editor to enter and change the data. Afterwards the moderator will check the entries and accept them if they are fine.
 * The Moderator has to make sure that no duplicates of publication data exist in eDoc (to check all collections of MPDL). In case there is a duplicate and duplicate is stored in the collection of Information Provision or Stab but belongs to the collection of R&D, one has to get in touch with ScIP-moderator or the corresponding Stab member for deletion.
 * Moderator view should be checked on a regular basis. If new entries are generated and ready for authorization, a reminder should be sent per mail to Authority, to let him know that it is ready for his last check.

Workflow for Information Provision (ScIP)

 * Each ScIP member is requested to enter his/her publication data in eDoc himself/herself.
 * Afterwards the moderator will check the entries and accept them if they are fine.
 * The Moderator is responsible to recommend entries for the Yearbook.
 * Each member has to make sure that no duplicates of publication data exist in eDoc (to check all collections of MPDL).
 * The Moderator view should be checked on a regular basis. If new entries are generated and ready for acceptance, a reminder should be sent per mail to Authority to let him know that it is ready for his last check.