Session 8: Editing - October 2022A Cohort

Hello, @oct22-a-cohort! I look forward to seeing you on Thursday to discuss authoring and editing logistics. The activity around content structure last week is really useful for thinking about your chapter structures and we encourage you to spend some time with that for planning your content.

Here are the Week 8 slides and handout .

Also, we’re not sure again what happened with all of the invitations for the Zoom room. Here is the link, just in case it got lost in your inbox -
Passcode: 794785
Meeting ID: 882 0325 8342
One tap mobile
+16469313860,88203258342# US
+19292056099,88203258342# US (NewYork)

Dial by your location
+1 646 931 3860 US
+1 929 205 6099 US (New York)
+1 309 205 3325 US
+1 312 626 6799 US (Chicago)
+1 301 715 8592 US (Washington DC)
+1 305 224 1968 US
+1 719 359 4580 US
+1 253 205 0468 US
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
+1 360 209 5623 US
+1 386 347 5053 US
+1 507 473 4847 US
+1 564 217 2000 US
+1 669 444 9171 US
+1 669 900 6833 US (San Jose)
+1 689 278 1000 US
Meeting ID: 882 0325 8342
Find your local number: Zoom International Dial-in Numbers - Zoom

Join by SIP

Join by H.323 (US West) (US East) (India Mumbai) (India Hyderabad) (AmsterdamNetherlands) (Germany) (Australia Sydney) (Australia Melbourne) (Singapore) (Brazil) (Mexico) (Canada Toronto) (Canada Vancouver) (Japan Tokyo) (Japan Osaka)
Meeting ID: 882 0325 8342
Passcode: 794785

Thank you to those who attended our session today. Those who couldn’t attend, please find the recap below. We worked on the homework during the session, so please try to find for that as well.

Session 8 helped emphasize the importance of authoring and editing logistics because we know from experience that if you carefully prepare and document your processes, you can move your teams through this stage more smoothly.

A clearly defined author guide will help your authors create content with accessibility, equity, and open pedagogy in mind. This, in turn, will also streamline the work of your editors as it hopefully reduces the time they need to remediate accessibility or equity issues after the fact.

Additionally, for multiperson teams, it may be helpful to develop a content tracking sheet as it can help your teams track who’s been tasked with the authoring and editing of specific content items including interactive content.

In addition to the documents above, we recommend that you also develop a sample chapter since it can be especially helpful for projects with more than one contributing author. A sample or model chapter does a variety of things for your collaborators:

  1. It can help you convey the desired tone and style(s) of your writing. Seeing an example of a well-executed idea or chapter can help other authors with their drafts!
  2. It helps you determine the sequence of textual and non-textual elements in the chapters. This is a chance for you all to test the chapter structure you worked on last week!
  3. Last but not least, your sample chapter will demonstrate your standards for accessibility and inclusive, culturally relevant materials.

Please note that both the adaptation of your team’s author guide and the writing of a sample chapter are homework activities (though we started on them during the session), laid out in more detail for you in the handout for session 8. We recommend that you adapt and further develop these documents together with your teams and then share them with everybody as they embark to create or adapt content for your OER.

In the second part of our session, we talked about editing, which is important in that it gives your OER structure and appeal and thereby significantly impacts how useful it is for learners. The editing process - be it the more substantial enterprise or more focused on copyediting and proofreading - can benefit from the diverse perspectives in your teams as it puts you in a position to push for the changes that place equity at the core of your work.

Since there is no “one size fits all approach” to editing workflows, you can determine your teams’ approach by considering the following few pieces of advice:

  1. Editing needs time, so plan well for it. Be intentional with your time and energy by avoiding too many phases of passing content back and forth between team members.
  2. For the project manager - we also recommend the timeless strategy of underpromise and overdeliver on deadlines. This builds in some cushion for when deadlines get pushed back.
  3. Be sure to foreground exactly what type of feedback you are looking for at this stage, as it can be tempting for folks to give a bit too much for the context. It’s okay to be directive here and provide a list and/ or style sheet that lays out what exactly should be checked.

We always suggest: don’t let great be the enemy of good. Don’t dwell on making everything perfect on the first go. Remember that OER are living documents with opportunities for improvement in future versions.

The final part in our session was dedicated to an editing practice activity that helped us identify a number of accessibility issues in an example chapter. If you are curious or want to go back to the activity, you can find the instructions and solution key in the editing activity template linked here.

Next week, we’ll look at more ways to get feedback and input on your projects — through peer and other kinds of review. Getting a seal of approval or recommendation from an external reviewer can help make your OER stronger and more appealing to adopters, so we’ll see how you can work that into your projects.

Hi @oct22-a-cohort,

My article I mentioned yesterday, Worth the time: Exploring the faculty experience of OER initiatives is now live and in Manifold. I’m curious if it will resonate with your experiences.