Please note that this schedule is subject to change. (And open to pull requests.) Class progress through early materials, and the possibility of “guests” (via Skype and/or Twitter) may warrant a change in the schedule or assigned work.
fill out course survey
Read or watch the following. Tweet questions and discussions about the materials with the #corpusmusic hashtag. (Please see Readings and resources page for Twitter handles of authors.) Collaborate on Google Doc response to Gibbs/Cohen and Stommel.
Scales & Triads
Digital + Humanities = Digital Humanities? (Gibbs/Cohen, Stommel)
Creating a set of guidelines (a manifesto?) for computational musicology research
First, leave one or two comments or ideas in the collaborative methods document (must be signed in with CU Google account to view) based on the first two days’ readings.
Then, read or watch the following. Tweet questions and discussions about the materials. (Please see Readings and resources page for Twitter handles of authors.) Collaborate on Google Doc response to de Clercq/Temperley.
Review of scales and triads
Walk through pop/rock harmony resource
Harmonic schemata (blues, doo-wop, VI–IV-I-V, etc.)
de Clercq/Temperley, “A corpus analysis of rock harmony.”
Read the following. Tweet questions and discussions about the materials with the #corpusmusic hashtag. Collaborate on Google Doc response to Foucault and Meyer.
Introduction to pop/rock form and Variations Audio Timeliner
Discuss Meyer’s definition of style
Discuss Foucault & implications for computational musicology
Compare Meyer & Foucault, and critique de Clercq/Temperley in light of them
First, come up with some questions or comments you have for our discussion with Trevor de Clercq.
Discussion with Trevor de Clercq (via Skype)
Discussion with Chris White (via Skype)
Start thinking about collaborative project
Read the following pages of Chapters 4–5 of Ashley Burgoyne’s dissertation, “Stochastic processes and database-driven musicology”:
Tweet questions and discussions about the materials with the #corpusmusic hashtag. Collaborate on Google Doc response.
Then come up with some ideas for our collaborative group project based on this reading and our previous readings and discussions.
Collaborate on project planning
Add to the Collaboratve Project GDoc begun in class. Include new project ideas, or added details and practical implications for the ideas already present.
Finalize project plan
Align project tasks with course objectives
Begin assigning tasks and creating course assessment contracts
Setup individual GitHub accounts and membership in the corpusmusic organization.
Review our collaborative project document in Google Drive
Make a copy of one of the sample course contracts I put in our shared folder, fill in your own proposed details, and share with me by 8am.
Signup for a GitHub account, if you haven’t done so already, and send Kris your username (via Twitter is fine).
Intro to git/GitHub.
Decide on our first milestone and its requisite components.
Assign tasks to individuals and/or small work groups to begin the project.
Those new to GitHub can check out my article “Push, Pull, Fork: GitHub for Academics” which contains a video, and follow some of the links, as necessary.
No live meeting. Work in your groups with the goal of presenting some finished work and a status report on Friday. Be sure to post code and data to the corpusmusic group on GitHub. When working together online, use open channels like Twitter and GitHub, or coordinate using our Google Drive folder so that others in the class (and I) can follow and, where appropriate, join in.
Present status updates and finished work.
10:30 - discuss the music encoding conference with Dan Shanahan.
Plan the next stage of work.
Report on project progress, solicit feedback.
Report (near) final results of project work.
Plan final stage of written/web presentation of findings.
Update course contracts with the following:
Complete or fine-tune any remaining computational or analytical work.
Draft your write-up(s) for our publis website. Make them Google Docs, and share them in the “WRITEUPS” folder in our shared Google Drive folder.
Presentations of any new findings.
Peer-review of write-ups.
Complete any outstanding revisions of code or write-ups, and make sure everything has been pushed to GitHub or posted in Google Drive.
Update course contracts.
Final peer-review, uploading, and discussion of writings.
Final course contract updates.