Git Product home page Git Product logo

open-data-training's Introduction

ResearchFox

WELCOME to the Open Data Training Program Repository!

The Mozilla Science Lab is developing an Open Data Training Program. This repository will be where we build and share our curriculum and resources for open data.

Here's what's been developed so far.

Our first priority is to complete the first five primers as laidout in the Roadmap linked below. Following that, we will be writing up Instructor Guides based off those primers. You can see an example at the link to Instructor Guides above.

If you'd like to see our current plan for development of this program, check out our Roadmap.

If you are looking for more information on Mozilla Science Lab, please see our website.

  • Stephanie Wright, Program Lead, Mozilla Science Lab
  • Zannah Marsh, Learning Strategist, Mozilla Science Lab
  • Christie Bahlai, Mozilla Fellow for Science 2015-16, Assistant Professor, Kent State University
  • Danielle Robinson, Mozilla Fellow for Science 2016-17, Scientific and Partnerships Director, Code for Science and Society
  • Robin Champieux, Scholarly Communication Librarian, OHSU

Special Thanks

to Cynthia Tso, Web & Curriculum Development Intern, UW iSchool for all her hard work updating these materials over the summer of 2018.

Huge thanks to contributors from 2016 Global Sprint who aren't noted in GitHub because we were working in the Google Docs!

See also the list of contributors who participated in this project.

License

Creative Commons License

This work is licensed under a Creative Commons Attribution 4.0 International License.

open-data-training's People

Contributors

alexmorley avatar auremoser avatar nduma avatar stephwright avatar zee-moz avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

open-data-training's Issues

Add visuals/illustrations to the primers!

Comment from Dhafer Laouini at the 2016 global sprint:

Would be perhaps good to add a comparative and illustrative schema to highlight the benefits and advantages of open data in comparison to private date

Prepare Modules 1-3 for Midwest Librarian Symposium

Add this content to Module 5!

This topic surfaced during the global sprint:

Fatma commented: (Pasteur_Tunis) Could it be possible to add a new issue about reviewing the data critically before using it ? such as "Should I believe this data blindly?..." several stories report big scientists names creating the data from scratch without experimental evidence. Have a look at the 'Office of Research Integrity' as an example https://ori.hhs.gov

Steph answered:
Absolutely think this is critical to ask. I think it may fit better in what we have in mind for module 5 (Making Friends with Other People's Data) which will be abt what you need to consider before using others data.

Develop Modules 4-7

  • 4. Become a Data Hunter (1.5 hour session)
  • 5. Making Friends with Other People's Data (1 hour session)
    6. Open Facilitation, Teaching, + Community Building (2 hour session)
    7. Tools and workflow for working Open (1.5 hrs)

Should the Open Data Primer address privacy?

Excellent IRL examples and unpacking of the open data rationale. I wonder if this

But data is also collected by governments, who may be interested in the number and location of potholes on a city street, or the geospatial pattern of new cases in an outbreak of the flu. Corporations and businesses collect data, too.

opens a discussion about the boundaries of what should be shared openly, subjects' privacy choices, and how researchers can avoid sharing seemingly innocuous data that reveals too much about individuals.

Develop Module 1: Why Open Data

Module 1
Based off Primer 1

Are there concepts in the Primer that aren't addressed in the Module?
Do you have interactive exercises to suggest to drive home concepts?
Are there resources and / or real-life example stories we should include in this module?

Feel free to address these directly in the Google doc linked above.

Provide general feedback on Primer 1: Why Open Data

Primer 1

Looking specifically for feedback on:

  • anything terms or concepts that aren't clear
  • typos
  • how the primer flows from beginning to end
  • is there something missing from the primer you think should be added?
  • suggestions for additional resources at the end
  • suggestions for readings and / or real-life examples to be used in the primer to drive home concepts

Add info on where to access data in Primer 3

John Kratz commented: I think it would make more sense to merge geospatial and temporal coverage into one item and break off access/licensing/reuse.

Amel Ghouila: I perfectly agree

Stephanie Wright:I'm wondering what that will do to the flow of the original six questions we asked (WHY, WHAT, WHO, WHERE, WHEN & HOW). We can combine WHEN & WHERE into one section w/o too much trouble. If we break out access/licensing/reuse, we are breaking the questions out across two sections and w/i in one section at the same time. (Geospatial in one section and location of access in another while both address WHERE; combining access/licensing/reuse into one section gives us a section containing WHERE & HOW(?))

John Kratz: Okay, I can see the logic of the current arrangement, but I still think combining the two senses of WHERE is confusing. If we were talking about physical specimens collected here and stored there, that would make sense, but the WHERE of the dataset will almost always be a URL (or something that resolves to a URL), and of course we don't care about the physical location.

What if we pulled access/license stuff from this primer and put it in primer 3? The only reason we're talking about it here is that it should go in the DATA_README, but you have to go through the next primer to have that information anyway. Maybe just put a note at the end of the six questions that there's one more thing to add, but we're not ready for that yet and we'll get to it in the next primer?

TLDR version: I think we should divide the discussion of metadata into descriptive metadata and administrative metadata, and cover descriptive here and administrative in primer 3.

Neuroscience Open Data Workshop

As part of our department's Training day in January '17 I have been asked to give a workshop on Data Sharing. I'm going to start working on some extra stuff for this soon as well drawing up an open data plan with other members on the unit. I thought this might be a nice use case to have up on the repo so shall I put up a planning document / folder up here?

Develop Module 2: How to Open Your Data

Module 2
Based off Primer 2

This module has not progressed as far as module 1. Just some rough thoughts put in a doc. Feel free to hack on it.

Are there concepts in the Primer that aren't addressed in the Module?
Do you have interactive exercises to suggest to drive home concepts?
Are there resources and / or real-life example stories we should include in this module?

Feel free to address these directly in the Google doc linked above.

Provide general feedback on Primer 3: Sharing Your Data

Primer 3

This primer is not in full draft yet. Looking for:

  • suggestions for filling out the sections at the end on privacy / ethical considerations
  • additional resources at the end
  • clarification of terms / concepts
  • is anything else missing?
  • suggestions for readings and / or real-life examples to be used in the primer to drive home concepts

Develop Module 3: Sharing Your Data

Module 3
Based off Primer 3

This module is BARELY started and the primer is still in rough draft. The primer will need to be addressed more fully before much work can be done on the module but feel free to give it a go.

Are there concepts in the Primer that aren't addressed in the Module?
Do you have interactive exercises to suggest to drive home concepts?
Are there resources and / or real-life example stories we should include in this module?

Feel free to address these directly in the Google doc linked above.

Write up interactives in primers 1-3 as exercises to use in modules

  • Review primers for interactives
    • Primer 1: Why open data
    • Primer 2: How open data
    • Primer 3: Sharing data openly
  • Determine which ones would work well as exercises in modules
  • Determine if those not suitable for modules now could be modified to become exercises
  • Write up exercises in Handout templates
  • Link to and insert in modules where appropriate

Provide general feedback on Primer 2: How to Open Your Data

Primer 2
Looking specifically for feedback on:

  • anything terms or concepts that aren't clear
  • typos
  • how the primer flows from beginning to end
  • is there something missing from the primer you think should be added?
  • suggestions for additional resources at the end
  • suggestions for readings and / or real-life examples to be used in the primer to drive home concepts

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.