This page collects resources for Community Data Science Collective members.
Technical documentation and getting setup
- CommunityData:Backups (nada) — Details on what is, and what isn't, backed up from nada.
- CommunityData:Beamer — Installing/using Mako's beamer templates
- CommunityData:Build papers — Both the TeX and Beamer templates above come along with a Makefile that makes some assumptions about your workflow. Learn about that here.
- CommunityData:Code — List of software projects maintained by the collective.
- CommunityData:Email — Information on email aliases and their management.
- CommunityData:Embedding fonts in PDFs —
ggplot2creates PDFs with fonts that are not embedded which, in turn, causes the ACM to bounce our papers back. This page describes how to fix it.
- CommunityData:Exporting from Python to R
- CommunityData:Git — Getting set up on the git server
- CommunityData:Hyak — Using the Hyak supercomputer system at UW for reserach.
- CommunityData:Hyak setup — Getting an account and getting setup on Hyak.
- CommunityData:Northwestern VPN — Connecting to the Northwestern VPN
- CommunityData:Jargon — Jargon and Common Shorthand
- CommunityData:Knitr — Using Knitr with Tex to build graphs, tables, insert and format numbers in tex documents.
- CommunityData:Planning document — Details on producing Matsuzaki-style planning documents
- CommunityData:reveal.js — Using RMarkdown to create reveal.js HTML presentations
- CommunityData:TeX — Installing our LaTeX templates
- CommunityData:Tmux — Using tmux (terminal multiplexer) to keep a persistent session on a server.
- CommunityData:Zotero — How to use our shared Zotero directory.
- CommunityData:Wikia data — Documents information about how to get and validate wikia dumps.
- CommunityData:Hyak Spark — Documents how to use Spark on Hyak
- CommunityData:ORES - Using ORES with wikipedia data
- CommunityData:Message Walls -- Documents information about how to get and validate wikia dumps.
Ongoing and Future Meetings and Meetups
Meetings and Meetups of Past
- Sociotechnocanonicon Great Books Discussion Series
- CommunityData:Meetup September 2018
- CommunityData:Meetup April 2018
- CommunityData:Meetup April 2018: Organizational notes
- CommunityData:Meetup July 2017
- CommunityData:UW Weekly Meeting
- Schedule — Deadlines, events, and simialr
- CommunityData:Logos — Like our visual branding, not like λόγος. Although we should always make sure we're good in that department too.
- CommunityData:Advice on writing a background section to an academic paper — Once upon a time, Mako and Aaron submitted a paper with a mediocre introduction to a journal. Mac Parks, the editor of that journal at the time, set us straight with some very clear pointers. Save yourself the trouble and learn to follow these today!
- Community Data Science Lab (UW) — Directions to the lab space at UW. This is something you can share with visitors.
University of Washington Resources
Chat on IRC
A number of us are idling in #communitydata on OFTC (irc.oftc.net). IRC is basically a chat system that is similar to Slack in many ways (it was actually the inspiration for Slack!).
To use IRC, you'll need a client. A really good one for folks new to IRC is IRCCloud. With IRCCloud there is a web interface as well as good Apps for iOS and Android.
One limitation of IRCCloud is that, after a 1-week trial period, the system will disconnect folks every two hours. There are a couple options for this. The easiest one is subscribing to IRC cloud which costs $5/month or $50 a year. Mako or Aaron will foot the bill. The other is to connect through an IRC "bouncer." Talk to Mako about this if you're interested in this approach. He can run one for you.
Another option for those wanting a persistent connection without setting up a bouncer (such as ZNC) is to connect via the Matrix protocol. While there are numerous clients, Salt recommends Riot which is freely supported on every platform. Join the room `#_oftc_#communitydata:matrix.org` to bridge into IRC.
Due to spam, we are now blocking all "non-registered" users from posting to #communitydata -- which should help a lot with the spam. But the disadvantage to this setting is that if you speak on the channel but are not registered, we won't be able to hear you!
If you've already done this long ago, you can stop reading, there's nothing new to do. If you haven't gotten fully registered and verified, here are the four "easy" steps, heavily mediated by the NickServ bot:
1 - From IRC (irc.oftc.net), /msg NickServ register <<your password>> <<your email>> 2 - Verification is via the website, see:  3 - Ask NickServ 'checkverify' and she'll tell you if you're verified. 4 - Please say something on the channel to test. If you do not get a response, your messages can still be seen by community members. /msg mako or ashaw for help.
The light in the lab at UW is funny. We have three fluorescent lights. On flipping the light switch, only two turn on. The third turns on eventually. We are studying this arcane phenomenon over at CommunityData:Light events
- CommunityData:GameIDs — A directory containing the game IDs for CDSC members to connect with each other across various gaming platforms.