OER Synthesis and Evaluation / review thoughts
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Stop wasting time looking for files and revisions. Connect your Gmail, DriveDropbox, and Slack accounts and in less than 2 minutes, Dokkio will automatically organize all your file attachments. Learn more and claim your free account.


review thoughts

Page history last edited by Lou McGill 7 years, 8 months ago

add this tweet form marion into journey section

Marion Manton@MarionManton

Looking at departmental strategy and OER to suggest where we go next. #oersesame was just the start #ukoer


Jay: Interesting parallel of our OER journeys with Joanna Wild's SCORE research report where she offers an "OER Engagement Ladder" conceived as a way to help participants articulate what engagement with OER reuse means to them, how it manifests itself, and how it can be fostered. And indeed early on, she asked the question to participants "Is ladder metaphor a good way to model progression stages in people’s engagement with OER?" and most were positive about how that helped them talk through their OER journey. Fifteen recommendations are summarised, could be quite useful as a checking back with our synthesis findings :)


must refer to oergate - about metatdata but indicative of continued commitment and strong community

Lorna Campbell



Amber Thomas


Many people might still see benefits of signifying their content is contributing to a UK OER commons. That commons is the real impact of the programme and it would be healthy to see that continue.


However our decision about whether to encourage continued use of the “ukoer” tag will not just be about best practice. It is about weighing up best practice against common practice and the cultural considerations. At the risk of sounding like I’m overcomplicating things: it is a socio-technical issue. There is a balance to be made between the stated or tacit requirements of funders, the role Jorum plays for the funders, the role of Jorum for contributors, and the effort of people involved with OER. Of course by contributors, we are talking about the deposit/share point within an institution or team, who need to keep messages and requirements as simple as possible.


We are lucky to have experts in this field, including two members of the Jorum team who wrote about the challenges of metadata in learning object repositories  and members of JISC Cetis who are writing about resource description in OER. I have gathered their input into this post so that we can try to start articulating the issues here. It is through this exchange that we can make the right decisions for JISC, HEA and the wider community.


The point I make here is that we have before us a classic problem space. It illustrates that metadata decisions are about current and future use, that they are about balancing the needs of contributors and users, and that these things require discussion and the unpacking of assumptions. There are solutions out there, involving the sources, the aggregations … but it depends on what we want.

What’s the answer? Should we continue using ukoer as a community tag for a fuzzy concept or try to restrict use to a controlled tag for a funding stream? If we chose the latter (for any reason) could it actually be controlled in that way?


Jay: Quite a few discipline and generic examples are provided in Ming Nie's SCORE final report where her study resulted in a model of reuse patterns adopted by academics in higher education, outlines four categories arising from a quadrant of design/delivery vs Used 'as is' (just in time) / Repurposed (structured), since ratified.


Jay: To include a specific section on ACCESSIBILITY for OER release/use, Anna Gruszczynska's SCORE project/case study examined barriers and enablers in considering accessibility issues and taking steps to making open educational resources accessible, by examining approaches taken by UK OER projects. It resulted some clear list of findings/factors.


Comments (0)

You don't have permission to comment on this page.