Editing CommunityData:Meetup July 2017/Infrastructure

From CommunityData
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
== Zotero ==
== Outline ==
=== Zotero ===


Instructions are online at [[CommunityData:Zotero]]
Checkoff list before we start:


== Git (migration to gitolite from wikiresearch) ==
* Everybody upgrade to Zotero 5.0. You will need to download this from https://www.zotero.org because it was released recently and its not in the distributions yet. It's important to be running the new version. This will break support for BetterBibLaTeX but is also fixes most of the bugs that required this in the first place.
* Everybody make sure you have joined and a member of the [https://www.zotero.org/groups/163394/community_data_science_collective Community Data Science Collective Zotero repository].


Details on setting up Gitolite are already pretty clearly documented over at [[CommunityData:Git]].
Things that everybody should know:


The rest of this section covers migration of the wikiresearch repository off of Github. We'll be doing this at the session and disable/deleting the old repository then.
* In Zotero, folders are not like traditional folders. They are like tags. Do not add things if they are already there!
* Holding down <tt>Alt</tt> is extremely useful! It will show you which folders the selected item is in!


The process to add something cleanly is complicated but should always include the following steps:
# Check to see if it's in the CDSC shared folder by clicking on the top level of the shared group and searching. If it is already there, just drag it into your new subfolder for your project. If it's not, click back on your sub-folder and add it.
# Once you've added, change the title to sentence case. You can do this by: (a) ''Right clicking on Title → Transform Text → Sentence Case'' (b) you will then need to capitalize any proper nouns (e.g., Scratch, Wikipedia) as well as anything immediately following a ":". This is important because software like BibTeX/BibLaTeX can change from "Sentence case" to "Title Case" automatically, but not the other way around. APA 6 requires sentence case.
# Ensure that there's a DOI for your entry if it's necessary. Some publishers and conferences (like AAAI publications which publishes ICWSM) do not have DOIs. If your publication does not a DOI, it needs to have a URL because APA 6 requires one or the other.
# Edit & clean the Publisher field. According to [http://blog.apastyle.org/apastyle/2010/01/the-generic-reference-where.html APA 6 style] we should drop common words like "Press," "Publisher," "Inc." as well as first names (i.e., just Wiley, not John Wiley Inc.)
# Edit & clean the Place field. [http://blog.apastyle.org/apastyle/2010/01/the-generic-reference-where.html APA 6 style] requires "City, State" within the USA and "City, Country" outside. So, it's "New York, New York" for the ACM and "Cambridge, UK" for University of Cambridge Press.
# Remove anything in the "Extra" field unless it's something you want to be printed every time. Sometimes things like "ⓒ JSTOR" sneaks in.
# Make sure that there's a PDF attached and then rename the PDF to ''Name-YYYY-Short_title.pdf''. You can do this by: ''Right click on PDF → Rename File from Parent Metadata''
# Ensure that there aren't extraneous files attached. Just delete anything that doesn't look critical or useful. Keep in mind that anything attached will show up in fulltext searches which can be a reason to either leave something or remove it depending on what it is.


If you do <code>git remote -v</code> you should all see something like this:
If you add multiple copies (or if you just think you have), do not just delete the old version since that will remove it from folders you might have merged it into. Instead you should merge them:


origin git@github.com:aaronshaw/wikiresearch.git (fetch)
# Ensure that both are the same type (e.g., both are articles). This may involve changing one to the other.
origin git@github.com:aaronshaw/wikiresearch.git (push)
# Click on both by holding down <tt>Ctrl</tt>
# Right click on either and select ''Merge''
# Look at the combined items and delete an duplicate PDFs.


The first word might be different but the important thing to take note of is that word (i.e., “origin”).  
When you're done adding a bunch of things, look at the ''Duplicate'' pseudo-folder underneath the ''Community Data Science Collective'' folder.


First you need to add the new repository and pull down objects like:
=== Git===


git remote add communitydata git@code.communitydata.cc:wikiresearch
Details on setting up Gitolite are already pretty clearly documented over at [[CommunityData:Git]].
git fetch communitydata
git push --set-upstream communitydata
git remote remove origin
git remote rename communitydata origin
 
Check to see if you have multiple branches:
 
git branch
 
If you do, and you want to push them all, you can do that with:
 
git push --all origin
 
== Planning documents repository ==
 
We'll create one on the community data server. Nearly everyone should clone it and contribute once we do! There's also one [[CommunityData:Planning_document|here]]
 
== Move RCommunityData to its own repository ==
 
This needs to happen. It's another one that nearly everyone should clone once it exists.
 
== Communication channels ==
 
=== Internal ===
Since we're a distributed organization, it's pretty important to keep track of the ways/media we use to communicate and how they get used. Here's a pretty current list:
 
* [https://wiki.communitydata.cc/CommunityData:Email email lists] (collective, collective-''university'') — announcements, event coordination
* [https://wiki.communitydata.cc/CommunityData:Resources#Chat_on_IRC IRC] — ongoing water cooler; sharing random stuff; ad-hoc group/pair conversations
* wiki — archive of shared resources; asynchronous project coordination


You could probably add jit.si to this list and include our bi-weekly meetings. Anyhow, the point is that each of these plays an important role already and we should discuss whether/how they're working. In particular, Aaron and Mako want to make sure that our internal communication channels are accessible and inclusive for all group members.
* Troubleshooting anybody's git/gitolite setup.
* Migration of the wikiresearch repository from Github over to Gitolite:


=== External ===
=== Migration of wikiresearch ===


We also communicate externally with a few channels:
== Ideas of things to cover in an infrastructure and hygiene session ==


* [https://blog.communitydata.cc/ blog.communitydata.cc]
* gitolite
* [https://twitter.com/comdatasci @comdatasci on Twitter] — you all should have access to this on Twitter.
* mailing list
* IRC
* Zotero(!!)
* Migration away from the wikiresearch hosting on Github
* Planning documents (creating a shared repository?)
* Wiki organization
* Move RCommunityData to it's own git repository
Please note that all contributions to CommunityData are considered to be released under the Attribution-Share Alike 3.0 Unported (see CommunityData:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)
Retrieved from "https://wiki.communitydata.science/CommunityData:Meetup_July_2017/Infrastructure"
Attribution-Share Alike 3.0 Unported
Powered by MediaWiki