-
Notifications
You must be signed in to change notification settings - Fork 0
/
oss-tools.html
250 lines (209 loc) · 10.6 KB
/
oss-tools.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<title>Collecting and Protecting Your Data</title>
<link rel="stylesheet" href="reveal/css/reveal.css">
<link rel="stylesheet" href="reveal/css/theme/simple.css">
<!-- Theme used for syntax highlighting of code -->
<link rel="stylesheet" href="reveal/lib/css/zenburn.css">
<!-- 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/css/print/pdf.css' : 'reveal/css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
</head>
<body>
<div class="reveal">
<div class="slides">
<!--SLIDE 1-->
<section>
<h2>Free and Open Source Digital Tools</h2><br/>
<div class="title-page"><p>Vicky Steeves & Nicholas Wolf | April 8, 2017 </p></div>
<img src="imgs/dataservices.png" width="30%" height="30%" align="middle"><br/>
<div class='footer'>
<hr/>
<p>Vicky's ORCID: <a href="http://orcid.org/0000-0003-4298-168X/">0000-0003-4298-168X</a> | Nick's ORCID: <a href="http://orcid.org/0000-0001-5512-6151">0000-0001-5512-6151</a><br/>
This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc/4.0/">Creative Commons Attribution-NonCommercial 4.0 International License</a>.</p>
</div>
</section>
<!--SLIDE 2-->
<section>
<h3>Open Source <strong>Research</strong> Software: Benefits</h3>
<span style="color:#ff6a1c;"><p>1. Cost</p></span>
<ul>
<li>Yes, open source is about transforming certain types of expenses (e.g. license fees) into other types (e.g. salaried/volunteer labor; maintenance costs)</li>
<li>Yes, sometimes open source can be more expensive overall once maintenance and personnel are factored in...<br/><br>...though see Wong and Sayo (2003), Russo et al. (2005), Dehinbo & Dehinbo (2013) noting that proprietary software still often outstrips open source in costs</li>
</ul>
</section>
<!--SLIDE 3-->
<section>
<h3>Open Source <strong>Research</strong> Software: Benefits</h3>
<span style="color:#ff6a1c;"><p>1. Cost</p></span>
<ul>
<li>BUT...Remember that we are talking about <strong>research</strong> software used by researchers and their community, not enterprise-level services (most of the current studies only look at open source enterprise-level software)</li>
<li>Thus, the line between doing research and building software is blurred...so to a greater degree the (research) labor also covers development cost</li>
</ul>
</section>
<!--SLIDE 4-->
<section>
<h3>Open Source <strong>Research</strong> Software: Benefits</h3>
<br/><br/><p>We pause to mention:</p>
<img src="imgs/r-software.jpg" width="30%" height="30%" align="middle">
</section>
<!--SLIDE 5-->
<section>
<h3>Open Source <strong>Research</strong> Software: Benefits</h3>
<span style="color:#ff6a1c;"><p>2. Technology</p></span>
<ul>
<li>Open source development depends on a collaborative community dedicated to uncovering knowledge. That aligns, as Dehinbo & Dehinbo note, with the values of the university</li>
<li>Most importantly, open source community of researchers have responsibility for maintenance, requiring an ongoing push against obsolescence and closed code bases</li>
</ul>
</section>
<!--SLIDE 6-->
<section>
<h3>Barriers to Adoption</h3>
<ul><li>Most researchers want to focus on analysis, and they want it done now <span style="color:#ff6a1c;">(right now)</span> with the closest masterable tool at hand</li>
<li>University IT, university libraries, and others overseeing licenses find it easier to manage workflows and asset management via contracts and license fees</li>
<li>Open source research software features a steeper initial learning curve but greater extensibility</li>
</ul>
</section>
<!--SLIDE 9-->
<section>
<h3>Barriers to Adoption</h3>
<img src="imgs/LearningCurve2.png" width="80%" height="80%" align="middle">
</section>
<!--RESEARCHERS, 5min-->
<section>
<h3>Researcher Reactions</h3>
<div style="float:left; width:45%">
<h3><u>Pre-OSS</u></h3>
<p>"I don't have time to teach myself or my students a new tool."</p>
<p>"I won't be as supported as I am with XYZ company."</p>
<p>"I don't trust tools without a company behind it. Who knows if it'll go away?"</p>
</div>
<div style="float:right; width:45%">
<h3><u>Post OSS</u></h3>
<p>"This made my research more reproducible!"</p>
<p>"The community provides great resources for learning."</p>
<p>"I've actually contributed to the software! Awesome!"</p>
</div>
<aside class="notes">
Teaching and consults using open source, push to increase interop, archivability, sustainability
</aside>
</section>
<!--SOLUTIONS, 5min-->
<section>
<h2>The goal is to encourage <span style="color:#ff6a1c;">the community</span> to consciously choose open tools to increase <span style="color:#ff6a1c;">interoperability</span> & <span style="color:#ff6a1c;">sustainability</span> of their research.</h2>
</section>
<!--SLIDE 2-->
<section>
<h2>Open Access to Research <em>Results</em>?</h2>
<ul><li>NSF "Public Access to Results" initiative: all publications funded by NSF to be publicly accessible within one year. Currently, publications only but moving in direction of including data.</li>
<li>NIH already has PubMed Central...in talks over "data commons."</li>
<li>Humanities CORE, NEH-funded repository for humanities data</li>
</ul>
<strong>Summary:</strong>For now, just require data management, but strong possibility of requiring data access, too.
</section>
<!--SLIDE 3-->
<section>
<h2>Getting Credit for Your Data</h2>
<img src="imgs/data-citations.png" align="middle">
<!--SPEAKER NOTES-->
<aside class="notes">
Oh hey, these are some notes. They'll be hidden in your presentation, but you can see them if you open the speaker notes window (hit 's' on your keyboard).
</aside>
</section>
<!--SLIDE 5-->
<section>
<h2>Time to Share Data...How?</h2>
</section>
<!--SLIDE 6-->
<section>
<h2>A Reminder of Some Open Access Principles</h2>
<ol><li>Green (freely accessible, self-archived) vs. Gold (researcher-paid freely available) Access</li>
<ul><li>Most data archives/publishers are green, though a few provide deeper preservation through partnered financial support (quasi-gold)</li>
<li>Close link between publication and data archiving (i.e. archiving by journals) means data archiving may be green/gold depending on journal</li></ul>
<li>Levels of archiving: Self-Archived/Minimally Described vs. Self-Archived Well-Described vs. Fully Archived</li></ol>
</section>
<!--SLIDE 7-->
<section>
<h2>Some Minimum Requirements</h2>
Data must be:
<ul><li>Persistently linked (At least URI/URL...preferabally DOI)</li>
<li>Searchable and browsable</li>
<li>Retrieved or downloaded easily</li>
<li>Citable</li>
</ul>
</section>
<!--SLIDE 8-->
<section>
<h2>Self-Archived/Minimally Described</h2>
<a href="http://osf.io">Open Science Framework</a>
</section>
<!--SLIDE 9-->
<section>
<h2>Self-Archived Well-Described</h2>
<a href="https://datadryad.org/">Dryad</a><br/>
<a href="https://figshare.com/">Figshare</a><br/>
<a href="https://mla.hcommons.org/core/">MLA CORE, Open Access Repository for the Humanities</a>
</section>
<!--SLIDE 10-->
<section>
<h2>Fully Archived</h2>
<a href="https://www.icpsr.umich.edu/icpsrweb/">ICPSR</a><br/>
<a href="http://www.data-archive.ac.uk/">UK Data Archive</a><br/>
<a href="https://qdr.syr.edu/">Syracuse Qualitative Data Archive</a>
</section>
<!--SLIDE 11-->
<section>
<h2>...Or, Select Repository by Discipline</h2>
<a href="http://guides.nyu.edu/data_management/repository_selection">NYU Data Management: Selecting a Repository</a>
</section>
<!--SLIDE 12-->
<section>
<h2>Some hands-on work:</h2>
<a href="http://openrefine.org/">Open Refine (Data Cleaning)</a><br/>
<a href="https://gephi.org/">Gephi (Network Analysis)</a><br/>
<a href="https://wordpress.org/">Wordpress (Open Source Web Platform/Content Management System)</a>
</section>
<!-- CONCLUSION SLIDE -->
<section>
<h2>Questions?</h2><br/>
<p>Email us: <a href="mailto:[email protected]">[email protected]</a> & <a href="mailto:[email protected]">[email protected]</a></p>
<p>Learn more about RDM: <a href="http://guides.nyu.edu/data_management">guides.nyu.edu/data_management</a></p>
<p>Get this presentation: <a href="http://guides.nyu.edu/data_management/resources">guides.nyu.edu/data_management/resources</a></p>
<p>Make an appointment: <a href="http://guides.nyu.edu/appointment">guides.nyu.edu/appointment</a></p>
<div class='footer'>
<hr/>
<p>Vicky's ORCID: <a href="http://orcid.org/0000-0003-4298-168X/">0000-0003-4298-168X</a> | Nick's ORCID: <a href="http://orcid.org/0000-0001-5512-6151">0000-0001-5512-6151</a><br/>
This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc/4.0/">Creative Commons Attribution-NonCommercial 4.0 International License</a>.</p>
</div>
<!--SPEAKER NOTES-->
<aside class="notes">
Oh hey, these are some notes. They'll be hidden in your presentation, but you can see them if you open the speaker notes window (hit 's' on your keyboard).
</aside>
</section>
</div>
</div>
<script src="reveal/lib/js/head.min.js"></script>
<script src="reveal/js/reveal.js"></script>
<script>
// More info https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
history: true,
// More info https://github.com/hakimel/reveal.js#dependencies
dependencies: [
{ src: 'reveal/plugin/markdown/marked.js' },
{ src: 'reveal/plugin/markdown/markdown.js' },
{ src: 'reveal/plugin/notes/notes.js', async: true },
{ src: 'reveal/plugin/highlight/highlight.js', async: true, callback: function() { hljs.initHighlightingOnLoad(); } }
]
});
</script>
</body>
</html>