PubMan Going Productive

MPDL this is under preparation;-) ...thanks!

Phase 1 - Milestone BT (May 2009)

 * includes all Must-A criteria defined
 * some aspects will be communicated at BT
 * complete list of enduser features planned for R5 not included (see JIRA for details)

User administration
Extension Admin solution
 * incl. automatic mail after creation account, change PW link, policy link (http://zim01.gwdg.de:8080/browse/ADM-27, http://zim01.gwdg.de:8080/browse/ADM-28)

Role concept (access rights, workflows)

 * clear list of roles supported by PubMan (see http://colab.mpdl.mpg.de/mediawiki/ESciDoc_Access_Rights )
 * clear description of workflows supported by PubMan (see http://colab.mpdl.mpg.de/mediawiki/PubMan_Action_Matrix )

General admin functions for the solution

 * Check usage of Nagios@GWDG

Google/google scholar

 * released Publications and Researcher portfolios
 * if the researcher portfolio should be indexed by google including the list of publications, the current mechanism to include publications via an ajax call can not be used.--Robert 20:04, 23 March 2009 (UTC)

Feature stability
Outsource citation style manager to available server@gwdg see (http://zim01.gwdg.de:8080/browse/AS-729)

Provision of delaying request for search&export (see http://zim01.gwdg.de:8080/browse/AS-730 )

Enduser documentation
Online help up-to-date

Support page on CoLab, incl. mailinglist pubman-support

Screencast up-to-date

Back-up system
current back-up procedures to be extended (see http://zim01.gwdg.de:8080/browse/AS-731)

Performance&Scalability goals
Support PubMan Workshop@BT:
 * 15 concurrent users
 * max 3 seconds response time
 * see http://zim01.gwdg.de:8080/browse/AS-732

http://www.useit.com/papers/responsetime.html may be a helpful guideline here.--Robert 09:33, 24 March 2009 (UTC)

Browser compatibility
Minimum set to be supported: FF2, FF3, IE6, IE7, Safari3
 * Level of support: user can work properly, "cosmetics" to be ignored
 * toDo: change Doc Type from XHTML to HTML 4.1 transitional

Policy for Bugfix release for R5
Decision on Priority by Nicole and N.N.(dev-team)
 * Critical bugs to be crosschecked by Ulla and/or Natasa
 * In case of doubt, final decision Malte

Showstoppers/must-fix:
 * Log-in fails
 * Submission fails
 * Modification fails
 * Search fails
 * Export fails

Server maintenance
Minimum: 99,8% availability, i.e. maximal annual downtime (incl. updates, regular releases): 18h
 * Aim for: 99,9% availability, i.e. maximal annual downtime: 9h
 * Maximal un-planned downtime : 9-16 h/year (tbd by AB team)
 * urgent bug fixes, hot fixes not included
 * do these downtimes only refer to the PubMan solution, i.e. downtimes of the complete machine for maintenance are included?--Robert 20:12, 23 March 2009 (UTC)

1 SvM, 1 Dev as permanent contact for GWDG: Nicole (Juliane), Tom (Tobi)
 * In case of downtimes, communication to Malte, Natasa, Ulla
 * In case of downtimes, switching/information for user on startpage ("We are currently down...")
 * see http://zim01.gwdg.de:8080/browse/AS-734, http://zim01.gwdg.de:8080/browse/AS-733
 * does this mean that only pubman is expected to be down, but apache still running - or would the traffic have to be routed to a different machine?--Robert 20:12, 23 March 2009 (UTC)
 * Provide possibility to read-only access
 * see http://zim01.gwdg.de:8080/browse/AS-735

All conditions to be agreed with GWDG


 * i think these numbers are unrealistic. trying to guarantee an uptime of 99.8% would imply being able to react to problems every single day of the week - which is impossible with our working hours. so maybe 99.2% may be more realistic.--Robert 06:48, 24 March 2009 (UTC)

Log file anonymization
Anonymization of IP addresses by removing the last octet in Apache and JBoss log files
 * Crosscheck before what needs to be considered for statistical services
 * Might be extended due to PubMan Repository Policy, data privacy

PubMan Repository Policies
HTML page in german (english), to be linked from Main menu

"easy-to-understand" human-readable text, focus on endusers

Will cover:
 * Responsibilities MPG, MPDL and institutes
 * Purpose of repository
 * Content - what is contained/not contained
 * Submission - who can submit and how
 * Preservation - when/how long accessible
 * Rights/Legal issues - How can you use, incl. data privacy issues
 * Access - who can access how

Support Coverage

 * For enduser
 * first level support (can be solved immediately): Nicole, Juliane, HiWis?
 * second level support (needs background work): Nicole, Juliane, Melanie
 * third level support (needs new project): Ulla, N.N.
 * Technical
 * first level support:
 * second level support:
 * third level support:
 * Core times support: Monday to Thursday 9-15, Fri 9-14
 * at least one of first level has to be available
 * Install automatic telephone chain: Nicole => Juliane => Melanie=> Ulla
 * was canceled--Ulla 07:34, 9 April 2009 (UTC)
 * Install Answering machine texts
 * Support Channels
 * Mailinglists: pubman-support (enduser), escidoc-dev-ext (technical)
 * Complementary public Jira web-form for submitting requests on PubMan Main menu(separate JIRA project)
 * Main contact to public, to filter incoming requests: Nicole (Juliane), to filter bugs, improvements, new requirements, new projects
 * Requests for installation support to be delegated to FIZ (MPDL pays FIZ for installing/supporting at MPIs)

Trainings, Workshops

 * regular PubMan Days (half day presentation, half day hands-on) min. twice a year
 * additional 3 days a year for regional cluster trainings
 * Workshops, Hands-on training (for migration candidates or institutes decided to use live) on demand

Phase 2 - Milestone eSciDoc Days (June 2009)

 * includes all Must-B criteria defined
 * might be re-prioritized after BT

Feature readiness

 * User administration
 * LDAP server set up
 * Data interoperability
 * OAI-PMH, RSS
 * Leftovers from original scope R5
 * to be prioritized before eSciDoc Days
 * see below Leftovers
 * Statistics service
 * NIMS requirements
 * Open Source documentation
 * community support&documentation

Technical readiness

 * Performance&Scalability goals
 * create testbed (e.g. JMeter) to evaluate current behavior

Organisational readiness

 * Policy for Bug-fix releases
 * to be communicated to community
 * Review of quality of internal processes
 * Permanent service monitoring
 * Regular log file analysis
 * PubMan Repository Policies
 * machine-readable, configurable policies(?)


 * Check third-party OS licenses

Phase 3 - further maintenance/development PubMan
List of enduser and technical features to
 * shape next releases
 * estimation on necessary resources
 * MPDL projects for PubMan extensions not mentioned
 * NIMS phase 2 not mentioned

Leftovers R5

 * administrative search
 * Institutional Visibility
 * Collaboration
 * Checksum for components

Improvements existing features

 * MPG citation style
 * additional cone entities (PACS for subject)
 * Manage cone entities (journals, persons)
 * policy
 * workflow? privileges
 * Improvements standard workflow (without workflow engine)
 * Issues from Karin will be collected here
 * save basket for user
 * New rule local admin/admin interface for users
 * Format policy eSciDoc (supported, known, unknown formats)see http://zim01.gwdg.de:8080/browse/AS-108
 * Extension statistical reports (incl. export statistics to CSV)
 * Statistical data for OA
 * Feed PubMan data to edoc Yearbook
 * Forgotten PW function
 * UTF-8 and ASCII support for BibTex
 * customizable Look&feel for GUI
 * Multiple sorting
 * improvement of GUI for current revisions (chronological order of revisions, highlight OA revisions)
 * extend relations (is part of, is related to, ...)
 * default item template on context level (see Future development Submission)
 * Export (more formats, set limit) (see Future development Export)
 * Change/define order of organizational units in org unit search
 * Improve researcher portfolio (see Future Development RPF)
 * Extend import/export for TEI
 * TEI mapping is done
 * Deposit of TEI possible with SWORD interface
 * Improve COinS support for references
 * Improve view item version (see Future Development for view item version)
 * Citation service
 * Fetch MEtadata, fetch DOI from CrossRef (usage is clarified and fine with CrossRef)

New features

 * Browse by ... (people, authors, users, title, date)
 * Yearbook on PubMan
 * New workflows (incl. workspaces) with workflow engine
 * User preferences
 * Duplicate checks and handling cross-org units
 * GUI to define local-specific genre-specific masks
 * Concept integration DCAP
 * Concept data internationalization
 * Suppport Mark-up types for some metadata (in search, display, submission)
 * Versioning Metadata profile
 * Messaging system
 * Administrative Reports (e.g. on usage)
 * Entry points for specific org unit
 * Monitoring function for specific pubman items, for selected external sources (e.g. alert when new version on arxiv)
 * Concept integration PubMan data into library catalogs
 * Integrate SFX service for MPG users
 * Integrate look-up for article in an OpenURL resolver registry (for any user)
 * Expert search (one field, supporting "Klammerausdrücke")
 * Automatic MD extraction from uploaded file
 * Virus check for uploaded file
 * Request copy feature for restricted files
 * Extraction References/Citations from fulltext and visualize
 * Attract Researcher
 * Interface to twitter and facebook
 * Integration of mention-it
 * 'Most popular publications' on homepage (retrieved via item retrieval statistics)
 * Enable discussion/ commenting of publications (idea: enable to create a blog entry in the pubman blog (special category) with the publication. Here everyone can comment).

Maintenance

 * bug fixes
 * essencial requirements of new migration candidates (can only migrate if...)
 * Customizable Endnote import for other productive users
 * new genre types (on demand)

Development
(Input: preprint at preprint-Cito for a description of CiTO, and see Figure 8 of  David Shotton, Katie Portwin, Graham Klyne and Alistair Miles (2009) Adventures in semantic publishing: exemplar semantic enhancements of a research article. /PLoS Computational Biology/ *5* (4): e1000361./ Article with citation typing ontology for an example of its use.  The ontology itself is available at  Cito ontology - this is very much a work in progress. )
 * research portfolio of a user in RDF (Foaf) see also rdf-cheatsheet
 * extending publications with references
 * ideas you may get by using the citation typing ontology or somewhere else
 * extending publications with references (input from Gergana) (ideas you may get by using the citation typing ontology or somewhere else)

(in this case, cone references would be great, as CONE is already RDF)
 * exporting/ exposing resources (Items ) in RDF and OAI-ORE formats (respective changes can be additionally considered for OAI-PMH syndication manager, Search&Exporting)

thus natively => Faces extension towards collaborative workspace for media, images, documents (linking to pubman or elsewhere) (i.e. when Face etc.
 * Generic metadata editor (Faces extension)


 * Admin solution (domain specific extensions e.g. Pubman, Faces, Virr)..
 * IDP
 * self registration
 * request privileges ...


 * establishing notification mechanisms via various non-PubMan channels
 * RSS feeds
 * automatic emailing (in specified frequency) on latest releases
 * additional blog for PubMan releases (groups: publication date, institute affiliation) with links to PubMan Item views - this would allow for posting comments directly on the blog pages (natively, this can come also as Institute specific blog)