UKOER 2: without the collections strand

An intial look at UKOER without the collections strand (C). This is a post in the UKOER 2 technical synthesis series.

[These posts should be regarded as drafts for comment until I remove this note]

In my earlier post in this series on the collections strand (C), I presented a graph of the technical choices made just by that part of the programme looking at the issue of gathering static and dynamic collections, as part of that process I realised that, although the collections strand reflects a key aspect of the programme, and part of the direction future I hope future ukoer work is going, a consideration of the programme omitting the technical choices of strand C might be of interest.

The below graphs are also the ones which compare most directly with the work of UKOER 1 which didn’t have an strand focused on aggregation.

Platform related choices in UKOER2 excluding the collections strand

Platform related choices in UKOER2 excluding the collections strand

Standards related choices in UKOER2 excluding the collections strand

Standards related choices in UKOER2 excluding the collections strand

I’m hesitant to over-analyse these graphs and think there’s a definite need to consider the programme as a whole but will admit, that a few things about these graphs give me pause for thought.

  • wordpress as a platform vanishes
  • rss and oai-pmh see equal use
  • the proportional of use of repositories increases a fair bit (when we consider that a number of the other platfoms are being used in conjunction with a repository)


now in a sense, the above graphs fit exactly with the observation at the end of UKOER that projects used whatever tools they had readily available. However, compared to the earlier programme it feels like there are fewer outliers – the innovative and alternative technical approaches the projects used and which either struggled or shone.

Speculating on this it might be because institutions are seeking to engage with OER release as part of their core business and so are using tools they already have, it might be that most of the technically innovative bids ended up opting to go for strand C, or I could be underselling how much technical innovation is happening around core institutional technology (for example ALTO’s layering of a web cms on top of a repository).

To be honest I can’t tell if I think this trend to stable technical choices is good or not. Embedded is good but my worry is that there’s a certain inertia around institutional systems which are very focused on collecting content (or worse just collecting metadata) and which may lose sight of why we’re all so interested in in openly licensed resources (See Amber Thomas’ OER Turn and comments for a much fuller discussion of why fund content release and related issues; for reference I think open content is good in itself but is only part of what the UKOER programmes have been about).


  • the projects have been engaged in substantive innovative work in other areas, my comments are purely about techincal approaches to do with managing and sharing OER.
  • when comparing these figures to UKOER graphs it’s important to remember the programmes had different numbers of projects and different foci; a direct comparison of the data would need a more careful consideration than comparing the graphs I’ve published.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s