Phase 2 planning

OERca - Phase 2 Planning
 * Previous Phase 2 planning can be found at Phase 2 plan-old.

Enabling Technologies

       OER Phase II Tool Development Specs

 

OER Phase II will be enhancements &amp; additional function added to the existing tool found at. Phase 2 must be complete and tested before the UMMS dScribes begin June 8. Here is an attempt to gather all the specs provided by the Pieter &amp; Garin that (hopefully!) will lead to coding.

The full set of Mock-Ups for Phase 2:


 * [[Media:PhaseII-mockups_graffle.pdf|May 8, 2008 (PDF, 1mb)]]

I. Setting up the dScribe process: Instructor contacts Admin
 Priority: Low - Given the number of dscribes, dscribe2's, and instructors will be small for the June deployment - we will continue to "manually" perform this tasks using phpMyAdmin.

A. Accounts Setup and Permissions - Tool

 * 1) Admin adds a new course to the tool
 * 2) Admin assigns an Instructor to the course * (added to dB schema) - Pieter 10:07, 29 April 2008 (EDT)
 * 3) Admin assigns a dScribe to the course
 * 4) Admin assigns dScribe2 to a dScribe * (added to dB schema) - Pieter 10:07, 29 April 2008 (EDT)
 * 5) Admin adds Instructor login to the database
 * 6) Admin adds dScribe login to database (the dScribe 2 login may already exist)
 * 7) Admin/dScribe/dScribe 2 submits permission form from the Instructor – Scanned form or electric form within the tool

These functions require some new data fields (Instructor, dscribe2) to be added to the database schema.

B. Course Setup – Tool
1.   DONE! dScribe/dScribe 2/Instructor edits course and Instructor information

A. Ingesting Materials – Tool
High dScribe/dScribe 2/Instructor adds materials through a single or bulk upload (through ctools / desktop import) (materials need version / timestamp to distinguish between updated (Instructor or dScribe) materials) (need categories for materials (resources, assignments, lectures, etc)) * this is still critical, but the CTools component is low priority - Pieter 10:34, 29 April 2008 (EDT) *[MOCK-UP]* 2/Instructor edits material information
 * 1) Priority:
 * 1) DONE! dScribe/dScribe

B. Capturing Content – Tool/Desktop
High dScribe/dScribe 2/Instructor downloads the source materials from the tool – given the option doing a single CO download or bulk download of all associated CO with the course. The course material can include multiple embedded CO's. *[MOCK-UP]* png) using “Save as” or “Export” feature in PPT / Keynote, creating one unique image for each slide.(this is currently being done using a manual process - Glenn is making good progress on the Snapper tool)  2/Instructor captures content objects from materials (this is currently being done using a manual process - Glenn is making good progress on the Snapper tool) Step: <span style="color: rgb(153, 153, 153); font-style: italic;">dScribe/dScribe 2/Instructor assign metadata to objects using XMP (optional, but not default)
 * 1) <span style="font-weight: bold; color: rgb(255, 0, 0);">Priority:
 * 1) <span style="font-weight: bold; color: rgb(255, 0, 0);"><span style="color: rgb(0, 0, 0);">Priority: Low  <span style="font-style: italic; color: rgb(153, 153, 153);">dScribe/dScribe 2/Instructor converts slides to images (jpg, gif,
 * 1) <span style="font-weight: bold; color: rgb(255, 0, 0);"><span style="color: rgb(0, 0, 0);">Priority: Low  <span style="font-style: italic; color: rgb(153, 153, 153);">dScribe/dScribe
 * 1) <span style="font-weight: bold; color: rgb(255, 0, 0);"><span style="color: rgb(0, 0, 0);">Priority: Low  <span style="font-weight: bold; font-style: italic; color: rgb(153, 153, 153);">Optional

C. Ingesting Content Objects – Tool
2/Instructor uploads slide images and COs to tool in .zip file 2/Instructor adds metadata to the objects 2 chooses to send CO to the Instructor High dScribe/dScribe 2 sees standardized questions for provenance ASK form and adds any personalized questions about provenance – sent to dScribe – Instructor ASK form High dScribe chooses to send CO to the dSCribe2 with general questions, fair use, permission, or commission recommendations – sent to dScribe – dScribe 2 ASK form *[MOCK-UP]* chooses to escalate CO to Legal &amp; Policy Review Team for the purposes of general IP/policy CO escalation or fair use escalation standardized questions for general IP/policy or fair use ASK form and adds personalized questions / comments about CO – sent to Legal &amp; Policy ASK form 2/Instructor uploads replacement COs (RCOs) from desktop to tool 2/Instructor assigns metadata to the RCOs 2 chooses to send RCO to the Instructor High dScribe/dScribe 2 sees standardized questions for replacement ASK form and adds any personalized questions about the replacement – sent to dScribe – Instructor ASK form. This is similar to II.C.2.b *[MOCK-UP]*
 * 1) <big style="font-weight: bold; color: rgb(255, 0, 0);">DONE! <span style="background-color: rgb(255, 255, 0);">dScribe/dScribe
 * 1) <big style="font-weight: bold; color: rgb(255, 0, 0);"> <big style="font-weight: bold; color: rgb(255, 0, 0);">DONE! <span style="background-color: rgb(255, 255, 255);"><span style="background-color: rgb(255, 255, 0);">dScribe/dScribe
 * 1) <big style="font-weight: bold; color: rgb(255, 0, 0);">DONE! <span style="background-color: rgb(255, 255, 0);">dScribe/dScribe
 * 1) <span style="font-weight: bold; color: rgb(255, 0, 0);">Priority:
 * 1) <span style="font-weight: bold; color: rgb(255, 0, 0);">Priority:
 * 1) <span style="font-weight: bold; color: rgb(255, 0, 0);"><span style="color: rgb(0, 0, 0);">Priority: Low  <span style="color: rgb(153, 153, 153); font-style: italic;">dScribe 2
 * 1) <span style="font-weight: bold; color: rgb(255, 0, 0);"><span style="color: rgb(0, 0, 0);">Priority: Low  <span style="color: rgb(153, 153, 153); font-style: italic;">dScribe 2 sees
 * 1) <big style="font-weight: bold; color: rgb(255, 0, 0);">DONE! <span style="background-color: rgb(255, 255, 0);">dScribe/dScribe
 * 1) <big style="font-weight: bold; color: rgb(255, 0, 0);">DONE! <span style="background-color: rgb(255, 255, 0);">dScribe/dScribe
 * 1) <big style="font-weight: bold; color: rgb(255, 0, 0);">DONE! <span style="background-color: rgb(255, 255, 0);">dScribe/dScribe
 * 1) <span style="font-weight: bold; color: rgb(255, 0, 0);">Priority:

D. Editing Materials – Tool/Desktop
is this different from II.B.1 download? ) - this is exactly the same as II.B.1 - Pieter 10:56, 29 April 2008 (EDT) *[MOCK-UP]* High dScribe/dScribe 2/Instructor downloads single or bulk RCO s to desktop from tool *[MOCK-UP]* annotations, removed COs, inserted RCO <span style="font-style: italic; background-color: rgb(102, 255, 153);">(I crossed this off my list, is that correct?)   - this is something that is already accomplished manually (off your list) - Pieter 10:56, 29 April 2008 (EDT)
 * 1) Unless done previously, dScribe/dScribe 2/Instructor downloads the source materials from the tool – single or bulk download (<span style="font-style: italic; background-color: rgb(102, 255, 153);">How
 * 1) <span style="font-weight: bold; color: rgb(255, 0, 0);">Priority:
 * 1) <big style="font-weight: bold; color: rgb(255, 0, 0);">DONE! <span style="background-color: rgb(255, 255, 0);">dScribe/dScribe 2/Instructor updates materials with edits,

E. Ingesting Updated Materials - Tool

 * 1) dScribe/dScribe 2/Instructor uploads updated materials to tool
 * 2) dScribe/dScribe 2/Instructor edits updated materials information

<span style="font-style: italic; background-color: rgb(102, 255, 153);">This is based on filenaming (filename.v2) convention, right? '''* Ali, David, and I were discussing how to do this well and we tabled the discussion for the moment because it was holding up our progress on the dB schema changes - we should revisit this week to make a conclusive decision. -''' Pieter 10:56, 29 April 2008 (EDT)

III. Interactions Between Users Around Content Objects
=== A. dScribe → Instructor (<span style="font-style: italic; font-weight: normal; background-color: rgb(102, 255, 153);">dscribe can view the ASK form but cannot edit the ASK form )  ===

High dScribe/dScribe 2 views ASK form(s) to see all questions sent to Instructor  ( non editable, view only ) should this email be sent? Once a day? cron job? '''* It seems that we would have a lot of annoyed faculty on our hands if we were to email them each day and they had no way to turn off the emails easily. I think that the dScribes should, for the moment, be sure to email the instructor pointing them to a URL where they can input responses. - '''Pieter 11:11, 29 April 2008 (EDT)
 * 1) <span style="font-weight: bold; color: rgb(255, 0, 0);">Priority:
 * 1) what if there are multiple instructors? is there a "primary" instructor?   (see III.B.1 ) * multiple instructors should be able to access the form and respond. The response given should be tagged with the user's name so the dScribe/dScribe 2 can see who is making the response. - Pieter 11:11, 29 April 2008 (EDT)
 * 2) will there be any questions on ASK from not related to a CO? * No, all ASK form questions are about COs. - Pieter 11:11, 29 April 2008 (EDT)
 * 3) Tool sends email notification to Instructor (uniqname) notifying the instructor that there are COs in the ASK form awaiting instructor response
 * 4) <span style="background-color: rgb(102, 255, 153);">how often
 * 1) smtp mail needs to permitted for oer.umms.med.umich.edu machine

B. Instructor → dScribe
views ASK form to see all questions from dScribe/dScribe 2 reviews both provenance and replacement objects, responds to questions or saves COs for a later response should this email be sent? Once a day? cron job? '''* I don't mind pestering dScribes/dScribe 2s once a day. - '''Pieter 11:11, 29 April 2008 (EDT)
 * 1) <big style="font-weight: bold; color: rgb(255, 0, 0);">DONE! <span style="background-color: rgb(255, 255, 51);">Instructor
 * 1) <big style="font-weight: bold; color: rgb(255, 0, 0);">DONE! <span style="background-color: rgb(255, 255, 51);">Instructor
 * 1) Tool sends notification to dScribe/dScribe 2 about materials having been updated by Instructor (see III.A.2 )
 * 2) <span style="background-color: rgb(102, 255, 153);">how often
 * 1) smtp mail needs to permitted for oer.umms.med.umich.edu machine

C. dScribe → dScribe 2
High dScribe/dScribe 2 views ASK form to see all questions for dScribe 2 ( non editable, view only ) should this email be sent? Once a day? cron job? '''* I don't mind pestering dScribes/dScribe 2s once a day. - '''Pieter 11:11, 29 April 2008 (EDT)
 * 1) <span style="font-weight: bold; color: rgb(255, 0, 0);">Priority:
 * 1) Tool sends email notification to dScribe 2 notifying that there are COs in the ASK form awaiting dScribe 2 response (see III.A.2 )
 * 2) <span style="background-color: rgb(102, 255, 153);">how often
 * 1) smtp mail needs to permitted for oer.umms.med.umich.edu machine

D. dScribe2 → dScribe
High dScribe 2 views ASK form and reviews COs within form *[MOCK-UP]* High dScribe 2 responds to questions, tables COs for a short time, sends out permission forms, or escalates CO to Legal &amp; Policy Review Team *[MOCK-UP]*
 * 1) <span style="font-weight: bold; color: rgb(255, 0, 0);">Priority:
 * 1) <span style="font-weight: bold; color: rgb(255, 0, 0);">Priority:
 * 1) Tool sends email to dScribe notifying him/her of ASK form COs with responses and recommended actions by dScribe2

should this email be sent? Once a day? cron job? '''* I don't mind pestering dScribes/dScribe 2s once a day. - '''Pieter 11:14, 29 April 2008 (EDT)
 * 1) <span style="background-color: rgb(102, 255, 153);">how often
 * 1) smtp mail needs to permitted for oer.umms.med.umich.edu machine

E. dScribe 2 → Legal &amp; Policy Review Team (Priority: Low)

 * 1) dScribe views Legal &amp; Policy ASK form to see all questions/comments for Legal &amp; Policy Review Team (not editable, view only)
 * 2) Tool sends email to Legal &amp; Policy Review Team notifying them of pending COs awaiting input

F. Legal &amp; Policy Review Team → dScribe2/dScribe (Priority: Low)

 * 1) Each individual Legal &amp; Policy Review Team member views ASK form and reviews COs
 * 2) Each individual Legal &amp; Policy Review Team member adds comment / question to the ASK form
 * 3) Optional – email notification of new comments/questions by Legal &amp; Policy Review Team sent to dScribe 2
 * 4) After the Legal &amp; Policy Review Team meets, a final decision with rationale is added to the ASK form by a designated member of the team
 * 5) Tool sends email to dScribe 2 and dScribe about the final decision