1 / 20

eSciDoc Community Model Draft

eSciDoc Community Model Draft. Overview. Introduction Requirements on the Community Model Organizational Aspects Open Issues / Risks Summary. 1. Introduction. Current Community Model. Pubman Early Adopters Vital Interest to use PubMan soon Help on Prioritization

kyne
Download Presentation

eSciDoc Community Model Draft

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. eSciDoc Community Model Draft

  2. Overview • Introduction • Requirements on the Community Model • Organizational Aspects • Open Issues / Risks • Summary

  3. 1. Introduction

  4. Current Community Model • Pubman Early Adopters • Vital Interest to use PubMan soon • Help on Prioritization • Provide very specific Requirements • Pubman Pilotgroup • To shape PubMan and provide Expertise • To help for PubMan dissemination • To Contribute in Functional and GUI Working Groups • Partner Institutes • Identified needs for Solutions • In Context of Research Questions • Clusters of Institutes with similar Solution Interest • Workshops and presentations at the Institutes

  5. Stakeholders • eSciDoc Project (MPG/FIZ) • Objectives within funding scope • Strong commitment beyond project funding • Organizations within the community wishing to contribute actively • Own Contributions to developments • Strategical requirements on roadmap and directions • Organizations within the community as end users • Adoption of “out of the box” solutions • Own Requirements on changes and further developments • Prospective community members for “Test Drive” Phase • HU Berlin • DANS, Netherlands • NIMS, Japan • GBV, Göttingen

  6. Timeline Closed Project “Test Drive” Community Project MPS/FIZ Community Evolving community process Fully fledged community process eSciDoc Days June 10, 2008 eSciDoc project ends July 31, 2009

  7. 2. Requirements on the Community Model

  8. Aspects of the Community Process • Build Trust • Enable for influence • Shaping a common vision • Integrate external Expertise • Include new scenarios and use cases • Benefit from experience of other key players • Sustainable Integration of other applications within relevant communities • Involvement of new Partners • Transparent process • Management of Expectations • Identify Synergies • Strengthening of the platform by re-use • Customized and low threshold Solutions • Transparent Communication

  9. Objectives for the Community Process • Four main aspects: • Common shaping of roadmap and priorities • Joint planning of Architecture and Service developments • Coordination of External Communication for further distribution • Development of the Community Process at large

  10. Development of the Community Process at large • Support and Extend the Community • Community Events • Face-to-face and virtual • Overall and discipline/solution specific • Prepare for Continuous Modifications • The Community Process should be adopted to new requirements coming up over time • Identification of unsuitable procedures to be revised

  11. 3. Organizational Aspects

  12. Possible Instruments • Special Interest Groups • Work on specific issues • Could be created on demand and could be volatile • eSciDoc Architecture Group • Keeps overview of general Architecture of Core Services and Solutions • Provides decision support for the Board • eSciDoc Board • Aligns General Directions • Decides about Proposals • Consolidates disparate Requirements

  13. SIG 1 PubMan SIG 2 Digilib SIG 3 xxx SIG 4 Standard Y SIG 5 Infrastructure Solution 1 PubMan Service 2 Digilib Solution 3 XXX eSciDoc Community Model: Option 2 Joint Roadmap eSciDoc Board provides implements Draft Resolutions interacts with Architecture Group Infrastructure XXXRoadmap PubManRoadmap DigilibRoadmap InfrastructureRoadmap Infrastructure Infrastructure

  14. SIG 1 PubMan SIG 2 Digilib SIG 3 xxx SIG 4 Standard Y SIG 5 Infrastructure Solution 1 PubMan Service 2 Digilib Solution 3 XXX eSciDoc Board eSciDoc Community Model: Option 1 Joint Roadmap Infrastructure XXXRoadmap PubManRoadmap DigilibRoadmap InfrastructureRoadmap Infrastructure Infrastructure

  15. Summary

  16. Timeline Closed Project “Test Drive” Community Project MPS/FIZ Community Evolving community process Fully fledged community process eSciDoc Days June 10, 2008 eSciDoc project ends July 31, 2009

  17. Proposals for Discussion • Invitation of one additional person into the current eSciDoc project board during Test Drive Phase • Voted by the external partners • Bi-Annual Meetings to shape Community Model • Annual eSciDoc Days

  18. Feedback from first day

  19. Topics that came up in discussion yesterday • Standards and Best Practices • Management of metadata profiles within eSciDoc • Metadata crosswalks • Content model and common standards (content model registry?) • Archival formats • Persistent identifiers • New Services • Controlled vocabulary service • Workflows • Tinyurl • Access analysis and usage statistics • Scalability and Performance • Improved authorization (combination of RBAC and XACML?) • Profiling of Infrastructure (under load) and publication of results • Demo installations (~1 million objects) • Clustering and replication • Documentation and Community Building • Unified build management and source code distribution • Community forum and mailing lists • Technical support • Instant eSciDoc (packaging) (for open source distribution) • Improved documentation (e.g., „getting started“ document) • Service Registries

  20. Thanks

More Related