Public Knowledge Project:From Open Source to Community            Source     Barbara Hui, California Digital Library Brian...
Outline•   Community & Sustainability (Brian)•   Open Monograph Press (Alec)•   Development partner perspective (Barbara)•...
Open Source Community Source•   Direction & coordination•   Financial & in-kind commitments•   Organization & Governance•...
Some Challenges• Multiple development teams• Virtual collaboration• Development practices: coding, review &  integration, ...
Sponsors, Partners & Sustainability• Sponsors: 2 Platinum; 9 Gold; 7 Silver; 9 Bronze• Traditional OS contributions: Freie...
PKP Software: Releases
Open Monograph Press• First new workflow design in (5?) years• Opportunity to pioneer new structures   • Flexible roles   ...
Rust Never SleepsOJS lines of code (from ohloh.net)
Strategic / The Future• New Development Areas:  •   Open, dynamic publishing platform  •   Social networking integration &...
The PKP Partnership and            eScholarship’s future• Access to community based enhancements/solutions, e.g.   – Data ...
The PKP Partnership and       eScholarship’s future (contd)• Exponentially increased collaboration possibilities for  tack...
OJS & OMP Usability Assessment• What  • Improve the OJS and OMP user experience  • User-centered assessment and redesign p...
Usability Assessment (contd)• Challenges   • Effective communication   • Multiple work cultures   • Multiple timelines   •...
Questions?                Thanks!Barbara Hui     barbara.hui@ucop.eduBrian Owen      brian_owen@sfu.caAlec Smecher    alec...
Upcoming SlideShare
Loading in …5
×

Public Knowledge Project

778 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
778
On SlideShare
0
From Embeds
0
Number of Embeds
61
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Traditional OS models don’t work well for niche applications: smaller community, often limited technical resources, OS business models not as applicable, etc. Mention Kuali Foundation, Brad Wheeler
  • multiple development teams: already sufficient exp. with other comm.based OJS partners, e.g. Free University Berlin virtual collaboration: has always been the norm for core PKP team development practices: this dialogue has already commenced, e.g. transition to GIT local vs. community: huge potential for benefits, i.e. expertise core team doesn’t possess; re-architecting goal to modularize may allow more flexibility
  • multiple development teams: already sufficient exp. with other comm.based OJS partners, e.g. Free University Berlin virtual collaboration: has always been the norm for core PKP team development practices: this dialogue has already commenced, e.g. transition to GIT local vs. community: huge potential for benefits, i.e. expertise core team doesn’t possess; re-architecting goal to modularize may allow more flexibility
  • Dedicated development & support for all PKP modules Interoperability w. other related platforms, e.g. IRs DA1 - Open Dynamic Publishing Platform To allow for customizable implementation from a web library of modules for assembling more efficient publishing platforms involving traditional and innovative forms of scholarly communication: a) Modularization of the workflow stages in article processing and publishing.. b) Definable user roles to suit needs of different communities. c) More efficient modal interface and navigation design throughout. d) Output flexibility capable of serving up content on multiple platforms. DA2 - Social Networking Integration and Content Enrichment To enable the tracking, as well as the extension, of research ’ s reach and impact, in ways that will assist in establishing value and authority of content: a) System for assembling article-level statistics and metric based on traditional measures of citations as well as social networking and media measures. b) Plugin capacities for third-party content-management tools such as Mendeley and Zotero. c) Social networking notification tools. DA3 - Indexing and Discovery Facilitation To increase the efficiency with which research is discovered, reviewed, and utilized, as well as supporting data-mining: a) Tools to support structured tagging (XML) of (i) all content elements to enable indexing and data-mining of research methodologies, statistical techniques, captions, etc. and (ii) bibliographies for correction, improved citational accuracy, and linking out. b) Improved metadata production and quality control for published content, with author disambiguation, works cited, etc. c) Support for enhanced PDF production of published content, including metadata, linkouts, and features that keep content part of the dynamic web. DA4 - Research Data Integration and Generation To advance the use and analysis of published research through a sharing of the associated data-sets for published studies and for opening the research itself to studies through data-mining and other techniques: a) System tools for linking research data sets to articles (e.g., Dataverse). b) System tools for analysis of datasets (e.g., data visualization). c) Demonstration articles in sciences, social sciences, and humanities with well-integrated and well-structured data-sets and associated analysis tools.
  • --PKP partnership presents an opportunity to extend and grow eScholarship that wouldn’t be feasible otherwise. --PKP partnership also allows CDL to contribute back development work done over past 1.5 years (in addition to possible integration of CDL services like EZID)
  • --First example of major CDL contribution in capacity as development partners, in collaboration with another partner institution
  • Public Knowledge Project

    1. 1. Public Knowledge Project:From Open Source to Community Source Barbara Hui, California Digital Library Brian Owen, Simon Fraser University Library Alec Smecher, Public Knowledge Project
    2. 2. Outline• Community & Sustainability (Brian)• Open Monograph Press (Alec)• Development partner perspective (Barbara)• OJS & OMP Usability assessment (Barbara)
    3. 3. Open Source Community Source• Direction & coordination• Financial & in-kind commitments• Organization & Governance• Transparency• Scheduling & Milestones
    4. 4. Some Challenges• Multiple development teams• Virtual collaboration• Development practices: coding, review & integration, testing, documentation, release• Local vs. community priorities
    5. 5. Sponsors, Partners & Sustainability• Sponsors: 2 Platinum; 9 Gold; 7 Silver; 9 Bronze• Traditional OS contributions: Freie Universität BerlinDevelopment Partners:• OMP Early Adopter: Univ. of Pittsburgh• Marketing, Wordpress, Usability: UBC• Support Forum: OCUL & Scholars Portal• UI/Usability & OJS: CDL & UBC
    6. 6. PKP Software: Releases
    7. 7. Open Monograph Press• First new workflow design in (5?) years• Opportunity to pioneer new structures • Flexible roles • Multiple-file reviews • User interface• 1.0b launched in September• Adoption; stabilization; incubation; post-production
    8. 8. Rust Never SleepsOJS lines of code (from ohloh.net)
    9. 9. Strategic / The Future• New Development Areas: • Open, dynamic publishing platform • Social networking integration & content enrichment • Indexing & discovery facilitation • Research data integration & generation
    10. 10. The PKP Partnership and eScholarship’s future• Access to community based enhancements/solutions, e.g. – Data publishing modules – New peer review mechanisms and methodologies• Potential solutions to growing requests from UC researchers – Conference support -- Open Conference Systems (OCS) – Monograph publishing -- Open Monograph Press (OMP) • Non-PDF-based publishing support
    11. 11. The PKP Partnership and eScholarship’s future (contd)• Exponentially increased collaboration possibilities for tackling emerging publishing and repository needs• Opportunities to integrate valuable CDL technologies into a widely used platform (e.g. EZID)
    12. 12. OJS & OMP Usability Assessment• What • Improve the OJS and OMP user experience • User-centered assessment and redesign process• Who • Assessment: • CDL will focus on OJS • University of British Columbia will focus on OMP • Implementation: • developers from PKP, CDL, UBC (and elsewhere?), in collaboration with CDL and UBC UI/UX teams
    13. 13. Usability Assessment (contd)• Challenges • Effective communication • Multiple work cultures • Multiple timelines • Collaborative, open development• Opportunities • Shared expertise, experience, perspective, hours in the day • More robust results • Work with cool colleagues at other cool institutions!
    14. 14. Questions? Thanks!Barbara Hui barbara.hui@ucop.eduBrian Owen brian_owen@sfu.caAlec Smecher alec@smecher.bc.ca

    ×