notebook.community

Edit and run

![Imagine the books you were looking for in the library actually glowed!](images/Library-shelves-bibliographies-Graz.jpg) [Source](https://commons.wikimedia.org/wiki/File:Library-shelves-bibliographies-Graz.jpg)
_"A fact is only as reliable as the ability to source that fact, and the ability to weigh carefully that source."_ [\[1\]](https://meta.wikimedia.org/wiki/WikiScholar#Motivation)
Introductions
What perspectives are in the room?
  • Raise your hand if:
    • You are familiar with (wiki world):
      • Wikipedia ;)
      • WikiSource
      • Wikimedia Commons
      • WikiData
      • Labs
      • Scholarly publishing generally
      • Open Access academic literature
    • You know about Open Access
    • You have heard about the OA-Signalling project
    • You are a member of WikiProject Open Access
    • You have heard of Wikiproject Open Access
    • You have a working knowledge of (technical stuff):
      • MediaWiki (wiki software)
      • Bots for Wikipedia, other Wikimedia projects (various wares)
      • Python (programming language)
      • PyWikiBot (python library)
      • XSLT (xml style templating)
      • JATS (NLM xml format)
WikiProject Open Access [\[1\]](https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Open_Access)

Goals

  1. Improve Wikimedia content with the help of Open Access materials.
  2. Improve coverage of Open Access and related topics.

[Source](https://commons.wikimedia.org/wiki/File:PhD_Comics_Open_Access_Week_2012.ogv)
[Source](https://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg)
Signalling Open Access References [\[1\]](https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Open_Access/Signalling_OA-ness)
![In a Nutshell sample of reference signals](images/oa-signalling_in-a-nutshell_screenshot.png) [OA-Signalling Project](https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Open_Access/Signalling_OA-ness) under WikiProject Open Access
ⓐ
What's the _problem?_

Managing Citations is Hard!

Cultural Norm is to Make Knowledge (and Sources) Scarce

What are _solutions_ (past & present)?

Reference Management

  • Templates (Many wikis)
  • Categories (Many wikis)
  • Namespace (French Wikipedia)
  • WikiScholar (Closed project proposal)
  • New VisualEditor with Zotero (Open question)

Open Access (to Knowledge)

  • WikiSource open to Open Access literature
  • CitationBot, {{cite-doi}}
Opportunities (more than solutions)

Re-open the "reference management" thread

Integrate with Wikidata

Forge deep knowledge resources, with full source content

Automate, and use human judgement





In [1]:



    


from IPython.display import IFrame
IFrame('http://www.wikidata.org/wiki/Help:Sources', width='100%', height=600)



    


















    
Out[1]:
Visions of the Future

Imagine a world where...

  • Adding references (even across projects) is very easy and even pleasurable
  • The Wikipedia corpus is deep, with many source content for cited texts, along with summary content.
    • "Open Access" all the way down!
  • We don't need icons or "signals" any more. Because it's clear, by default.




In [8]:



    


%load https://raw.githubusercontent.com/wiki/wpoa/OA-signalling/data-flow.md
Data Flow

Data Sources

  1. PMC
  2. Crossref
  3. Undetermined sources:
    1. OA button
    2. OCLC
    3. ImpactStory
  4. Wikipedia:
    1. Most cited journals on enwp
    2. Most cited articles on enwp

Wikimedia Projects

  1. Wikimedia Commons
  2. Wikisources
    1. Primarily English language.
    2. Identify the 1000 most cited articles on enwp, import the suitably licensed ones into enws
  3. WikiData
  4. Wikipedias
    1. Especially English language.
    2. Eventually, all ;)
  5. WikiTech (for bots/tools)
    1. Including Wikimedia Labs (virtual private servers).
    2. Including Wikimedia Tool Labs

Phase 1

  1. Import media files from PMC to Wikimedia Commons
    1. Will eventually trigger a record in Wikidata, but not now.
    2. Add relevant categories to media files.
  2. Import full text content from PMC to Wikisource (or equivalent)
    1. Wikisource item submission will automatically (in a delay) create a record in Wikidata
    2. Embed article media from Wikimedia Commons.
  3. Import article license data from CrossRef to Wikidata.
    1. Consider verifying CrossRef license data against PMC license data (flag inconsistencies).
  4. Bots run from Wikimedia Labs servers on English Wikipedia to:
    1. Implement Cite DOI templates
    2. Signal license in template
    3. Signal content in template from:
      1. Wikisource
      2. Wikimedia Commons
      3. Wikidata
    4. Link to third party services in template to:
      1. OA Button
      2. ImpactStory
      3. PeerLibrary
      4. OCLC

Phase 2

  1. When importing media files to Wikimedia Commons, check consistency and formatting of article meta data from CrossRef.
  2. Check metadata between Wikimedia Commons files and WikiData records.
  3. Expand bots to run on all language Wikipedias.
  4. Include more experimental components to the Wikipedia cite template, such as dependent on services run on Wikimedia Labs servers:
    1. E.g. alt-metrics




In [11]:



    


%load https://raw.githubusercontent.com/wiki/wpoa/OA-signalling/timeline.md
Timeline

Working within the following general timeline, to give this project better context / scope:

  • Months 1-6: Phase 1 - development, prototype, community engagement, early implementation.
  • 6th month: Wikimania!
  • Year 1+: Phase 1 + Phase 2, more proposals, funding, coordination
  • Years 1-5: More projects, funding, partnerships, independent development
  • Years 5-10: WikiData & All Wikipedias, etc.




In [12]:



    


%load https://raw.githubusercontent.com/wiki/wpoa/OA-signalling/schedule.md
Schedule

Setting particular tasks, time estimates, and corresponding milestones that works within the timeline.

Milestones

See project milestones here: https://github.com/Daniel-Mietchen/OA-signalling/issues/milestones

For a "nutshell" quick-view of progress, see the following:

  • [In-progress] Parse & Import from PMC (test articles)
  • [In-progress] OA Button Gadget
  • [In-progress] Citation Usage Data
  • [In-progress] CrossRef Proposal
  • [Start] New Bot (License & Citation)

Events

Reports

Timeline for giving concrete reports of progress on discrete milestones and on community engagements, especially with various Wikimedia projects and other stakeholders.

  • 6/2 - Report 1 - Post-WikiConference USA
  • 7/19 - Report 2 - Post-Open Knowledge Festival
  • 8/11 - Report 3 - Post-WikiMania
Next Steps

You

Us

  • We'll build our bot and grow our community!

Thank You

@wrought @notconfusing





In [5]:



    


%load presentation_notes.md

WikiProject Open Access - OA Signalling

Presentation organized for 2014 WikiConference USA in New York City, New York.

Format

  • Hopefully written in markdown or similar plain-text, html-compatible format
  • Presented using iPython Notebook, or some other web-based alternative. ** PDF fall-back is wise based on constraints of presentation room projector/computer.

Outcomes

Not absolutes, but setting scope of expectations for the parties involved

Attendees / Participants

  • Basics
    • Learn the history and basics about WikiProject Open Access and the OA Signalling project.
      • Know the definition of Open Access
      • Know how open access, the wikiproject, and the signalling project all fit in to the context of Wikipedia
    • Become familiar with current demonstration of signalling under "In a Nutshell" section of project page on WP.
  • Status and Roadmap
    • Be able to summarize the current status of the project.
    • Review the currently planned flow of information, and how to work with existing communities to make it happen.
    • Have an understanding of the general roadmap, including timeline/schedule and longer-term goals, for the project.
  • Participation Paths
    • Learn the clear ways to participate in, build from, or otherwise lend support to this project.
  • Tools and Infrastructure
    • Be able to define the tools being used to manage and build this project, and explain their use in context.
    • Build a vocabulary to discuss projects of this general nature.
      • E.g. include new Labs infrastructure, along with github, and wikipedia itself through the wikiproject.
  • Related Projects
    • Hold an over-arching narrative of how this project fits into the wider theme of citations/references on WP.
    • Maintain awareness of VisualEditor project component on reference management directions / potential / collaboration
      • Zotero-server fetching via ajax requests in the browser.
    • Become familiar with WikiData, its progress and emerging role for data across projects
      • Scholarly works (open access) inclusivity
    • OA Button
    • New icon designs!
  • Hands-on
    • Join WikiProject Open Access, or some other wikiproject.
    • Sign up for github, or some other git hosting service like GitLab or Gitorious.
    • Install git, and git hosting service client on your local computer.
    • Introduction or advanced usage of PyWikiBot, python scripting with MediaWiki, programming generally, etc.
  • Extras
    • Build basic comprehension of the "hacker ethic" w/r/t the nature of this project.

Presenters / Facilitators

  • Get an understanding of how the project is best communicated to Wiki-savvy and general audiences.
  • Get updates about any existing projects that attendees know about, that we don't currently know.
  • Get feedback, both solicited and un-solicited from wiki-enthusiasts who attend WikiConference USA.
    • Learn how to best respond to this feedback.
    • Learn to incorporate this feedback into further plans, development, progress, etc.
  • Brainstorm ideas and overlap with other initiatives
  • Become comfortable opening doors to participate, as well as simply listening and benefiting from the contribution of participating in our session.

Free-form Summary

Start off by getting familiar with the attendees. Isn't clear who and how many are going to join, but we should anticipate being flexible and scoping our time to the people who are present. Very few attendees promotes a closer, informal discussion. Many attendees may promote having a larger, more formal presentation component, as well as potentially small-group discussion or hands-on components. Generally it's important for us to cater to the experience, interests, and needs of the attendees. They will be able to provide us early, invaluable feedback on our project—even if that feedback is a lack of clarity or comprehension (implying, for example, that we should focus on clarity going forward).

Overall, we should situate our project in the narrative of improving references / citations on Wikipedia. We're all about improving the experience of editing, and supporting the various communities of Wikipedia and its sister projects to create deep, connected, and flexibly consumed resources. We have focused our project on minimal goals in order to make the case for various small improvements that may one day be expanded into more comprehensive workflows. Our presentation should include a narrative arch:

  • What's the problem?
  • What we did we try in the past?
  • What worked, what didn't?
  • What are the solutions we see now?
  • What does the future look like?
  • What do we do starting now?

Outline

  1. Introductions
    • What do you spend your time doing, On-wiki and off-wiki?
  2. Skill-level and familiarity assessment
    • Raise your hand if:
      • You are familiar with (wiki world):
        • Wikipedia ;)
        • WikiSource
        • Wikimedia Commons
        • WikiData
        • Labs
        • Scholarly publishing generally
        • Open Access academic literature
      • You know about Open Access
      • You have heard about the OA-Signalling project
      • You are a member of WikiProject Open Access
      • You have heard of Wikiproject Open Access
      • You have a working knowledge of (technical stuff):
        • MediaWiki (wiki software)
        • Bots for Wikipedia, other Wikimedia projects (various wares)
        • Python (programming language)
        • PyWikiBot (python library)
        • XSLT (xml style templating)
        • JATS (NLM xml format)
  3. WikiProject Open Access
    • Open Access generally
    • Wikipedia, WikiProjects, and the goals of WikiProject Open Access
    • Signalling OA-ness
  4. Problems
  5. Solutions
    • Previous attempts
      • Successes
      • Failures
    • Current solutions
  6. Opportunities
    • How OA-signalling project provides partial solution, uses opportunities, and opens up opportunities.
    • Other projects opening opportunties here.
  7. The Future
    • Visions
    • Longer-term roadmap for OA-signalling and WikiProject Open Access
  8. Next Steps
    • How to participate / support
  9. Hands-on Component
    • Time-permitted workshopping based on areas of interest, skill.
      • Install OA Button

Content source: wpoa/OA-signalling

Similar notebooks:

notebook.community | gallery | about