On 6 Apr 2012, at 20:26, Pat Lockley wrote:

> Shouldn't we agree one though as JLern submitters? I'm not sure early
> submitters creating a standard sounds like a good idea

We're probably just as well off experimenting with the service for a while first before trying to identify potential extra standards - I don't think I'll know if the approach I'm taking now is going to work until I hook it into at least two stores and try to get them interoperating using it..

At the moment I'm using some of the examples here as a starting point:

https://docs.google.com/document/d/19ZkVpxQn1O1dLhCZClkQkzvypziBI7gBytszTxgXmX0/edit?hl=en_US

> 
> On Fri, Apr 6, 2012 at 7:59 PM, Scott Wilson
> <[log in to unmask]> wrote:
>> 
>> On 6 Apr 2012, at 19:36, Daniel Rehak wrote:
>> 
>> Pat
>> 
>> We started with the activity streams model, and then extended it -- so LR
>> paradata can be mapped to AS, but it will be lossey.
>> 
>> In LR we ask for people to submit one piece of data at a time, but the full
>> paradata spec does use the packaging model from AS to bundle things.  But
>> none of LR uses that.
>> 
>> LR doesn't have a standard strategy for what to submit -- e.g., each event,
>> an incremental time summary/aggregate over some period (each week, each
>> month), a cumulative summary "to date".  We wanted the community to be able
>> to do what they think is best.
>> 
>> 
>> Sounds like a sensible approach.
>> 
>> For our use in widget/app stores we'll be using individual events for user
>> reviews,  but for downloads and embeds we'll probably use aggregate-to-date
>> stats . As we encounter other UCs we'll have to decide which is the
>> appropriate model to use.
>> 
>>     - Dan
>> 
>> On Fri, Apr 6, 2012 at 13:53, Pat Lockley <[log in to unmask]>
>> wrote:
>>> 
>>> After my last post I went to read the LR "Paradata in 20 seconds"
>>> google doc. It seems to delineate the LR paradata from
>>> activitystrea.ms by aggregating the actions together (the examples are
>>> monthly). Of course we could submit something else, but I don't think
>>> we have a standard schema / policy for this.
>>> 
>>> On Fri, Apr 6, 2012 at 6:32 PM, Scott Wilson
>>> <[log in to unmask]> wrote:
>>>> On 6 Apr 2012, at 16:56, Pat Lockley wrote:
>>>> 
>>>>> I think turning the ramanathan or Jeffrey Hill's LRPHP (see github)
>>>>> into an API would be really simple, but I am unsure of what the best
>>>>> publishing policy is? If it's metadata packaged up, I would guess we
>>>>> should delete our metadata package before we add a new one - but that
>>>>> seems open to conjecture? Also if we submit paradata, is it per act,
>>>>> or per month, and do we maintain a core paradata package with all the
>>>>> data in?
>>>> 
>>>> I've been working on a Java lib for publishing and synching LR paradata,
>>>> specifically ratings (reviews and downloads still to go): for ratings I've
>>>> assumed one paradata record per rating on the assumption that ratings and
>>>> comments go hand in hand so its worth keeping them as individual records
>>>> with actor-measure-subject. However I can also see the case for doing
>>>> summaries (e.g. "in our store this app has an average rating of 3.2 from a
>>>> sample of 43 ratings") so will probably add some support for that too.
>>>> 
>>>> In any case I have to filter to remove earlier updates, e.g. see:
>>>> 
>>>> 
>>>> http://scottbw.wordpress.com/2012/04/05/spaws-initial-code-hands-on-with-the-learning-registry/
>>>> 
>>>> Code is at:
>>>> 
>>>> https://github.com/scottbw/spaws
>>>> 
>>>> (& in sonatype snapshots repo for all you Maven fans)
>>>> 
>>>> Putting this lib behind a web API would be pretty easy if you wanted to.
>>>> I guess the main value-added is the de-duplication and filtering.
>>>> 
>>>> S
>>>> 
>>>>> 
>>>>> On Tue, Apr 3, 2012 at 11:02 AM, Julian Tenney
>>>>> <[log in to unmask]> wrote:
>>>>>> What would be really helpful for us is a leg-up with the technology
>>>>>> side of
>>>>>> things. What we would like to do is add some pages to our example at
>>>>>> http://www.nottingham.ac.uk/toolkits/play_560 to ask users to rate the
>>>>>> resource, maybe comment on it and then push that info into the LR.
>>>>>> What we
>>>>>> would really like is some easy method of doing that, I’m thinking
>>>>>> about some
>>>>>> simple API call I can make. I have Pat’s ‘post data to the LR’ php
>>>>>> code, but
>>>>>> it would be much simpler for me to call a service, and I think for
>>>>>> others
>>>>>> too. We could also explore publishing a resource into the LR from
>>>>>> toolkits,
>>>>>> again an API to call would make this easy, and would facilitate
>>>>>> building
>>>>>> other tools by which data can be added to the node, be them widgets,
>>>>>> gizmos,
>>>>>> whatever,
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> From: Open Educational Resources [mailto:[log in to unmask]]
>>>>>> On
>>>>>> Behalf Of Sarah Currier
>>>>>> Sent: 03 April 2012 10:03
>>>>>> To: [log in to unmask]
>>>>>> Subject: JISC OER RI projects working with the JLeRN on Learning
>>>>>> Registry
>>>>>> stuff
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Hello all,
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> See below for link to (and text of) JLeRN blog post on OER Rapid
>>>>>> Innovation
>>>>>> projects working with JLeRN and/or the Learning Registry.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Had a brief chat with Suzanne Hardy at the end of the Programme
>>>>>> Meeting last
>>>>>> week about what might help these projects, and any others interested
>>>>>> in
>>>>>> JLeRN / The Learning Registry.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Can you please shout if (a) you have an OER RI (or any OER) project
>>>>>> interested in this stuff and I haven’t mentioned you in the blog post,
>>>>>> and
>>>>>> (b) if you have an idea of what might be helpful for you to move on
>>>>>> with
>>>>>> this aspect of your project.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Suzanne and I were just thinking, maybe a kick-off virtual meeting of
>>>>>> some
>>>>>> kind (with CETIS input too).
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Thanks
>>>>>> 
>>>>>> Sarah
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> From: Sarah Currier [mailto:[log in to unmask]]
>>>>>> Sent: 03 April 2012 09:55
>>>>>> To: Sarah Currier
>>>>>> Subject: Fwd: Some new UK-based JISC projects working with the JLeRN
>>>>>> on
>>>>>> Learning Registry stuff
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> ---------- Forwarded message ----------
>>>>>> From: Sarah Currier <[log in to unmask]>
>>>>>> Date: 3 April 2012 09:54
>>>>>> Subject: Some new UK-based JISC projects working with the JLeRN on
>>>>>> Learning
>>>>>> Registry stuff
>>>>>> To: [log in to unmask]
>>>>>> 
>>>>>> 
>>>>>> Hello all,
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> For those who don't follow the JLeRN blog, thought you might be
>>>>>> interested
>>>>>> in these new JISC-funded projects (blog post
>>>>>> here:
>>>>>> http://jlernexperiment.wordpress.com/2012/04/03/jlern-and-the-jisc-oer-rapid-innovation-projects/
>>>>>> ).
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Text of post here:
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> JLeRN and the JISC OER Rapid Innovation Strand
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> The HE Academy / JISC OER3 Programme‘s new Rapid Innovation strand
>>>>>> projects
>>>>>> kicked off last week in London at the Programme Meeting. We are
>>>>>> thrilled
>>>>>> that there are four projects within the strand who want to work with
>>>>>> us on
>>>>>> Learning Registry related developments.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> With only four months left for JLeRN, we want to make the most of the
>>>>>> time
>>>>>> we have, and participating in well-thought-out projects meeting real
>>>>>> requirements in the OER space seems like a good way to consolidate
>>>>>> what
>>>>>> we’ve learned so far. All of these projects involve folk who supported
>>>>>> us by
>>>>>> coming to the Hackday in January and the CETIS Conference Learning
>>>>>> Registry
>>>>>> session in February so it’ll be nice to give something back.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> The four projects we are working with are as follows (NB: There were a
>>>>>> few
>>>>>> other sparks of interest in the OER Rapid Innovation projects’
>>>>>> breakout
>>>>>> session, so I think we may pick up a few more along the way: don’t be
>>>>>> shy to
>>>>>> get in touch if you’d like to work with us):
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Rapid Innovation Dynamic Learning Maps-Learning Registry (RIDLR)
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Based at Newcastle University, and led by Simon Cotterill, this
>>>>>> project will
>>>>>> build on their Dynamic Learning Maps work, and their FavOERites social
>>>>>> bookmarking project, to develop “open APIs to harvest and release
>>>>>> paradata
>>>>>> on OER from end-users (bookmarks, tags, comments, ratings and reviews
>>>>>> etc.)
>>>>>> from the Learning Registry and other sources for specific topics,
>>>>>> within the
>>>>>> context of curriculum and personal maps.”
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Sharing Paradata Across Widget Stores (SPAWS)
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Based at Bolton University (with partners KMi (Open University); IMC
>>>>>> AG,
>>>>>> Saarbruecken; Katholieke Universiteit Leuven, Belgium) and led by
>>>>>> Scott
>>>>>> Wilson, this project will use the Learning Registry infrastructure to
>>>>>> share
>>>>>> paradata in the form of user views, reviews and ratings about
>>>>>> educational
>>>>>> widgets across four existing widget stores.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Xerte Experience Now Improved: Targeting HTML5 (XENITH)
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Based at Nottingham University (with partners JISC TechDIS, EDINA and
>>>>>> Mimas
>>>>>> (us!)), and led by Julian Tenney, this project builds on the Xerte
>>>>>> Online
>>>>>> Toolkits, which integrates directly with the Xpert Repository. As an
>>>>>> adjunct
>>>>>> to its main development work, it will explore sharing metadata and
>>>>>> paradata
>>>>>> about Xerte resources with the Learning Registry.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Track OER: Tracking Open Educational Resources
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Based at the Open University, and led by Patrick McAndrew, this
>>>>>> project aims
>>>>>> to “develop software that can help track open educational resources”
>>>>>> as they
>>>>>> are used away from their point of origin. JLeRN has already entered
>>>>>> discussions with them to ensure mutual affordances are identified.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> In addition to these projects, the University of Liverpool will soon
>>>>>> be
>>>>>> working with the JLeRN team to set up their own node. As well as
>>>>>> assisting
>>>>>> with meeting Liverpool’s requirements, this will enable JLeRN to
>>>>>> experiment
>>>>>> with sharing data between nodes at different locations. Work with
>>>>>> Jorum will
>>>>>> continue, and discussions have begun with the JISC Resource Discovery
>>>>>> Programme to widen the reach of the Learning Registry concept. Watch
>>>>>> out for
>>>>>> blog posts on all of these activities!
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Cheers all, comments and questions welcome: the blog post has project
>>>>>> links
>>>>>> in it.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Sarah
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Sarah Currier  |  Jorum Technical Coordinator (R&D Projects)  |  JLeRN
>>>>>> Experiment Project Lead
>>>>>> 
>>>>>> Mimas  |  Roscoe Building (5th Floor)  |  Oxford Road  |  The
>>>>>> University of
>>>>>> Manchester  |  Manchester  |  United Kingdom  |  M13 9PL
>>>>>> 
>>>>>> Tel.: +44 (0)161 275 6034 (ext. 56034)  |  Mob.: +44 (0)7980855801
>>>>>> 
>>>>>> E-mail: [log in to unmask]
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Skype & Twitter: morageyrie
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> This message and any attachment are intended solely for the addressee
>>>>>> and
>>>>>> may contain confidential information. If you have received this
>>>>>> message in
>>>>>> error, please send it back to me, and immediately delete it. Please do
>>>>>> not
>>>>>> use, copy or disclose the information contained in this message or in
>>>>>> any
>>>>>> attachment. Any views or opinions expressed by the author of this
>>>>>> email do
>>>>>> not necessarily reflect the views of the University of Nottingham.
>>>>>> 
>>>>>> This message has been checked for viruses but the contents of an
>>>>>> attachment
>>>>>> may still contain software viruses which could damage your computer
>>>>>> system:
>>>>>> you are advised to perform your own checks. Email communications with
>>>>>> the
>>>>>> University of Nottingham may be monitored as permitted by UK
>>>>>> legislation.
>> 
>> 
>> 
>> 
>> --
>> Daniel R. Rehak, Ph.D.
>> 
>> Skype: drrehak
>> Email:  [log in to unmask]
>> Twitter: @danielrehak
>> Web:   learningregistry.org
>>             lsal.org
>> Google Voice: +1 412 301 3040
>> Tel:       +1 412 931 7317
>> Work:   +1 412 931 7319
>> Mob:    +1 412 805 7683
>> 
>>