Skip to content

Commit 7c37a6f

Browse files
author
protohedgehog
committed
Fixed brokens links, #15
1 parent cb4e35a commit 7c37a6f

File tree

5 files changed

+10
-12
lines changed

5 files changed

+10
-12
lines changed

CONTRIBUTING.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ These are the main contributing guidelines for the development of this MOOC, and
33
1. Invited experts as part of a core development team, led by one or two managers for each module.
44
1. Open participation, where anyone can contribute using the standard processes on GitHub.
55

6-
Feedback and contributions of any form are welcomed. Feel free also to [contact us](https://opensciencemooc.eu/contact-us/) to discuss anything further.
6+
Feedback and contributions of any form are welcomed. Feel free also to [contact us](https://opensciencemooc.eu/contact/) to discuss anything further.
77

88
At the present, development is in very early stages, as this is an entirely crowd-sourced and volunteer-led project. We are focusing inititally on [Module 5](https://github.com/OpenScienceMOOC/Module-5-Open-Research-Software-and-Open-Source) to run as a pilot for testing and receiving feedback. After this, the protocol and content will be revised, and then applied accordingly to the development of the remaining modules.
99

@@ -13,14 +13,14 @@ If you want to contribute, add yourself to the [contributors list](https://docs.
1313

1414
If you have questions about the project, please [email us](info@opensciencemooc.eu) directly.
1515

16-
Stay tuned on what's happening on Twitter with [@OpenSci_MOOC](https://twitter.com/OpenSci_MOOC).
16+
Stay tuned on what's happening on Twitter with [@OpenSci_MOOC](https://twitter.com/OpenScienceMOOC).
1717

1818
## Getting started
1919
1. [Forming a team for collaborative design](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/MODULE_DESIGN_PROTOCOL.md#forming-a-team-for-collaborative-design).
2020
1. [The development process](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/MODULE_DESIGN_PROTOCOL.md#the-development-process).
2121
1. Familiarise yourself with the [script writing guide](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/Writing_a_script.md), the [script template](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/Script_template.md) and the [video management protocol](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/Video_management_protocol.md).
2222

23-
Each team will adhere to the [MOOC planning template](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/MOOC%20planning%20template.docx) to structure development in a systematic way.
23+
Each team will adhere to the [MOOC planning template](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/MOOC_planning_template.md) to structure development in a systematic way.
2424

2525

2626
## Reporting issues

content_development/MAIN.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ Therefore, irrespective of your background **you are very much welcome here**.
7878

7979
<center><img src="https://github.com/OpenScienceMOOC/Module-1-Open-Principles/blob/master/content_development/images/open_science.png?raw=true" width="800" /></center>
8080

81-
<p align="center"><i>Melanie Imming, & Jon Tennant. (2018, June 8). Sticker Open Science: just science done right. Zenodo. <a href="http://doi.org/10.5281/zenodo.128557">http://doi.org/10.5281/zenodo.128557</a></i></p>
81+
<p align="center"><i>Melanie Imming, & Jon Tennant. (2018, June 8). Sticker Open Science: just science done right. Zenodo. <a href="https://zenodo.org/record/1285575#.XDebSM17lPY">https://zenodo.org/record/1285575#.XDebSM17lPY</a></i></p>
8282

8383
<br/>
8484

@@ -654,7 +654,7 @@ There is so much potential material out there that it would take years of contin
654654

655655
- [Gareth O'Neill](https://twitter.com/gtoneill), Language Lubber
656656
- [Bruce Caron](https://twitter.com/junanaguy), Culture Work Architect
657-
- [Jo Havemann](https://twitter.com/Access2Perspectives), #ResearchinAfrica Highlighter
657+
- [Jo Havemann](https://twitter.com/johave), #ResearchinAfrica Highlighter
658658
- [Jon Tennant](https://twitter.com/protohedgehog), Dinosaur Whisperer.
659659

660660
<br/>

content_development/Task_1.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ For automatic links use [square brackets](https://www.google.com) and then inser
104104

105105
For images, use an exclamation to indicate this and then a link to the image location:
106106

107-
`![image](https://github.com/OpenScienceMOOC/Module-1-Open-Principles/blob/master/content_development/images/logo.png)`
107+
`![image](https://github.com/OpenScienceMOOC/Module-1-Open-Principles/blob/master/content_development/images/Logo.png)`
108108

109109
Some times you can also add in bits of HTML here if you want to be a bit fancier, which can help with display issues too some times:
110110

key_elements.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -134,8 +134,6 @@
134134

135135
* [Vienna Principles](http://viennaprinciples.org/): A vision for scholarly communication.
136136

137-
* [Summer School Open Science course](https://www.utrechtsummerschool.nl/courses/science/open-science-and-scholarship-changing-your-research-workflow), Utrecht University.
138-
139137
* [A short lecture on Open Licensing](https://figshare.com/articles/A_short_lecture_on_Open_Licensing/4516892/1) (Lorena, 2017; presenter notes also on [SpeakerDeck](https://speakerdeck.com/labarba/a-short-lecture-on-open-licensing). [Bonus interview](http://rtalbert.org/blog/2015/interview-lorena-barba)).
140138

141139
* [The Panton Principles of Open Science](https://en.wikipedia.org/wiki/Panton_Principles).

production_toolkit/MODULE_DESIGN_PROTOCOL.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,8 @@ This is a collaborative, team-based effort. Each module has its own repo on GitH
88
2. [Open Collaboration](https://github.com/OpenScienceMOOC/Module-2-Collaborative-Platforms)
99
3. [Reproducible Research and Data Analysis](https://github.com/OpenScienceMOOC/Module-3-Reproducible-Research-and-Data-Analysis)
1010
4. [Open Research Data](https://github.com/OpenScienceMOOC/Module-4-Open-Research-Data)
11-
5. [Open Research Software and Open Source](https://github.com/OpenScienceMOOC/Module-5-Open-Research-Software-and-Ope)
12-
6. [Open Access to Research Papers](https://github.com/OpenScienceMOOC/Module-6-Open-Access-to-Resea)
11+
5. [Open Research Software and Open Source](https://github.com/OpenScienceMOOC/Module-5-Open-Research-Software-and-Open-Source)
12+
6. [Open Access to Research Papers](https://github.com/OpenScienceMOOC/Module-6-Open-Access-to-Research-Papers)
1313
7. [Open Evaluation](https://github.com/OpenScienceMOOC/Module-7-Open-Evaluation)
1414
8. [Public Engagement with Science](https://github.com/OpenScienceMOOC/Module-8-Public-Engagement-with-Science)
1515
9. [Open Educational Resources](https://github.com/OpenScienceMOOC/Module-9-Open-Educational-Resources)
@@ -27,14 +27,14 @@ This is a collaborative, team-based effort. Each module has its own repo on GitH
2727
2. Expectations of what each will contribute and receive from taking part.
2828
3. An explanation of time scales and commitments.
2929
4. An exploration of the MOOC module, the design and development protocol, the knowledge that will be included, and what the challenges to be addressed are.
30-
5. The core learning outcomes and mission objectives for the module. These are all defined in the [Proposed Modules](https://opensciencemooc.eu/proposed-modules/) section of the companion website for the MOOC.
30+
5. The core learning outcomes and mission objectives for the module. These are all defined in the [Proposed Modules](https://opensciencemooc.eu/modules/) section of the companion website for the MOOC.
3131
3. Setting a timeline and action plan for development.
3232
4. Acquiring team information. Each team member will be required to provide:
3333
1. A profile picture.
3434
2. A short bio.
3535
3. Twitter handle (where appropriate).
3636
4. Personal website (where appropriate).
37-
5. Publicising the team to the MOOC companion website, [here](https://opensciencemooc.eu/about-us/production-team/).
37+
5. Publicising the team to the MOOC companion website, [here](https://opensciencemooc.eu/people/#production).
3838

3939
## The development process
4040

0 commit comments

Comments
 (0)