forked from rstudio/bookdown-demo
-
Notifications
You must be signed in to change notification settings - Fork 13
/
00-syllabus.Rmd
120 lines (69 loc) · 12 KB
/
00-syllabus.Rmd
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
# Preface {-}
## Course Syllabus {-}
The most up-to-date syllabus is <a href="https://docs.google.com/document/d/1Z39J9Hn-qn2iKcrVzpMz3nm60ThnGKZMZQ_cWJSlUOg/edit?usp=sharing" target="_blank">here</a>.
Please leave comments on the syllabus if you have any questions.
### What to expect each week? {-}
This online class is designed to offer rich opportunities for social participation. Below is an infographic showing how a week would (typically) look like.
- **Our class meetings happen on Tuesdays.** The class meetings are designed for us to chat about things we've learned, gaps of understanding, future plans, etc. In some weeks we will meet in Gather; in some other weeks, we will "meet" on Slack throughout Tuesday.
- **A fresh week starts on Wednesdays.** Depending on your schedule, you can get started with course readings and begin to make annotations.
- **By the end of Friday**, you are expected to finish reading articles assigned for the week and post your personal annotations on Hypothesis.
- **By the end of Monday**, you are expected to check out what other colleagues annotated and reply to each other. You will receive an email notification when someone responds to you. It is hoped that by putting our minds together we can develop deeper understanding.
- On Tuesday, we chat more on Slack or Gather. Detailed guidelines will be posted each week.
## Why not Canvas for this course? {-}
To learn social network analysis (SNA) -- and many other stuff -- I believe the best way is to 'live' with it. That is, the best way to learn SNA is to seize every opportunity of applying SNA in one's own learning journey. This philosophy leads to two major reasons I'm piecing together a learning environment by myself:[^1]
- First, as an instructor I wish to foster **social interaction** as much as possible. Traditional learning management systems, like Moodle and Canvas, do not prioritize this goal
- Second, to **practice SNA with our own 'learning traces'**, system log data[^2] need to be somehow exposed to users. Traditional systems are less transparent in this area.
If you haven't used these tools mentioned above, no worries. I will provide detailed guidelines to get you started (see the next section). **Many of us would be venturing out of our comfort zones.** (SO DO I -- because I cannot stop trying new things :-).) I hope we will all learn a great deal about SNA and beyond.
Have fun!
[^1]: I've published these ideas as [a *design case* on TechTrends](https://link.springer.com/article/10.1007/s11528-018-0284-7) if you're interested in reading more.
[^2]: I treat 'data' as [plural](https://en.oxforddictionaries.com/definition/us/data) in the course.
## Two tracks of participation {-}
This course website is openly available online, reflecting my committment to '[open scholarship](https://uark.libguides.com/openscholarship)'. So there are two tracks of participation designed for this class.
1. **UMN class**: For UMN graduate students enrolled in the class, your participation in this class is not that different from taking another online class. You are expected to meet course requirements outlined in the course syllabus. You will have *private spaces* (on Slack and Hypothesis) for within-class communication.
2. **Open participation**: For 'Open Participants' who are following the class, you can access the same materials I curate on this website. You may need to buy the required textbook if you do not have a library access. And ways for you to participate include 1) making public Hypothesis annotations using tag `SNAEd`, and 2) tweeting out your ideas or links to your blog posts using hashtag `#SNAEd`.
<!-- Open Participants accomplishing major course requirements will be offered [Digital Badges](https://openbadges.org/). -->
If you have any feedback on the current design, please get in touch. I'd love to hear your thoughts.
## Digital learning environments {-}
This is a **fully online** class. An online course does not need to be about watching videos and answering quizzes. To foster rich learning experiences, we will be using several technological tools to foster social, collaborative learning. Depending on your familiarity with these tools, there could be a learning curve. So please spend time this week to familiarize yourself with them.
Below is a list of them and we could tweak the list when moving forward.
**Bookdown course site**. This website you're reading is built by myself using `Bookdown`. `Bookdown` is designed for writing books. While this site may evolve into an open textbook, I'm using it as our course portal.
Course resourses, usually organized by weeks, will be published here. Weekly course annoucements will be pushed to the class through Slack (more below). (If you are an 'Open Participant', just check this website every Tuesday!)
**Gather**. You will receive a calendar invite to all class meetings in a virtual space named [Gather](https://gather.town/). It is an alternative to Zoom but gives us more options to socialize in a more organic manner. Watch the video below to get started. Check out the [documentation page](https://gather.town/docs/) if you wish to learn more.
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/8orexZsFRxs" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
**Slack** (UMN Students Only). You will receive a link that invites you to join [our Slack community](https://la-mn.slack.com/). Course announcements are made on Slack. All sorts of class discussion will take place there as well. First time using Slack? Watch the video below and/or read this [brief introduction to Slack](https://get.slack.help/hc/en-us/articles/115004071768-What-is-Slack-).
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/9RJZMSsH7-g?rel=0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
To get started with Slack, get familiar with a few **Slack terms** you need to know [^3]:
- **Messages** or **Updates** — the basic message or status of Slack. Similar to Facebook updates, tweets, chats, etc.
- **Channels** — like separate rooms within the domain. They can be *public* or *private*.
- **Direct Messages** — like DMs or private messages anywhere else.
- **Posts** — longer than a status update. Similar to a blog post or a Word document. Once it's shared to a *Channel*, folks can **comment** on it or even **edit** it if the owner allows.
- **Snippets** — Chunks of syntax-highlighted code for when that’s the thing you need to share. We *might* use it.
- **\@replies** — much like on Twitter, used when you want to mention someone. You can \@everyone or \@channel.
- **emoji** — just like what you see everywhere.
- **Integrations** — Slack can 'talk' with many other systems. For example, you can post a doc from your Google Drive when submitting an assignment; you can type `/giphy` to share random gifs. I will explain more later.
To learn more, check out the [Slack tutorials](https://get.slack.help/hc/en-us/categories/200111606-Using-Slack).
**Hypothesis**. If you're a formal participant, you should have received a link that invites you to join a private Hypothes.is group. Hypothes.is is a web annotation tool that enables us to discuss readings in a contextual manner. When annotating, please make sure our group name (**SNAEd**) is properly selected. *Pro Tip*: Please try to use a same (or at least a smilar) username for Slack and Hypo so that we can match you in two spaces.
If you are an Open Participant, please annotate publicly and make sure to tag your annotations with `SNAEd`. Otherwise, it will not be picked up by our [class feed](https://hypothes.is/search?q=tag%3ASNAEd).
To learn more, check out [Hypothesis Quick Start Guide for Students](https://hypothes.is/quick-start-guide-for-students/), and [a more complete Resource Guide for Students](https://hypothes.is/student-resource-guide/).
<!-- **Zoom**. We will host virtual meetings on Zoom from Week 7. Please make sure your computer has [Zoom](https://zoom.us/) installed (see the video below). Please test your Zoom setup in advance to make sure audio and video configurations work properly. You will receive a calendar invitation with details about joining our Zoom meetings. -->
<!-- <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/vFhAEoCF7jg?rel=0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe> -->
**Twitter** (optional). If you tweet, like [me](https://twitter.com/bod0ng), please tag your tweets with `#SNAEd` as well.
To demonstrate how Twitter could be useful, I bet you can learn more from [TechPizza](http://techpizza.org/twitter.php) than from this course (set Topic to be, for example, 'Text, Network Analysis' --> 'network:gephi').
**Google Drive**. Google Drive will be used for major assignment submissions. I will provide detailed feedback directly in your Google Docs, so it is important you use Google Drive. UMN offers free Drive access and unlimited storage. If you need help, check this OIT page: https://it.umn.edu/technology/google-drive
<!-- To submit an assignment through Slack, head to the #assignment Slack channel and click on the '+' button to pull out a menu with opitons of adding Drive files. You may need to authenticate Google Drive on Slack. See [help page](https://get.slack.help/hc/en-us/articles/205875058-Google-Drive-for-Slack). -->
<!-- ### Integrations -->
<!-- We are using multiple systems in this class. And I am fully aware that it may cause disorientation especially in the first one or two weeks. Please keep in mind Slack is the place for us to hang out, and other things -- course content on our course site, Hypo, Drive -- will be somehow integrated in our commucations on Slack. -->
<!-- - **Course site -> Slack**: When new content is published (weekly in most cases), I will send out an annoucement in the `#annoucement` channel. -->
<!-- - **Hypo -> Slack**: Hypo annotations properly posted using our `#SNAEd` tag will be notifed in Slack's `#hypo_feed` channel. -->
<!-- - **Drive -> Slack**: You can directly add Drive files into Slack when submitting a 'larger' assignment (e.g., project paper, presentations, essays). -->
<!-- - **Slack -> Email**: Depending on your preference settings, you will receive some notification emails from Slack. The default settings will email you Private Messages. You can change [your email preferences here](https://snaed.slack.com/account/notifications). -->
## Ways to contribute to this site {-}
This is the 3rd time I am offering this course. By making this course site open, I hope it could be useful beyond the formal class and was thrilled see tweets like this one:
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Very inspiring course book shared by <a href="https://twitter.com/bod0ng?ref_src=twsrc%5Etfw">\@bod0ng</a> about Social Network Analysis in Education <a href="https://t.co/w85Rf5AVs9">https://t.co/w85Rf5AVs9</a> <a href="https://twitter.com/hashtag/SNA?src=hash&ref_src=twsrc%5Etfw">#SNA</a> <a href="https://twitter.com/hashtag/SNAEd?src=hash&ref_src=twsrc%5Etfw">#SNAEd</a></p>— Marco Kalz (\@mkalz) <a href="https://twitter.com/mkalz/status/1346413687670763520?ref_src=twsrc%5Etfw">January 5, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
I'd appreciate your help to continually improve the site and here are ways you can contribute:
1. The best way to contribute to this site is to annotate it using [Hypothesis](https://Hypothes.is/). For example, to point out a possible spelling error, you can highlight the error and include two tags -- `SNAEd` and `issues` -- in your annotation.
2. The second best way is to report a `New Issue` on this website's [Github issues page](https://github.com/meefen/sna-ed/issues).
3. If you're Github-savvy, please consider forking the [Github repository](https://github.com/meefen/sna-ed/), making edits, and sending me a pull request.
4. If none of those options work for you, simply drop me an email at chenbd\@umn.edu.