Difference between revisions of "Portal:PubMan"

From MPDLMediaWiki
Jump to navigation Jump to search
(→‎Basic concepts: internal link corrected)
Line 15: Line 15:
For proper design of the solution and its features and alignment with conditions applied to other services, you find here an overview of our basic functional concepts.
For proper design of the solution and its features and alignment with conditions applied to other services, you find here an overview of our basic functional concepts.
* [[PubMan_Versioning|Versioning]]
* [[PubMan_Versioning|Versioning]]
* [[ControlledVocab|Controlled vocabulary]]
* [[Control_of_Named_Entities|Control of Named Entities]]
* [[PubMan_PID|Persistent Identification]]
* [[PubMan_PID|Persistent Identification]]
* [[PubMan_Collections_and_Organizational_Units|Collections and Organizational Units]]
* [[PubMan_Collections_and_Organizational_Units|Collections and Organizational Units]]

Revision as of 09:14, 17 April 2008

eSciDoc Solutions

PubMan:
Overview · Functionalities
Interfaces · Support

Faces:
Overview · Functionalities
Scope · Support

ViRR:
Overview · Functionalities
Scope · Support

imeji
Digitization Lifecycle

edit

Solution for Publication Management: PubMan supports scientists and institutes in the management and the digital curation of their publications. This solution addresses all disciplines and focuses on the target groups scientists, local librarians and local IT. Due to the heterogeneous policies, cultures and workflows of the Max-Planck-Institutes, customization and configuration options throughout the solution features are of major importance.

PubMan is the working title for this solution. Everybody is welcomed to suggest alternatives on the discussion page.

Basic functionalities[edit]

For better overview, we divide the basic functionalities of the repository into three main areas of interaction with users and/or systems:

Basic concepts[edit]

For proper design of the solution and its features and alignment with conditions applied to other services, you find here an overview of our basic functional concepts.

Non-functional requirements[edit]

  • The client application has to be web browser based.
  • The system has to support multiple languages.
  • The initial languages are English and German.
  • All Data are stored in UTF 8.
  • All web pages have to support 'heat maps' to track mouse clicks. An apache webserver must be installed. PHP must be installed with the graphic library GD (PNG support is mandatory). ClickHeat version 1.2 (http://www.labsmedia.com/clickheat/index.html) has to be installed. The All pages generated by escidoc must contain javascript code to track mouse click events.