shawngraham

Agenda

• formal administrative requirements
  • how these play out
• purpose and structure
  • of a thesis
  • of an MRE
  • know the culture of your department!
• DH can but doesn't have to mess with structure
• Strategies

shawngraham

extensions [import-a fetch]
;;; SETUP PROCEDURE

to setup
  clear-all
  let thing (fetch:url (word "https://raw.githubusercontent.com/SantaFeInstitute/ABMA/master/ch1/ch1_map.png"))
  import-a:pcolors thing
  create-turtles 20                        ; create 20 agents
  [                                        ; with the following state variables:
    set color random 140                   ; color

shawngraham

http://air.decontextualize.com/tracery/

https://cheapbotsdonequick.com/source/tinyarchae

https://web.archive.org/web/20170428023005/https://electricarchaeology.ca/2017/04/27/bots-of-archaeology-machines-writing-public-archaeology/

https://programminghistorian.org/en/lessons/intro-to-twitterbots

shawngraham

import requests, re, json, types, traceback

class HypothesisAnnotation:

    def __init__(self, row):
        """Encapsulate relevant parts of one row of a Hypothesis API search."""

        self.tags = []
        if row.has_key('tags') and row['tags'] is not None:
            self.tags = row['tags']

shawngraham

# demo for sharing a script
# in scripts, a hashtag (pound sign) = a comment (in markdown, it means a header)

# we create a variable called y, and give it a _string_ of text; in this case, the direct URL to a csv file 
y <- "https://raw.githubusercontent.com/shawngraham/exercise/gh-pages/CND.csv"

# now we use the read.csv command to read the file address stored in 'y'; the results go into a dataframe called 'documents2'
documents2 <- read.csv(y)

shawngraham

library(rvest)
library(dplyr)
library(xml2)
library(stringr)
library(purrr)

base_url <- "https://curve.carleton.ca"

theses = data.frame()

shawngraham

shawngraham

shawngraham

#!/usr/bin/env python
# source: https://gamedev.stackexchange.com/questions/23659/is-there-a-way-to-procedurally-generate-the-history-of-a-world
# to create a visualisation, run like this:
#    ./historygen.py --dot | dot -Tpng > filename.png
# brew install graphviz to get the dot files rendering
# to have the story, run like this:
# ./historygen.py
# have your state names in the names.txt file
# now, all of this *could* be done with tracery i suppose, but you can see the bones of the
# history system could be expanded to model other aspects, keep track of things, calculate new things. 

shawngraham

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="text"/>

<xsl:template match="/">

<xsl:for-each select="article/front">
"<xsl:value-of select="article-meta/contrib-group/contrib/string-name/surname" />, <xsl:value-of select="article-meta/contrib-group/contrib/string-name/given-names" />" <xsl:text>&#9;</xsl:text><xsl:value-of select="article-meta/pub-date/year" /> <xsl:text>&#9;</xsl:text> "<xsl:value-of select="article-meta/title-group/article-title" />" <xsl:text>&#9;"</xsl:text><xsl:value-of select="journal-meta/journal-title-group/journal-title"/>"<xsl:text>&#9;</xsl:text> "<xsl:value-of select="article-meta/volume" />(<xsl:value-of select="article-meta/issue" />)" <xsl:text>&#9;</xsl:text> "<xsl:value-of select="article-meta/page-range" />" <xsl:text>&#9;</xsl:text>"<xsl:value-of select="article-meta/article-id" />" <xsl:text>&#9;</xsl:text><xsl:value-of select="article-meta/self-uri" /><xsl:text>&#xA;</xsl:text>
</xsl:for-each>