teaching-slide-shows
repo hosting teaching slideshow presentations
Science Score: 41.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
✓codemeta.json file
Found codemeta.json file -
○.zenodo.json file
-
○DOI references
-
○Academic publication links
-
✓Committers with academic emails
1 of 1 committers (100.0%) from academic institutions -
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (5.7%) to scientific vocabulary
Last synced: 10 months ago
·
JSON representation
·
Repository
repo hosting teaching slideshow presentations
Basic Info
- Host: GitHub
- Owner: lwasser
- Language: HTML
- Default Branch: master
- Size: 1.71 MB
Statistics
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
- Releases: 0
Created almost 10 years ago
· Last pushed almost 10 years ago
Metadata Files
Readme
Citation
README.md
Build DataOne Slide Decks
Contributors: Jonah Duckles, Leah Wasser
A markdown based system to build DataOne education modules using reveal.js.
Introduction
This repository takes a markdown file (pandoc flavored syntax) and builds it to a reveal.js responsive slide show.
To get going
- make sure reveal.js is setup as a submodule
- clone the repository
- make sure pandoc is installed on your local machine
- at the command line type
make html-- all files with an .md extension will be built.
To be able to build locally, you need to make sure that the reveal.js files
also clone.
git submodule add https://github.com/hakimel/reveal.js reveal.js and or
git submodule update --init --recursive
in the command line.
Owner
- Name: Leah Wasser
- Login: lwasser
- Kind: user
- Location: United States
- Company: @pyOpenSci
- Website: www.leahwasser.com
- Repositories: 143
- Profile: https://github.com/lwasser
Open education, Open source and Open Science. Executive Director @pyOpenSci
Citation (citation.html)
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="generator" content="pandoc">
<title></title>
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, minimal-ui">
<link rel="stylesheet" href="css/NEON-reveal.css">
<link rel="stylesheet" href="reveal.js/css/reveal.css">
<style type="text/css">code{white-space: pre;}</style>
<link rel="stylesheet" href="reveal.js/css/theme/black.css" id="theme">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? 'reveal.js/css/print/pdf.css' : 'reveal.js/css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
<!--[if lt IE 9]>
<script src="reveal.js/lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<div class="slides">
<section id="does-copyright-apply" class="level2">
<h2>Does copyright apply?</h2>
<p><strong>Copyright applies to creative works</strong></p>
<ul>
<li>source code</li>
<li>text (manuscripts etc)</li>
<li>images</li>
</ul>
</section>
<section id="does-copyright-apply-1" class="level2">
<h2>Does copyright apply?</h2>
<p><strong>Typically not copyrightable:</strong></p>
<ul>
<li>data, results</li>
<li>individual records in a database of facts</li>
</ul>
<p><strong>Depends on jurisdiction and case:</strong></p>
<ul>
<li>curated collections of data</li>
<li>databases</li>
<li>medical images</li>
</ul>
</section>
<section id="choose-a-license" class="level2">
<h2>Choose A License</h2>
<iframe width="70%" height="700px" src="http://choosealicense.com/">
</iframe>
</section>
<section id="software-licensing-guide" class="level2">
<h2>Software licensing guide</h2>
<p><small>Figure 3: Schematic representation of license directionality.</small> <small>Source: Morin, Andrew, Jennifer Urban, and Piotr Sliz. 2012. <a href="http://dx.doi.org/10.1371/journal.pcbi.1002598">A Quick Guide to Software Licensing for the Scientist-Programmer.</a> PLoS Computational Biology 8 (7): e1002598 </small></p>
<figure>
<img src="images/share-publish-archive/journal.pcbi.1002598.g002.png" />
</figure>
</section>
<section id="creative-commons" class="level2">
<h2>Creative Commons</h2>
<iframe width="100%" height="700px" src="http://creativecommons.org/choose/">
</iframe>
</section>
<section id="open-is-not-open-to-interpretation" class="level2">
<h2>Open is not open to interpretation</h2>
<p><a href="http://opendefinition.org/">The Open Definition</a> sets out principles that define “openness” in relation to data and content. It makes precise the meaning of “open” in the terms <em>open data</em>, <em>open content</em>, and <em>open source</em>:</p>
<blockquote>
<p><small>“Open means anyone can freely access, use, modify, and share for any purpose (subject, at most, to requirements that preserve provenance and openness).” </small></p>
</blockquote>
<p>or more succinctly:</p>
<blockquote>
<p><small>“Open data and content can be freely used, modified, and shared by anyone for any purpose”</small></p>
</blockquote>
</section>
<section id="waiving-copyright" class="level2">
<h2>Waiving copyright</h2>
<center>
<a href="http://creativecommons.org/about/cc0"><img src="http://mirrors.creativecommons.org/presskit/buttons/88x31/png/cc-zero.png" alt="CC Zero" /></a>
</center>
<p>CC0 enables scientists, educators, artists and other creators and owners of copyright- or database-protected content to waive those interests in their works and thereby place them as completely as possible in the public domain, so that others may freely build upon, enhance and reuse the works for any purposes without restriction under copyright or database law.</p>
</section>
<section id="dryad-requires-cc0" class="level2">
<h2>Dryad requires CC0</h2>
<p><a href="http://datadryad.org/pages/faq#info-cc0">Dryad’s use of CC0</a> to make the terms of reuse explicit has some important advantages:</p>
<ul>
<li><strong>Interoperability</strong>: Since CC0 is both human and machine-readable, other people nd indexing services will automatically be able to determine the terms of use.</li>
<li><strong>Universality</strong>: CC0 is a single mechanism that is both global and universal, covering all data and all countries. It is also widely recognized.</li>
<li><strong>Simplicity</strong>: There is no need for humans to make, or respond to, individual data requests, and no need for click-through agreements. This allows more scientists to spend their time doing science.</li>
</ul>
</section>
<section id="licenses-versus-community-norms" class="level2">
<h2>Licenses versus community norms</h2>
<p>From the <a href="http://pantonprinciples.org/faq/#Q11_What_are_community_norms_and_why_are_they_important">Panton Principles</a>:</p>
<blockquote>
<p><small>[...] in the scholarly research community the act of citation is a commonly held community norm when reusing another community member’s work.</p>
<p>Community norms can be a much more effective way of encouraging positive behaviour, such as citation, than applying licenses. A well functioning community supports its members in their application of norms, whereas licences can only be enforced through court action and thus invite people to ignore them when they are confident that this is unlikely.</small></p>
</blockquote>
</section>
<section id="licenses-are-legal-instruments" class="level2">
<h2>Licenses are legal instruments</h2>
<ul>
<li>Licenses, copyright, terms of use are complicated issues.</li>
<li>There are legal implications to your choices.</li>
<li>Citation is a professional norm in science.
<ul>
<li>We have good systems for ensuring proper citation.</li>
<li>Would you try to sue someone in court who fails to cite you properly?</li>
</ul></li>
<li>Keep it simple by putting the least-restrictive license possible</li>
</ul>
<p><br/> <em>Let scientists do science without having to talk to lawyers.</em></p>
</section>
</div>
</div>
<script src="reveal.js/lib/js/head.min.js"></script>
<script src="reveal.js/js/reveal.js"></script>
<script>
// Full list of configuration options available at:
// https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
slideNumber: true,
// Optional reveal.js plugins
dependencies: [
{ src: 'reveal.js/lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'reveal.js/plugin/zoom-js/zoom.js', async: true },
{ src: 'reveal.js/plugin/notes/notes.js', async: true }
]
});
</script>
</body>
</html>
GitHub Events
Total
Last Year
Committers
Last synced: over 1 year ago
Top Committers
| Name | Commits | |
|---|---|---|
| Leah Wasser | l****r@c****u | 2 |
Committer Domains (Top 20 + Academic)
colorado.edu: 1
Issues and Pull Requests
Last synced: over 1 year ago
All Time
- Total issues: 0
- Total pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Total issue authors: 0
- Total pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 0
- Pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0