Difference between revisions of "Best Practices"

From Kumu Wiki - TRU
Jump to navigation Jump to search
Line 2: Line 2:
 
[for checklists: expand each item in the list to link to subpage]
 
[for checklists: expand each item in the list to link to subpage]
 
===Conduct a Pre-Edit===
 
===Conduct a Pre-Edit===
Confirm with Brian (editing co-ordinator) the following:
+
Before starting to edit a course, confirm with Editing Coordinator (Brian):
* Issue (course) has been entered in JIRA[link] and assigned
+
* Issue (course) has been entered in JIRA[link] and assigned to you
Discuss and verify with the instructional designer, course lead, subject matter expert (SME), or course writer the following:
+
Discuss and verify with the instructional designer, course lead, subject matter expert (SME), or course writer:
 
* Scope of edit: this may change as editing proceeds and may differ from information captured in JIRA
 
* Scope of edit: this may change as editing proceeds and may differ from information captured in JIRA
 
* How to handle URLs: for example, as weblinks with author/originator stated, title of resource in bold font, URL provided, instructions to Production
 
* How to handle URLs: for example, as weblinks with author/originator stated, title of resource in bold font, URL provided, instructions to Production

Revision as of 15:40, 16 January 2014

Best Practices for Editing TRU-OL Curriculum Materials

[for checklists: expand each item in the list to link to subpage]

Conduct a Pre-Edit

Before starting to edit a course, confirm with Editing Coordinator (Brian):

  • Issue (course) has been entered in JIRA[link] and assigned to you

Discuss and verify with the instructional designer, course lead, subject matter expert (SME), or course writer:

  • Scope of edit: this may change as editing proceeds and may differ from information captured in JIRA
  • How to handle URLs: for example, as weblinks with author/originator stated, title of resource in bold font, URL provided, instructions to Production
  • How to handle lists of resources
  • Whether to provide a resources page
  • Layout in the web (for example, if the Course Schedule will have a separate page or be included in the Course Guide)
  • What citation style is to be used

Verify with the curriculum assistant the following:

  • Details of the textbook(s) (name, author, edition); companion website; and other resources
  • Editor's access to the resources

Set up a style sheet:

  • Either set up a new style sheet or get one from the previous editor
  • Log in to Blackboard Learn[link] and note in the style sheet choices already made for the course

Set up the folders and files:

  • Save all original files renamed according to File Naming Conventions[link]

Back up all materials on the O: drive:

  • Use a folder under O: Open Learning Share> Curriculum Services> editing [check] and back these up each day

During Edit [this heading will change]

Use JIRA

  1. Log work. If there are two MODs (methods of delivery), log work under each one.
  2. Enter comments for top-level information (from which an editing memo can be made) on the main page.
  3. Enter comments for granular information under the log work page.
  4. Estimate percentage of work done.

Use the Style Sheet

  • Use and add to the Style Sheet

Send Documentation

  • Email edited Course Guide to the appropriate CA

Use Generic [use other word?] Email Addresses

Some OL teams do work on campus or work with several other teams so they might have generic sites. Rather than email a particular person in the Intellectual Property Office (IPO), for example, we use the IPO's generic email address. Generic email addresses:

 * Copyright: Copyright@tru.ca[link]
 * CA Business: CA1@tru.ca[link]
 * CA Arts: CA2@tru.ca[link]
 * CA Health: CA3@tru.ca[link]
 * Media Services : media@tru.ca [verify][link]
 * Default Course Lead (Naomi) and Project Manager (Andrea C): CurriculumServices@tru.ca[link]