@feb22c-cohort :
In anticipation of our meeting on Thursday, here are some useful links:
Looking forward to seeing you there!
@feb22c-cohort :
In anticipation of our meeting on Thursday, here are some useful links:
Looking forward to seeing you there!
Thanks to those who were able to attend our session on Thursday. For those who couldn’t make it, here’s a pretty detailed summary (with links!)(which might also be useful to those of you who were at the session) and of course you can also watch the recording.
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.
Please note, we use the language of “teams” even though several groups in this cohort are mostly driven by one or two main authors who will wear many hats … but a lot of our discussion of logistics can apply to those mini-teams as well! Think of good workflows and documentation and clear author guides and sample chapter as you today be kind to you tomorrow: thinking through structure and making a style guide, etc., will enable to you to come back to your work after you take a break for any of a number of reasons (teaching, life, etc.) or do other tasks as you wear many hats in your OER-creation project, and continue to be effective and to make a great OER!
Here are some key document templates from our session to help guide your collaborators (or future you!) in their writing and editing efforts.
We also briefly mentioned Author Agreements as documents that could help clarify expectations for members in larger teams or instances when smaller teams work with people whom they haven’t collaborated with before.
In addition to the documents above, we also strongly recommend that you also develop a fully worked-out sample chapter. This can do a bunch of things for you and your collaborators:
Please note that both the adaptation of your team’s author guide and the writing of a sample chapter are homework activities, 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. Careful editing can ensure the consistent structure, approach, and tone which reduces the cognitive load on your students – which, as we’ve discussed, is fundamentally a social justice issue! 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:
Centrally, 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.