You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<li><a href="#markdown">Learning how to use markdown</a></li>
321
+
<li><a href="#"></a></li>
322
+
<li><a href="#bonus">BONUS STEP</a></li>
321
323
</ul>
322
324
</div>
323
325
<div id="getting-started" class="section level2">
@@ -327,43 +329,69 @@ <h2>Getting started <a name="Getting_started"></a></h2>
327
329
<p>Throughout these tasks, we will help you to directly create and edit content that becomes part of this MOOC and its companion website. What you do from here on out will directly influence the learning of all individuals who come here in the future. Our job is to guide you in this process, and help you to realise that what you are doing is valuable, to yourself and others.</p>
328
330
<p><strong>IMPOSTER SYNDROME KLAXON</strong></p>
329
331
<p>Scholarly researchers represent the highest density of Imposter Syndrome that has ever been known to exist in the history of anything, ever. [ADD SOME DUBIOUS LINK/CITATION HERE]</p>
<h2>Learning how to use markdown<a name="markdown"></a></h2>
332
336
<p>A lot of people think RStudio is just for writing complex scripts for statistical analysis. Wrooooong. It can also be used to write nicely formatted text documents, using something called markdown. Much of this MOOC was written in markdown, and look how nice it all looks!</p>
333
337
<p>[insert tumbleweed gif]</p>
338
+
<p>Markdown is really a simple formatting style that gives you full control over the format of text. If you’re used to using something like Microsoft Word, it’s kind of similar and gives you the same control over simple things like header style and text format. But in a way that is readable by more software, and can also be easily easily rendered as a webpage.</p>
339
+
<p>Here is some basic markdown syntax that might be handy here:</p>
334
340
<p>[INSERT SOME BASIC MARKDOWN SYNTAX HERE]</p>
335
-
<ul>
336
-
<li><p>Write a summary about Open Access efforts either on your research discipline and/or in your country. If you have a website or blog, post it there.</p>
337
-
<ul>
338
-
<li>Were the data for this easy to acquire? Which sources did you use?</li>
339
-
</ul></li>
340
-
<li><p>Look at the status of Open Science in your research group or lab. Make a note of who is doing what. What could be improved?</p></li>
341
-
<li><p>Define clearly what Open Science means to you. Have a conversation about it with a colleague. Then, find someone from a different country, and have another conversation about Open Science.</p></li>
342
-
<li><p>Find out the policies are in your department or institute regarding:</p>
<h2>Putting this into practise<a name="draft"></a></h2>
345
+
<p>Consider this task a bit like a mini research project to help increase your personal knowledge about Open Science. Here, what we are going to do is write a brief summary article about Open Science either about your research discipline and/or in your country.</p>
346
+
<p>We are going to use the simple markdown syntax we just learned about above here. For this, you can use a simple text editor like Notepad, or others that are a little more complex like Atom.</p>
347
+
<p>There are several choices you have here:</p>
348
+
<ol style="list-style-type: decimal">
349
+
<li><p>Write about the state of Open Access in your research community or lab group. This can include things like what proportion of articles are OA, whether there is an OA policy, or a summary of how your colleagues and you view OA. For this, it would be good to think about whether existing data are available, and if were they easy to acquire? Make note of which sources you used, and whether you think these are appropriate to answer the questions.</p></li>
350
+
<li><p>Look at the status of Open Science in your research group or lab. Make a note of who is doing what, using what tools and services, and what their views are. What do you think could be improved?</p></li>
351
+
<li><p>Define clearly what Open Science means to you. Here, we want to make it a little challenging, by having a conversation about it with a colleague. Then, find someone from a different country, and have another conversation about Open Science. How do these view points all differ?</p></li>
352
+
<li><p>Time to investigate! Find out whether policies exist for your research group or institute regarding:</p></li>
353
+
</ol>
343
354
<ul>
344
355
<li><p>Career progression and assessment.</p></li>
345
356
<li><p>Publishing and Open Access.</p></li>
346
357
<li><p>Data sharing.</p></li>
347
358
<li><p>Intellectual Property (IP).</p></li>
348
-
</ul></li>
349
-
<li><p>Identify any disciplinary repositories either for research articles or data.</p></li>
350
359
</ul>
351
-
<p>** BONUS STEP**</p>
360
+
<p>Write a brief summary for one of these, and about how it might influence your own research.</p>
361
+
<ol start="5" style="list-style-type: decimal">
362
+
<li>Identify any repositories for research articles or data for your discipline, as well as any tools and services that are widely used. Make a little table illustrating the key traits for these - you can decide what they are! (e.g., are they Open Source, are they owned by a for-profit company, are the data openly licensed etc.)</li>
363
+
</ol>
364
+
<p>That’s it! You can keep this as simple or detailed as you like, and depending on what information is available for you. If you don’t like any of these options, feel free just to write something about your experiences as a researcher, and what drew you to be here.</p>
365
+
<p><br /></p>
366
+
<p>##** BONUS STEP**<a name="bonus"></a></p>
352
367
<p>Hopefully, you just wrote something pretty awesome, that you are proud of and want to share with others. I mean, after all that effort, why would you not want to? Let’s make this a reality.</p>
353
-
<p>Format the file like this:</p>
354
-
<p><code>DD-MM-YYYY-yourname_blah.md</code></p>
368
+
<p>There are two ways to go about this. If you have an existing website or blog, post it there. That was easy!</p>
369
+
<p>For the second route, let’s make this a real contribution to the main Open Science MOOC website!</p>
370
+
<p>Format your file like this:</p>
371
+
<p><code>DD-MM-YYYY-your_name.md</code></p>
372
+
<p>Replacing <code>your_name</code> with your_name. Your actual name.</p>
355
373
<p>Now, go to <a href>this folder</a> and upload your new blog post. Click ‘Commit’ and simply add a little message describing what you have done. For now, don’t worry too much about using GitHub, as we address that in other modules.</p>
356
374
<p>What this will do is notify the people who are part of the core MOOC team that a new file has been uploaded. As soon as we ‘accept’ the new file, just like magic, it will automatically render [here] on the main Open Science MOOC website! How cool is that?</p>
357
375
<p>Now, all you have to do is share it. If you use Facebook, Twitter, LinkedIn, GooglePlus, Instagram or whatever, make sure to share your work widely. Let people know what Open Science means to you!</p>
<h2>Getting started <a name="Getting_started"></a></h2>
363
-
</div>
364
378
<div id="checklist" class="section level2">
365
379
<h2>Checklist <a name="Checklist"></a></h2>
380
+
<p>Hopefully now, you will have a greater understanding of just some of the different ways in which Open Science influences you and your research.</p>
381
+
<ul>
382
+
<li>[ ] You are now familiar with some basic markdown syntax and can use these to draft simple blog posts.</li>
383
+
<li>[ ] You can now describe some of the Open Science policies that influence you, your colleagues, and your research discipline.</li>
384
+
<li>[ ] You have written and shared a blog post illustrating this.</li>
385
+
</ul>
386
+
<p><br /></p>
366
387
<p><strong>CONGRATULATIONS!</strong></p>
388
+
<p>You have now help to upgrade your knowledge about Open Science, and have already shared this to help others learn too.</p>
389
+
<p>From now on, it is all up to you! Some advice is to:</p>
390
+
<ul>
391
+
<li>Keep learning. Knowledge is power.</li>
392
+
<li>Keep discussing these things with your colleagues, and develop a collective understanding of how Open Science influences you all in different ways.</li>
393
+
</ul>
394
+
<p><br /></p>
367
395
<p><strong>Know a way this content can be improved?</strong></p>
368
396
<p>Time to take your new GitHub skills for a test-run! All content development primarily happens <a href="https://github.com/OpenScienceMOOC/Module-1-Open-Principles/blob/master/content_development/Task_1.md">here</a>. If you have a suggested improvement to the content, layout, or anything else, you can make it and then it will automatically become part of the MOOC content after verification from a moderator!</p>
@@ -35,77 +33,93 @@ Scholarly researchers represent the highest density of Imposter Syndrome that ha
35
33
36
34
## Learning how to use markdown<aname="markdown"></a>
37
35
38
-
39
36
A lot of people think RStudio is just for writing complex scripts for statistical analysis. Wrooooong. It can also be used to write nicely formatted text documents, using something called markdown. Much of this MOOC was written in markdown, and look how nice it all looks!
40
37
41
38
[insert tumbleweed gif]
42
39
43
40
Markdown is really a simple formatting style that gives you full control over the format of text. If you're used to using something like Microsoft Word, it's kind of similar and gives you the same control over simple things like header style and text format. But in a way that is readable by more software, and can also be easily easily rendered as a webpage.
44
41
42
+
Here is some basic markdown syntax that might be handy here:
43
+
45
44
[INSERT SOME BASIC MARKDOWN SYNTAX HERE]
46
45
47
46
<br/>
48
47
49
48
## Putting this into practise<aname="draft"></a>
50
49
51
-
Consider this task a bit like a mini research project. Here, what we are going to do is write a brief summary article about Open Science either on your research discipline and/or in your country.
50
+
Consider this task a bit like a mini research project to help increase your personal knowledge about Open Science. Here, what we are going to do is write a brief summary article about Open Science either about your research discipline and/or in your country.
51
+
52
+
We are going to use the simple markdown syntax we just learned about above here. For this, you can use a simple text editor like Notepad, or others that are a little more complex like Atom.
52
53
53
54
There are several choices you have here:
54
55
55
56
1. Write about the state of Open Access in your research community or lab group. This can include things like what proportion of articles are OA, whether there is an OA policy, or a summary of how your colleagues and you view OA. For this, it would be good to think about whether existing data are available, and if were they easy to acquire? Make note of which sources you used, and whether you think these are appropriate to answer the questions.
56
57
57
58
2. Look at the status of Open Science in your research group or lab. Make a note of who is doing what, using what tools and services, and what their views are. What do you think could be improved?
58
59
59
-
3.* Define clearly what Open Science means to you. Here, we want to make it a little challenging, by having a conversation about it with a colleague. Then, find someone from a different country, and have another conversation about Open Science. How do these view points all differ?
60
-
61
-
62
-
63
-
If you have a website or blog, post it there.
64
-
65
-
66
-
*
60
+
3. Define clearly what Open Science means to you. Here, we want to make it a little challenging, by having a conversation about it with a colleague. Then, find someone from a different country, and have another conversation about Open Science. How do these view points all differ?
67
61
62
+
4. Time to investigate! Find out whether policies exist for your research group or institute regarding:
68
63
69
-
* Find out the policies are in your department or institute regarding:
64
+
* Career progression and assessment.
70
65
71
-
* Career progression and assessment.
66
+
* Publishing and Open Access.
72
67
73
-
* Publishing and Open Access.
68
+
* Data sharing.
74
69
75
-
* Data sharing.
70
+
* Intellectual Property (IP).
71
+
72
+
Write a brief summary for one of these, and about how it might influence your own research.
76
73
77
-
* Intellectual Property (IP).
74
+
5. Identify any repositories for research articles or data for your discipline, as well as any tools and services that are widely used. Make a little table illustrating the key traits for these - you can decide what they are! (e.g., are they Open Source, are they owned by a for-profit company, are the data openly licensed etc.)
78
75
79
-
* Identify any disciplinary repositories either for research articles or data.
76
+
That's it! You can keep this as simple or detailed as you like, and depending on what information is available for you. If you don't like any of these options, feel free just to write something about your experiences as a researcher, and what drew you to be here.
80
77
78
+
<br/>
81
79
82
80
##** BONUS STEP**<aname="bonus"></a>
83
81
84
82
Hopefully, you just wrote something pretty awesome, that you are proud of and want to share with others. I mean, after all that effort, why would you not want to? Let's make this a reality.
85
83
84
+
There are two ways to go about this. If you have an existing website or blog, post it there. That was easy!
85
+
86
+
For the second route, let's make this a real contribution to the main Open Science MOOC website!
86
87
88
+
Format your file like this:
87
89
88
-
Format the file like this:
90
+
`DD-MM-YYYY-your_name.md`
89
91
90
-
`DD-MM-YYYY-yourname_blah.md`
92
+
Replacing `your_name` with your_name. Your actual name.
91
93
92
94
Now, go to [this folder]() and upload your new blog post. Click 'Commit' and simply add a little message describing what you have done. For now, don't worry too much about using GitHub, as we address that in other modules.
93
95
94
96
What this will do is notify the people who are part of the core MOOC team that a new file has been uploaded. As soon as we 'accept' the new file, just like magic, it will automatically render [here] on the main Open Science MOOC website! How cool is that?
95
97
96
98
Now, all you have to do is share it. If you use Facebook, Twitter, LinkedIn, GooglePlus, Instagram or whatever, make sure to share your work widely. Let people know what Open Science means to you!
97
99
98
-
99
100
<br/>
100
101
101
-
## Getting started <aname="Getting_started"></a>
102
+
## Checklist <aname="Checklist"></a>
102
103
104
+
Hopefully now, you will have a greater understanding of just some of the different ways in which Open Science influences you and your research.
103
105
104
-
## Checklist <aname="Checklist"></a>
106
+
-[ ] You are now familiar with some basic markdown syntax and can use these to draft simple blog posts.
107
+
-[ ] You can now describe some of the Open Science policies that influence you, your colleagues, and your research discipline.
108
+
-[ ] You have written and shared a blog post illustrating this.
105
109
110
+
<br/>
106
111
107
112
**CONGRATULATIONS!**
108
113
114
+
You have now help to upgrade your knowledge about Open Science, and have already shared this to help others learn too.
115
+
116
+
From now on, it is all up to you! Some advice is to:
117
+
118
+
* Keep learning. Knowledge is power.
119
+
* Keep discussing these things with your colleagues, and develop a collective understanding of how Open Science influences you all in different ways.
120
+
121
+
<br/>
122
+
109
123
**Know a way this content can be improved?**
110
124
111
125
Time to take your new GitHub skills for a test-run! All content development primarily happens [here](https://github.com/OpenScienceMOOC/Module-1-Open-Principles/blob/master/content_development/Task_1.md). If you have a suggested improvement to the content, layout, or anything else, you can make it and then it will automatically become part of the MOOC content after verification from a moderator!
0 commit comments