OCW Publication Standards Training: Part 1

1
OCW Publication Standards TrainingPart 1

• 11/5/04

2
Agenda for Part 1

• Basics of OCW standards
• What are they?
• Why do we have them?
• Recap of F04 cycle
• OCW Intranet
• Administrative Information
• Presentations Meetings
• Content Preparation
• Intellectual Property
• Authoring
• Course Editing QA
• Evaluation
• Standards questions to resolve next session

3
Basics of OCW Standards

• Basics of OCW standards
• What are they?
• Why do we have them?
• 80-20 Rule

4
Recap of F04 Cycle Common Issues
5
Recap of F04 Cycle Common Issues

• Reinforce existing standards
• CHP images (alt-text, file size, dimensions,
  naming)
• Table column headings
• Citations (format when to list textbooks)
• Formatting in tables
• When to use a table
• Spacing in tables (to be continued in CMS
  training)
• Solve ongoing problems
• Spacing around tables (to be continued in CMS
  training)

6
OCW Intranet

• OCW Intranet
• Administrative Information
• Presentations Meetings
• Content Preparation
• Intellectual Property
• Authoring (CMS Training in Jan 05)
• Course Editing QA
• Evaluation

7
Summary of Key Updates

• Content capture - new section
• Course QA section separated and called Course
  Editing QA
• Images in sections (non-image gallery scenarios)
• Added home page image research downloadable
  content links
• CMS Course copy (to be covered in CMS training)
• Admin Mailing lists updated

8
Next Time Part 2 Agenda

• In-depth issues
• Writing highlights
• Image replacement process
• Video edits
• Line spacing (tables, text, subheads,
  sub-subheads)
• FQA for S05 cycle
• Publication process (after submission for
  publication)
• New author submission _at_ staging Initial QA
• QA Checklist

9
OCW Publication Standards TrainingPart 2

• 11/9/04

10
Agenda for Part 2

• In-depth issues
• Writing highlights
• Video edits
• Line spacing (tables, text, subheads,
  sub-subheads)
• FQA for S05 cycle
• Publication process (after submission for
  publication)
• New author submission _at_ staging Initial QA
• QA Checklist

11
In-depth issues writing highlights

• The primary purpose is to feature and get users
  to key types of content on the course site (e.g.,
  an interactive simulation, videos, assignments
  w/solutions).
• It is also an opportunity to "market" your course
  to users (e.g., the faculty member wrote the text
  used in the course, the faculty member is a Nobel
  Prize winner).
• It is not intended to include descriptive
  information about the course itself.
• Must include at least one link to a section
  within the course, but not more than 3 links.
• If the course contains the following
• lecture notes
• video and/or audio
• simulations and/or demos
• 100 complete downloadable content in a section
  (i.e., all readings, essay assignments and
  student examples of each one)
• questions and solutions (for assignments, exams,
  recitations, labs)
• image gallery
• online textbook
• then you must feature such sections - these types
  of sections are of great interest to our users.

12
In-depth issues writing highlights

• Examples
• This course features a complete set of
  downloadable problem sets and solutions in the
  assignments section. In addition, the final exam
  is available.
• This course features lecture notes and videos for
  all sessions.
• This course features a complete set of lecture
  notes. In addition an extensive bibliography of
  assigned and recommended readings is provided.
• This course features lecture notes for a number
  of sessions and videos for all sessions in the
  lecture notes section.
• This course features homework assignments with
  solutions. Extensive project information,
  including student submissions, are also provided
  in the projects section.
• This course features an online textbook in the
  readings section . The text was written by Prof.
  Smith, recipient of the 2001 Nobel Prize in
  physics.
• See Content Preparation Section Standards CHP
  section on Intranet

13
In-depth issues writing highlights

• Before
• Highlights of this Course
• Product Design and Development is a project-based
  course that challenges students to design a new
  product and to produce a prototype version of it.
  This site includes many resources from the class,
  including lecture notes, project
  examples and project guidelines. The course
  textbook, Product Design and Development, was
  co-written by Prof. Steven Eppinger
  (see http//www.ulrich-eppinger.net/ for more
  information).
• Course Description
• Covers modern tools and methods for product
  design and development. The cornerstone is a
  project in which teams of management,
  engineering, and industrial design students
  conceive, design, and prototype a physical
  product. Class sessions are conducted in workshop
  mode and employ cases and hands-on exercises to
  reinforce the key ideas. Topics include
  identifying customer needs, concept generation,
  product architecture, industrial design, and
  design-for-manufacturing.
• gtgtView this course en Español or em Portugues
  courtesy of Universia.

After Highlights of this Course This course
features features selected lecture notes. In
addition to student work, project guidelines are
available in the projects section. The course
textbook, Product Design and Development, was
co-written by Prof. Steven Eppinger (see Prof.
Eppingers Web site for more information).
Course Description Product Design and
Development is a project-based course
that challenges students to design a new product
and to produce a prototype version of it. It
covers modern tools and methods for product
design and development. The cornerstone is a
project in which teams of management,
engineering, and industrial design students
conceive, design, and prototype a physical
product. Class sessions are conducted in workshop
mode and employ cases and hands-on exercises to
reinforce the key ideas. Topics include
identifying customer needs, concept generation,
product architecture, industrial design, and
design-for-manufacturing. gtgtView this course en
Español or em Portugues courtesy of Universia.
14
In-depth issues video edits

• Types of edits
• Breaking into chunks (done by encoding team -
  Andrew)
• Not as costly
• Good for breaking up student presentations or
  other modular content
• Knock off beginning or end of a session
  (housekeeping info)
• Content edits (done by video production team -
  Craig)
• IP edits, other faculty driven edits
• Cut out small snipits of video (IP other edits)
• Fade to black screen - replacement text (IP)
• Whats possible?
• Full sets of lecture videos 10 edits/session max
• Selected lectures 0-5 edits are optimal
• How to submit
• Spreadsheet detailing time start stop, tactic
  details (see next slide for example)

15
In-depth issues video edits
Sample video edit submission spreadsheet
16
Line spacing in CMS

• Various components created within eWEP 4.5 or
  so
• View at http//ocw2.mit.edu/OcwWeb/Architecture/4-
  999GKSJanuary--IAP--2005/CourseHome/index.htm
• Spacing scenarios
• Subhead-BodyCopy-Table
• BodyCopy-Table
• Instructional Text-Table
• Subhead-Table
• Table-BodyCopy
• Table-Subhead-BodyCopy
• SubSubhead-Table
• Table-SubSubhead
• Table-Subhead-Table
• Table-BodyCopy-Table
• How to implement/check code to be covered in CMS
  training - but info is posted on Intranet

17
Post-ready for production

• Publication process gt3wks before cycle deadline
• Courses ready for FQA/re-publishing to be
  submitted by 5pm Tuesday
• course status should be Ready for Production
• staging engine runs every 20 mins. If something
  is stuck, email ocw-prod-request_at_mit.edu.
• Best practice enter any special notes into CMS
  course comments
• Email ocw-prod-request_at_mit.edu
• best practice Subject ltcoursegt ready for
  production
• SM emails FQA comments to micro-teams by 1pm on
  Thursday
• comments placed in CMS course comments (CMS
  comments as you use Course Log in FM)
• course must go through Steps 1-2 again until
  approved in FQA
• SM approves courses for publication by 5pm
  Thursday (Scheduled for Publication)
• Publication engine runs Friday morning MIT Time
• India team sends email to ocw-prod_at_mit.edu when
  Publication run courses are viewable at
  aka-ocw.mit.edu
• Best practice (indicating how many courses and
  global pages published (and any issues)
• Prod Team GKS runs "Akamai Purge"
• This tells the Akamai server to re-check our
  origin machine for updates to send them out to
  the world. The purge typically takes an hour
  depending upon size of update
• Once purge is complete all pages available on
  ocw.mit.edu
• users might need to do a Shift-Reload within the
  browser to bring up new content
• Prod Team sends email to ocw-pub_at_mit.edu to
  announce publication of list of courses

18
Post-ready for production

• Publication process lt3wks before cycle deadline
• Courses ready for FQA/re-publishing to be
  submitted by 5pm daily
• course status should be Ready for Production
• staging engine runs every 20 mins. If something
  is stuck, email ocw-prod-request_at_mit.edu.
• Best practice enter any special notes into CMS
  course comments
• Email ocw-prod-request_at_mit.edu
• best practice Subject ltcoursegt ready for
  production
• SM sends FQA comments to micro-teams by 5pm the
  following day
• comments placed in CMS course comments (CMS
  comments as you use Course Log in FM)
• course must go through Steps 1-2 again until
  approved in FQA
• SM approves courses for publication by 5pm
  daily (Scheduled for Publication)
• Publication engine runs every morning MIT Time
• India team sends email to ocw-prod_at_mit.edu when
  Publication run courses are viewable at
  aka-ocw.mit.edu
• Best practice (indicating how many courses and
  global pages published (and any issues)
• Prod Team GKS runs "Akamai Purge"
• This tells the Akamai server to re-check our
  origin machine for updates to send them out to
  the world. The purge typically takes an hour
  depending upon size of update
• Once purge is complete all pages available on
  ocw.mit.edu
• users might need to do a Shift-Reload within the
  browser to bring up new content
• Prod Team sends email to ocw-pub_at_mit.edu to
  announce publication of list of courses

19
Post-ready for production re-publishing

• If you edit a course after it has been published
  then
• Send email to ocw-prod-request_at_mit.edu to let SM
  know you are submitting a course for
  re-publication
• Best practice Subject ltcoursegt ready for
  repub
• SM approves course for publication by 5pm
  Thursday (changes status to Scheduled for
  Production)
• Course is published Friday morning and included
  in list of published courses email to
  ocw-pub_at_mit.edu

20
Author submission _at_ staging Initial QA

• Courses arrive by submission deadlines
• courses arrive Published in Staging
• Spec should note if course is to be submitted at
  Ready for QA
• SM scans all submitted courses (1st time) emails
  micro-teams India (as needed) w/any concerns or
  comments by 5pm 2 days after submission
• comments also placed in CMS course comments
• use CMS course comments as you use Course Log in
  FM
• Micro-teams continue regular process of review
  and submission of courses
• If you know/suspect a course has issues between
  initial scan and Ready for Production send a note
  to ocw-prod-request_at_mit.edu

21
QA checklist

• Updated QA checklist on Intranet
• Split India/Production, FL/DL Final QA lists
• Made FL/DL list slightly shorter and changed a
  few items to spot checking
• SM will use FL/DL QA list to review courses when
  sites are submitted by India/Production in
  staging