24 May 2012
We are pleased to be attending Dev8Ed next week in Birmingham and are grateful to the organisers for allowing us so much time to talk about and work on technical developments for PublishOER (funded under UKOER3), which have areas of cross over with two OERRI projects (RIDLR and SupOERGlue), all of which are of interest to our major partner in PublishOER, Elsevier.
There will be five of us from the team (including 4 developers) at Dev8Ed, and we'll be taking part and leading lightening talks, workshops and presentations about our work.
Please see the programme at - we are in the green stand mainly.
We've put a set of objectives together, but are open to adding to them, and don't expect to complete more than one or two from this list:
|
Objective |
Overview of work needed |
Helps project |
|
|
1 |
Plugin a two way API onto the PublishOER Permission Application System, to allow the flow of information from the system to external sites. |
Create a two way API for the PublishOER Permissions Application System. Once a user has filled in the appropriate information of the application system, an api call should alert an external site (Publisher) that an application is ready. The Publishers website should then call the Permissions systems API to retrieve the data, record that data and then update the Permission system with a new status. This status could be:
Completed, Actions Needs, Rejected. |
PublishOER |
|
2 |
Export a map from DLM into ePub format with license information
[get this done before OER hack day??]
|
DLM: new license-types table (id, license, url, default) DLM: export topic-set as ePUB; select license DLM: link topic-set and selected license type DLM: log user, date of export and license DLM: inherit topic-set when creating child topics
-needs discussion/work to refine ‘topic sets’ or just use any point in the tree? Control/Ownership issues to address. Need library / API |
PublishOER DLM |
|
3 |
Export map as above -include an element from another ePub file (e.g. diagram from Elsevier)
|
DLM: how to reference/import this element (as a topic? as meta data?) ePUB: how to extract info: Publisher, License, buy-the book URL, meta data etc. ePUB: how to embed the above information in the combined ePUB
|
PublishOER DLM |
|
4 |
Plugin a two way API onto the PublishOER Permission Application System, to allow the flow of information from the system to external sites. |
Create a two way API for the PublishOER Permissions Application System. Once a user has filled in the appropriate information of the application system, an api call should alert an external site (Publisher) that an application is ready. The Publishers website should then call the Permissions systems API to retrieve the data, record that data and then update the Permission system with a new status. This status could be:
Completed, Actions Needs, Rejected. |
PublishOER |
|
5 |
Export map as above -include an element from another source + details of permission from publisher (Dan’s work)
|
As above + how to embed permission & scope of usage e.g. diagram permission to use from Elsevier; scope=Newcastle University only? |
PublishOER DLM |
|
6 |
Export map as above -include an element from Learning Registry (simple element e.g. Image or txt)
|
DLM: how to reference/import this element (as a topic? as meta data?) ePUB: how to extract info: Publisher, License, URL, version etc. ePUB: how to embed the above information in the combined ePUB
|
RIDLR PublishOER DLM |
|
6 |
Build an aggregated online resource using OERGlue -embed in DLM
|
OERGlue: how to embed?; API |
SupOERGlue DLM |
|
7 |
Build a complex aggregated resource; potentially including 1-4 (view online; content package; other formats?)
|
DLM: how to sequence resources? how to embed info: Publisher, License, buy-the book URL, meta data etc.
|
PublishOER RIDLR SupOERGlue DLM |
|
8 |
Feeding back ‘paradata’
|
|
RIDLR PublishOER SupOERGlue DLM |
|
9 |
Export to PDF * |
For the above scenarios 1-4
|
DLM PublishOER RIDLR
|
We also put a process diagram together illustrating how the work relates to developments and projects. Anywhere you see a box there will be an opportunity to use an API to get access to different data streams at some point before the end of the projects (all due to finish in October).

There are additional links in several other places, but we though we'd share this rough draft early (we are doing stuff David and Amber ;)).
In summary
PublishOER (UKOER3 project): Working with publishers to find new business models enabling risk free incorporation of published materials into OER (including development work for centralising a business process for dealing with permissions requests to publishers, publishing to multiple publication formats from single source, dealing with multiple licences, etc)
Additional technical development work (SupOERGlue & RIDLR OERRI projects) to Newcastle University's novel Dynamic Learning Maps (see https://learning-maps.ncl.ac.uk) system, enabling creation of resource mashups using OER bookmarking (http://oerbookmarking.ncl.ac.uk/) and OER Glue (http://www.oerglue.com/) from within the learning environment and sharing of contextually rich curriculum related meta and paradata about learning resources via API/JLeRN to other users including publishers/HEIs. The Newcastle team develops with Django and Python. Other languages are not barriers to working with us.
We are very interested in working with others e.g.
Here are our slides for the PublishOER lightening talk on day one.
Related tags: dev8ed, oer phase 3, oerri, publishOER, RIDLR, supoerglue, technical development, ukoer
Posted by: Suzanne Hardy
Posted in: Suzanne's blog, OER rapid innovation: RIDLR, OER rapid innovation: SupOERGlue, OER phase 3 blog