The CourtYard

a space for writing, reading, and thinking in the first year at GSU

user nameplate
 pic
 blurb
public documents
 note introducing each piece in the collection, public or private
  course number (1101 - 1102)
  assignment description -- cut/paste or paraphrase
  number of pages
  draft / revision / final
  number of versions
  time spent
  reflection on strengths and weaknesses, notes for next time

doc goes in with date, place for prof comments, student comments, rubric scores

 works in progress -- protected, email list allows access

 semi public -- gsu ip addresses only

 public works -- world can see

surveys of writing practices and attitudes

1101 argumentative paper with prof comments

1102 revision of paper with comments by student

rubrics as dropdowns and then a sliding scale allowing prof to assert committment to level of accuracy of rubric for given assignment. (?)

Just the first few steps toward creating a gradebook. The file is as php/grades.htm. I guess for this to truely be useful it would need to be iterative, so there would be one form for each assignment and the total from each would be added to the subsequent forms until 100 per cent was reached. If user added another assignment, the form would recalculate the per cent of final grades.

Things to Do

• fix print css
• change setup and student setup so multiple signups aren't possible
• redo setup to break out by college and dept (change tables--user, courses-- too)
• change wow/index.php so that it displays courses by college/dept/prof in a table.
• change form_view so it can show more than one entry on a day, startup button doesn't show after due date, it says assessement average instead of grade
• admin grade should show break down of rubrics not just average#, should say "assess it" not "grade it", replace js popupscript with avg:3, development:4, argument:2, etc. , and zebra stripe alternating assignments under each student, with green or red box to indicate whether that assignment was done or not done
• admin_assignment_grader it says Grade: where it should save Average:
• connect create new assignment with uploaded files somehow
• professor's archive view?
• see thread of paper development. Maybe by viewing reviews
• administrator's archive view--average of averages, examples of 5s by rubric
• some way to know if rubrics are working , review of reviews
• software feedback mechanism for prof's and students

Things to add:

• forms should maintain state or be "sticky"
• place on admin_assignment form where prof can offer peer review instructions that would then appear for the student on the review section
• prof's email address somewhere on student page after login
• threaded discussion after assignment on form_view page
• grade generated by rubric--which prof can override
• archive--auto capture examples that get 5s across the board
• offer prof option to save a copy of a student paper for demo in another class
• offer option to reuse an assignment another time
• something about plagiarism on the two help pages
• delete student, view, edit student info

I've been working on a kind of cms / peer review tool (link) that I think would integrate nicely into the existing WAC setup, and ultimately some combination of the two would be easier to use than the current setup and more effective. See also. The necessary parts would be

• one login screen, differentiating prof and wc from students based on email and password only.
• The prof and wc would go to an admin screen where she can make assignments, make groups, grade assignments.
• students would go to a display page that would have a table with what is due and when. Student can select an assignment and work on it until it is due, and flag it whenever for peer review, indicating level of completion also.
• When the prof wants to grade, she simply grades as with WAC setup now.
• users (prof, wc, students) assignments, assessments, rubrics (?), someway to differentiate class, section, and semester so prof can use it more than once and more than one at a time.
• We can keep the clipboard, though I don't think it is used.
  • Get rid of the vault peer review thing.
  • keep the style thing?

When a prof fills out the WAC faculty form, it will enter prof. in profs db. The prof will then be able to choose who her WC will be (based on a drop down populated from the db that the WCs fill out) and if the WC will grade, apply a rubric, or just offer peer review. This decision will be alterable later.

About the DB:

One db with multiple tables

1. profs--prof_id, email, pword, class, section, semester
2. wc--wc_id, email, pword, role (universal peer, grader)
3. students--st_id, peer group,  
4. assignments, as_id, as_id_desc, as_id_due, as_id_val, as_id_rubric, st_id_as_id_grade
5. assessments, prof_id, wc_id, st_id, as_id, st_id_as_id_grade, rubric # 
6. rubrics

Files already existing

• WAC
  assignment view, make, edit, grade
• Commons
  peer groups, view, peer rubric, login,
  • will need admin view, including peer group setup, grade, wc role
  • will need wc view, based on prof's decision about wc role

I'm losing track of software I've written and so plan to keep a running log here.

• paragraph scramble
• word count (frequencies, Fogg etc.)
• scheduler
• tree (not my own)
• authent session (needs password.php)
• style checker
• todo
• peer review