Working Remotely

Process Change! 

Some editors may be working from home in the next few weeks. 

What? Why? 

The health authorities urge Canadians to practice social distancing, and we can do our work without being in close proximity to others in public spaces. 

man in blue hoodie using laptop computer

Photo by Dimitri Karastelev on Unsplash

What Does This Mean? 

We are still working! We will be doing daily check-ins with Dani C or Curriculum Services folks, and we’ll stay in touch with everyone about current projects.

Some editors will come in to the office as well. 

shallow focus photo of orange cat near laptop computer

Photo by Catherine Heath on Unsplash

How Can I Talk to an Editor?

Nothing could be easier!  If you don’t see us around the office, get in touch by email, Skype for Business, or WhatsApp.

And we might be on Mattermost (if we can figure-out how to sign-in). 

people sitting down near table with assorted laptop computers

Photo by Marvin Meyer on Unsplash

How Can I Learn More?

TRU’s web page on COVID-19 is being updated daily, and it is a great resource to check for the most recent information.


Editing Team Meeting 9/25/2019

Editing Team Meeting

Date | time 9/25/2019 11:00 AM| Location OL344

Meeting Notes:

Attendees: Dani, Mona, Justin, Cory

Regrets: Chris; Courtney

Note taker: Mona

  1. Editor’s website:
  • Log-in;
  • Review current content;
  • Collaborate;
  • Determine common objectives.
  1. Free online micro-course to master the basics of OER and Creative Commons:

Open Education, Copyright and Open Licensing in a Digital World (LiDA103)

  • Editors are welcome to attend;
  • Starts on October 7, 2019;
  • 2-week course, commit to 1–2 hours/day;
  • Negotiate with Naomi to use some work time;
  • Certificate earned upon completion;
  • Registration link:
  1. Maintenance Courses:
  • Change to file version for Rachelle’s IP review: Moving forward, she will *always* review the edited version.
  • Editors to flag new/deleted 3-rd party materials for her attention;
  • Dani will share the edited files with Rachelle upon completion of peer review process.
  1. “One-offs” (those maintenance projects that *should* involve only one component of a course):
  • Be sure to check all materials that could be affected by the corrections/changes made;
  • Discussion was around accountability and transparency of the very narrowed scope.
  1. Internal Review
  • Discussion postponed to next meeting;
  • Consider what common issues occur in the process;
  • Consider scope: skim vs. total re-edit.
  1. Style considerations for each course/discipline:
  • Justin suggested adding that information in D4P2 in the notes section;
  • Advantage to next editor: reduction of time spent determining which style was deemed appropriate.


Editing Team Meeting 9/11/2019

Call to order: 10:30am

In attendance: Courtney Charlton, Naomi Cloutier, Dani Collins (Chair), Justin Frudd, Mona Hall, Paul Martin, Cory Stumpf, Chris Ward (scribe & time keeper)

Dani: Welcome and new meeting format

  • Call for note taker and time keeper: Chris
  • Call for review of process changes this summer
    • Chris: brief review of process changes
    • Discussion:
       lack of CMP (what info needed? can it be shared in D4P?)
       determining, negotiating, and communicating editing scope
       identifying and confirming course materials
       exam processes
       ProctorU

Courtney: “Using a Tempest in a Teapot to Separate the Wheat from the Chaff” presentation on plain language with examples from HIST course

  • Learners’ needs not served by misused and obscure terms: e.g., obduracy, abrogation, temporal turmoil, venal, jeremiad, etc.
  • Long, complex sentence structure obscures meaning.
  • Random or inconsistent capitalization, and dated racial/cultural terminology requires more time for editors to query or resolve.
  • Discussion:
     How to minimize problematic language without changing voice of writer?
      How to balance student needs, writer wants, time constraints?

Paul: Introductions; enrollment growth up 15%; potential of non-linear development processes with editors contributing or collaborating earlier

Group: Appreciative enquiry

Dani: Open call for agenda items for future meetings

Tabled for future:

  • Editing websites
  • Credentials: when to include designations and certs

Adjourned: 11:45am

Back to the Future

Welcome to co-creators Dani (darwinsfrog), Cory (corythestumpf), and Mona (mohall2015)!

So, we moved back to this, our previous, wordpress site. We have ambitious plans to expand the site’s features in the future, but this will be the home of the OL Editors’ site for the next few weeks or months.

Workflow Emails to Production

New process!

Don’t include OL_Production on editing workflow emails. This refers to introductory emails (“I’ve begun editing…”) and the final emails (“files are in pre-production folder…”).

Keep writing notes for Production on the files, and summarize any concerns in your final email to Curriculum Services. CS will send the notes to Production after sign-off.

Outcomes before Materials

Heads up! I moved the Learning Outcomes section to appear before Course Materials in the Course Guide. Thanks for the feedback, Cory!

This will group together key Curricunet information, and it could save a bit of time by aligning with Production’s processes.

Style Sheets

Spring is here! Thank you for your patience while I play with this new colour feature in WordPress.

What Is a Style Sheet?

The most basic tool for editing, and one of the most practical, is a style sheet. Most of the time the editor creates this and shares it with others. A style sheet is a table or document used to track our decisions, so it is an essential tool for consistency in spelling and style.

More Work?

Normally editors track the decisions that are not covered by the house style or ones that conflict with the house style, perhaps due to a specific discipline’s style conventions or a writer’s preferences.

It is good to be thorough, but not so thorough that the style sheet becomes it’s own editing project.

But Why?

In addition to clarifying the spelling of tricky words, the style sheet reminds us of the types of changes we made in earlier parts of the document.

  • Did the writer use italics or bold for key terms?
  • Which heading level did we use in the table in Module 1?
  • Which terms did we capitalize?

All these choices are recorded in one place, so we don’t have to look them up each time. It makes editing easier since we don’t have to remember everything to be consistent throughout the document. It is also helpful as a reporting tool, since writers or course developers can quickly review the changes we’ve made without scanning through the entire document.

Format your document in whatever style works for you. I usually make it an online document (e.g., Google Docs) to share it with others, but many editors build a style sheet on paper or in a Word doc.



Editors’ Community of Practice

The editors’ team has started bi-weekly professional development seminars. We take turns facilitating the meetings, and we co-create the content to share our expertise and fill-in gaps in our knowledge. We have not chosen a way to reify or apply the new learning, but I’m sure a creative expression of our learning will present itself in time.

I’m currently taking a course that uses social learning theory and communities of practice, so I wanted to share some memorable quotes from Étienne Wenger that may inform our community: