Image Image Image Image Image Image Image Image Image

CHI Grad Fellow Post

Nikki Silva

By

March 24, 2017

Directory of Oneota Scholars: Tracking Them Down

March 24, 2017 | By | No Comments

My last blog post addressed the criteria of inclusion I am using for the Directory of Oneota Scholars. As I was collecting names of scholars, I had to eventually stop and begin working through this corpus to gather information on their current research interests, position, the institution (or entity they are at), and a website for contacting the individual. To track down this information, I have mainly used Google to search for individual’s names on their own and then with ‘archaeology’ in the search bar. It has been a bit difficult to track down current information on multiple scholars: out of 110 scholars, I have no current information on 14 individuals. I will continue to try and gather information on these individuals and begin filling my website with the content. Thankfully, I have already created my website and a coding template for each scholar, and the site is ready to be populated. I hope to finish populating the site with content in the next month. Please comment below if you have any questions about the project!

mahnkes1

By

March 24, 2017

The Rhetoric of Code

March 24, 2017 | By | No Comments

When working to persuade an audience, one assumes to mostly wrestle with whatever’s rendered on the other side of the code. The archaic mess of symbols tucked under the rug of GitHub files is kept cleanly from view—or especially interest—from the community I work with, because the rhetoric of the rendered site seems to be what counts most, the public face with the most agency. For example, as I continue to construct my site for Filipinx-American spaces, I begin to lean more heavily toward the Fil-Am community in terms of their needs and how the website could possibly contribute to meeting those needs. The process is a loop wherein I present the current manifestation of the site to community members with an assumption toward their needs, and their feedback corrects those assumptions, sending me back to the rebuilding of the site. The feedback loop continues (on and on, it seems, at this stage of the semester). None of them care for how I manipulate code, nor do I think to persuade them of my hefty inelegant patchwork of code adopted from several online spaces.

This last week, however, I’d been introduced to the rhetoricity of code, adding yet another layer to community work and the persuasive complexity within digital literacy.

At this year’s Conference on College Composition and Communication, Dr. Kevin Brock’s presentation “Treating Code as a Persuasive Argument” drew attention away from the often emphasized instrumental power of code toward its rhetorical capacity. Exploring a user’s proposal on Ruby Rails to improve code logic’s efficiency in determining a default layout, Brock revealed how the discourse of the proposal’s reception illuminated code’s ability to perform, measure against existing code, measure in terms of readability, measure in potential to bring further code improvements, and demonstrate potential applicability to other pages. The prioritized elements of code logic and representation point to the particular values of a digital discourse, one that may inform the persuasiveness and argument underlying any proposed code.

Fortunately for now, crafting a persuasive set of code is beyond my skill set. Admittedly, I’m not so discriminant in finding and adopting a code as long as it renders something decipherable and functional on the other end. Despite this, I can appreciate Dr. Brock’s insights into the rhetoricity of code which sheds light on the engagement of programmers and communities behind the scenes as another complex discourse that digital literacy grapples with. It also brought to my attention the idea of how adoption of certain codes for particular functions could culturally rewrite the code’s original use in the community, consequently helping to disperse a re-appropriated version. An example of this could be the innocent use of codes traditionally (and originally) used for listing as a new means for paragraph indenting. In these ways, code evolves as any other language, though with functionality seemingly dictating the values and hence direction of its evolution (for now, and put in extremely simplified terms).

In a sense, with digital composing, I realize I don’t just work with the community that drives my content. Especially with a public repository on platforms like Github, I could also potentially be engaging with the coding community.

Jack Biggs

By

March 17, 2017

Making headway…finally

March 17, 2017 | By | No Comments

The past few months have been incredibly frustrating as I made little headway in creating my clickable SVG of a juvenile skeleton using Raphaël.js.  By clicking on a certain bone, the user would be taken to another page corresponding to age estimation methods for that bone and use the features specified to come up with an estimated age.  Since clickable SVGs are created as paths that have beginnings and endings, each path corresponds to either a single bone or a closed path on a bone.  As a result, this means that each bone would have its own link, so to simplify the process, entire regions of bones will be selected at once no matter which bone you click on.  The skeletal regions have been split up according to standard anatomical regions: skull, thorax (ribs, vertebrae, sternum), upper limbs (hands, forearms, arms, clavicles, scapulae), pelvic girdle (pelvis and sacrum), and lower limbs.

Although I appeared to have the correct links and format for Raphaël.js, nothing would work and nothing showed up on my webpage.  Fortunately, I think I have found a way around that.  Instead of linking raphaël.js and my skeletal SVG data paths from separate files, I was able to successfully link embed the SVG data directly into the body of my html page without even using raphaël.js.  Downside is that this makes the code on my html page much longer and look less clean.  However, it correctly links and works and so I’m happy to have slightly less concise code if it means that one of the main functions will work!

As an example, I’ve copied and pasted my example here (https://jabiggs13.github.io/skull-test/).  For right now, the outlines of the skeleton are linked to another website so when you click on a feature, it takes you to eskeletons.org – a website created by the Department of Anthropology at the University of Texas at Austin dedicated to teaching basic human skeletal anatomy as well as focusing on other primate skeletal morphology.  (This was honestly the first site that popped in my head when testing to see if the linking feature of my SVG worked).

As it stands right now, there is a major problem that I had not anticipated.  The only portion of the skeleton that is truly clickable is the outline of each bone, not the actual bone itself.  This was not a problem I had thought about until I finally got everything working.  My solution to this problem is basically messing with the original paths and outlines of the SVG so that the space between the outline is filled in and is the actual clickable content.  With this process, there are now exponentially more paths, meaning that there are way more individual closed loops that would require their own separate links as the program (Inkscape – free!) is no longer recognizing my grouped regions (i.e. it is not recognizing the ‘ribcage’ but each individual rib or piece of rib that is its own separate loop).  Though less than ideal, this may just be the nature of the beast so that each individual path would then have to have its own link, making my skeletal regions less useful as an overarching theme.

Despite this newest hiccup, I am incredibly relieved to be past this one major hurdle do I can now focus on each of the individual ageing methods that will link up to specific bones.

Links:

http://eskeletons.org/

https://inkscape.org/en/

Jessica Yann

By

March 16, 2017

Project Update!

March 16, 2017 | By | No Comments

Greetings all! I don’t have many exciting new developments to report on my CHI project, so instead I thought I would share with you some screen shots of where I am at right now, and some of the pieces I could use help on.  The first is coming up with a flashier banner to go across the top. You can see my current placeholder banner below:

Along with that, I need a flashier title for my project.  You should be able to access it here, if you want to take a look at it in its current state. I’m still working on formatting, so you may still see some odd placement, off font size, or other issues.  However, please point them out!

All that aside, I have been learning a lot about how to make archaeological information accessible to the public. It is a lot more difficult than I anticipated to take the language from a National Register form, convert it into something that a school kid could understand, and maintain the information about why that site is importance.  I’ve done more editing on the text for each of my timeline events than on anything else!  We often underestimate the importance of communicating archaeology to the public. One of my main goals with this project is to successfully show how important archaeology is to understanding our past.  I hope by the time I am finished I will have succeeded, at least somewhat, in doing just that.

nesbit17

By

March 1, 2017

Getting Back to the Basics: Reducing the Content of My Site

March 1, 2017 | By | No Comments

My original vision for this project was to make a website showcasing the work I have been doing in collaboration with my colleagues in the Sociolinguistics Lab at MSU.  We’ve been documenting speech in the Greater Lansing Area over the last few years and have come across some unexpected trends…speech in Lansing is moving away from the prototypical rust-belt dialect and towards a more western (maybe Californian) dialect!

The website was going to showcase these facts. My earlier vision also included showcasing the sociolinguistics literature and previous findings regarding the Michigan dialect, commenting on how variationists like myself usually differentiate between dialects.  This then turned into having to describe (socio)linguistic theory and Bill Labov and vowel formants and standardization and OMG.  Waaay too much information.

Needless to say, I had a talk with myself and decided that I should just stick to the facts.  The stuff people, linguists and non-linguists alike, care about.  So, for better or for worse, my website is much simpler than originally planned, but I think it’s for the best.  No one wants to read the equivalent of a novel when they visit a website, right? Right!

nesbit17

By

March 1, 2017

Slowly

March 1, 2017 | By | No Comments

I wrote this in January and never published it, so here goes anotha try

I’ve done away with Bootstrap and am giving it a go with HTML and CSS.  Everything is coming along… slowly but surely.  I wish I could globally change my sub-pages, but am not savvy enough to know how. Lots of copy/paste going on.  Still pondering a name for the website.  It’ll likely come to me in a dream.

swayampr

By

February 27, 2017

Working out NorrisTown!

February 27, 2017 | By | No Comments

In the last month, I have begun putting the innards of my website together. Unsurprisingly it was difficult. But I am happy to report some progress! At this point, I am working towards making a page that whose format I would like to replicate in the other pages. In other happy news, I was able to procure some archival material (thanks to the internet and sagacious archival staff at Cornell University and the National Archives in Atlanta), seminal to my project.

In working out a page format I liked, I first went to a front end platform like Bootstrap. Unfortunately, what I wanted needed too many changes to the template. So I just began working ground-up. As someone new to JavaSript and CSS, I prefer to have everything at one place. It might be a slightly archaic way of working and definitely pedantic, but it’s the one way I am able to work on ‘website stuff’ without having to work again on a separate CSS file etc.

Broadly speaking the website will have five sections: about; ‘Norris: A Utopia’; ‘Understanding Norris’; ‘Photographing Norris’; ‘Company Towns in America’. Each of these sections will further have a drop down menu listing out sub-sections.

The section exploring Norris as a utopia will explore the imaginations that understood Norris as a utopia. It will explore the utopian nature of Norris through newspaper clippings, material generated by the TVA to justify Norris and extoll its virtues, press releases, and essays/commentary by architects and planners of Norris (this is where the Earle Draper papers would feature heavily).

Housing in Norris was based on typologies. The next section, ‘Understanding Norris’ will trace the rationale of the housing typologies, the housing typologies themselves and relating the typologies to plans, elevations and housing types.

As an important infrastructural project the Norris Dam was important for the TVA in many ways. As a project undertaken during the Great Depression, the Norris Dam and the town of Norris were photographed extensively by the Farm and Security Administration (FSA)- Office of War Information[1]. The photographs are available at the Library of Congress website. The next section then will showcase the FSA photographs, in addition to photographs of Norris from newspapers etc.

Lastly, Norris was company town. The last section will examine briefly, a history of company towns in the United States through essays and book sections. This section will also showcase further sources that readers can access on company towns.

On a personal note, I have begun to work in and through GitHub, a platform that has been giving me nightmares for many months now!

The page format I am veering towards is here . I would really appreciate any feedback you might have!

Also, I am really looking for a fun title. I welcome all ideas!!

[1] For more see http://www.loc.gov/pictures/collection/fsa/

Nikki Silva

By

February 24, 2017

Directory of Oneota Scholars: Criteria for Inclusion

February 24, 2017 | By | No Comments

As I’ve worked on building my corpus of scholars for the Directory of Oneota Scholars, I’ve realized that I need more than just one page to house information on scholars. I will create a drop down menu with four page options: Academics/Professionals, Graduate Students, Emeritus, and Deceased. The Academics/Professionals page will have individual scholars employed in university settings and those working for CRM firms and in museums. The Graduate Students page will have graduate students currently pursuing Master’s degrees and PhDs. The ‘Emeritus’ page will include individuals who were once employed in an academic setting but have since retired and the ‘Deceased’ page will include individuals who are deceased, but their work remains important in Oneota archaeology.

Read More

Erin Pevan

By

February 24, 2017

An organized chaos of Ngrams, corpora, and theory

February 24, 2017 | By | No Comments

At this point in my project exploring Norwegian national identity in literature over time, there is not much to report other than my continued progress knee-deep into the different pieces of my project. Over the past several weeks, I have been delving into different visualization tools to illustrate trends in national identity in Norway over time, and Ngram viewers (such as Google Ngram Viewer and Culturomics Bookworm, as well as a new fun Ngram discovery from the Norwegian Nasjonalbibliotekets Språkbanken repository) are the tools I am currently testing as my visualization for these trends.
Read More

nelso663

By

February 18, 2017

Querying the Collection of the British Museum for Propositional Objects

February 18, 2017 | By | No Comments

As I mentioned last month, one of the ideas of the semantic web is to render data from specialized, disparate sources comparable, and this is achieved by developing specifications like CIDOC-CRM. One implementation of CIDOC-CRM is the Erlangen CRM. Heritage institutions like the British Museum use implementations like this to organize their collection. It is implemented in the Web Ontology Language (OWL) and can be browsed in an ontology explorer like Protégé or by just reading the XML.

The CIDOC-CRM includes a class called Conceptual Object. Conceptual Object is a subclass of Man-Made Thing and a superclass of both Propositional Object and Symbolic Object. I’m particularly interested in exploring the Propositional Object class, which includes

“immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or imaginary things and that are documented as single units or serve as topic of discourse” (CIDOC-CRM, n.d.).

According to the documentation, a set of exemplary instances of this class are the common plot points of Kurosawa’s The Seven Samurai and Sturges’ The Magnificent Seven. A query to a SPARQL endpoint in order to materialize that collection’s Propositional Objects might read as follows:

# declare a prefix
# this allows us to refer to objects in the schema directly rather than by their full URI
# e.g., in the query below, crm:E89_Propositional_Object rather than the full URI http://erlangen-crm.org/current/E89_Propositional_Object
PREFIX crm: <http://erlangen-crm.org/current/>

# specify:
# a) the variable that the server should return (?instance)
# b) that the server should return unique instances only (with the DISTINCT modifier)
SELECT DISTINCT ?instance
# specify the pattern for the server to try to match
WHERE { 
 ?instance a crm:E89_Propositional_Object 
}
# state how the response should be ordered…
ORDER BY ?instance
# and the quantity of instances to limit the response to
LIMIT 100

Applying this query to the British Museum’s SPARQL endpoint returns 100 instances of Propositional Object, including Afghan Studies, Annual Reports, and Annual Review of the Royal Inscriptions of Mesopotamia Project.

Find the British Museum’s SPARQL endpoint and some helpful examples here.