Class2010Apr09

Class Assignments and Agenda for Week 13, 2010 Apr 9
Class meets from 9:10 - 11:55A in 3214 Jordan Hall Addition


 * The major objectives for this session are to ...**
 * Pull together metadata, templates, technical notes


 * Things to do before class**
 * Keep working on indicators


 * Agenda**
 * Where are we?


 * Decision about final formats - see TriangleEnvironment for my (Hess) proposal
 * Against print
 * TLC does not currently have resources for a big print distribution - will have to seek grant
 * TLC will likely want to reformat the information from whatever we do anyway
 * Print formatting is too complicated - we just don't have the time to mess with it
 * Too many versions - need a word version, a pdf, separate files for the images, etc
 * For online
 * On-line version is easier to modify and creates a model for community participation
 * Only one version - the official on-line text and images
 * Can upload all of the actual data we used for anyone to examine - ultimate in transparency and "peer" review
 * Allows community to review, comment, seek corrections, add new items
 * Against online
 * Not as pretty - crude tables, limited placement possibilities for graphics
 * Discuss content, format and tone for a "further research and analysis" section for each benefit (Aimee) <>
 * Overlapping content issues--ecosystem valuation?--(ACampbell)


 * Status of external reviews - how shall we proceed?
 * Hess' proposal:
 * Work on simplified versions in Word, mimicking wiki setup (separate file for each indicator) and send to Hess as they are completed during the week of 12 April - Hess will do some editing and return to you. Template Example
 * Send out to external reviewers by Fri 16 April, with return date request of 28 April
 * Review comments on 30 April and spend time until final (7 May) making edits
 * Put completed items on TriangleEnvironment wiki between 30 April and 7 May - Hess will keep site clean, take care of formatting messes, organize, etc


 * Team work time <>


 * Peer evaluation - we were supposed to do after break, but we haven't met - how should we handle? - [|PeerEvaluation.doc]
 * Recall this is part of how your grade is determined, along with the self evaluation - [|SelfAssessment.doc]
 * Update milestones/calendar in light of changes to external review schedule


 * Notes: (by Hess)

Decided to go with wiki approach - Hess will do tutorial next week - apologies for another reformat (but it's not hard to go from the simplified Word docs to the wiki, and I will do as much of the dirty work as I can)

Limitations becomes "Limitations and Further Research" and is associated with each indicator. More general limitations (ie, indicators we'd like to have but can't find data for) should be handled either in the introduction for each section OR creating a "dummy" indicator page that describes what it this?, why is this important?, and then a section "Why this measure can't be reported?" that explains that it cannot be reported because there are no data (or whatever the reason).

External Review Decision - Hess proposal rejected and replaced with this ... ** Peer evaluation
 * Copies to Hess ASAP - if he has anything to say, it will be by midnight Sunday 11 April
 * Out for external review on Mon 12 April
 * Ask for response ASAP but no later than 23 April
 * Review comments on 23 April and spend time until 30 Apr making edits, with edits possible until 7 May if needed
 * Put completed items on TriangleEnvironment wiki between 23 April and 7 May - Hess will keep site clean, take care of formatting messes, organize, etc
 * Team members will talk if there are any problems, but will not complete formal evaluation right now


 * Everyone will complete a team evaluation and self assessment by the end of the semester and will email to Hess. Peer comments will not be shared, because there are too few people on each team for there to be any kind of confidentiality. Deadline for submitting these will be announced by next class.

Final presentation
 * We decided to do a more active kind of presentation than we had originally considered, thanks to a great idea from Lauren.
 * Instead of a full-length PPT, which is made redundant by having everything on the web, we will do an overview to the full audience, and then have one of the large plasma screens set up for each of the four public values (big sign on top of each screen).
 * Audience will be able to move around to each and talk to the team, look at things, etc.
 * Jessica and I (Hess) were talking after class - we should also put out a bunch of the laptops scattered around the room so that people who want to poke around on their own can do so - we can bring them up and set to the TriangleEnvironment home page. People can look on their own and then also visit teams to ask questions.

Hess has updated milestones/calendar