WikiProject Open Access - OA Signalling¶
Presentation organized for 2014 WikiConference USA in New York City, New York.
- 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.
Not absolutes, but setting scope of expectations for the parties involved
Attendees / Participants¶
- 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!
- 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.
- 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.
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?
- What do you spend your time doing, On-wiki and off-wiki?
- Skill-level and familiarity assessment
- Raise your hand if:
- You are familiar with (wiki world):
- Wikipedia ;)
- Wikimedia Commons
- 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
- Open Access generally
- Wikipedia, WikiProjects, and the goals of WikiProject Open Access
- Signalling OA-ness
- Previous attempts
- Current solutions
- How OA-signalling project provides partial solution, uses opportunities, and opens up opportunities.
- Other projects opening opportunties here.
- The Future
- Longer-term roadmap for OA-signalling and WikiProject Open Access
- Next Steps
- How to participate / support
- Hands-on Component
- Time-permitted workshopping based on areas of interest, skill.