Looking at setting up aggregator to get RSS feeds into blog to provide update of latest resources in OpenJorum and other sources - this provides a more sustainable community view.

GeoCoding/ GeoTagging - GoogleEarth project marking items for upload. [I'm not sure of right term; standard in use by partners not known.]

Licensing: possible future issue if Ordinance Survey data used

Top three hoped for changes in JorumOpen: GEES don't appear at top level of any JACS codes, hoping that subject schemes are revisited; best practice scope notes on use of fields in upload tool; problem with link only records - only button 'export resource' sends you zipped link doesn't take you to resource ; page generally confusing

Tracking: considering adding to back page request for feedback; this presents an opportunity for qualitative information

Resource tracking and evaluation - not yet been able to address these issues beyond mechanisms in place at host repositories

Versioning: project has thought carefully about this- realise that you can't control verisoning beyond local; some reservations about how OER-licensed resources and versions work with sensitive/ rapidly changing topic

Versioning and duplicate copies: thought about multiple copies in many places but eventually decided to have stuff only in one place - some stuff in OpenJorum or in Institutional Repository

Due diligence and provenance data - if OER pursued legally and take down policy not enough - project considering how and where to keep this data - where does this go?

Licensing: project suggested to partners Office plugin for CC licenses (use not fully known)

Licensing and cover pages: included cover page and back page to resources with acknowledgement and detailed license info. Also encouraging partners to look encoding license information into images etc.

Licensing: complex licensing issues because of materials involved - some logos; some diagrams from publishers; resource under one license and elements of them under specific (restricted) licenses

Materials are well branded and polished - partners engaged institutions with benefits to institutional profile

Flickr and YouTube materials linked from powerpoints (as they're embedded in usable resources)

Granularity: producing polished coherent resources that learners can pick up and use (and that academics could use pieces of)

Jorum upload- so far using upload tool; this has been done by subject centre but this is now also being adopted by some partners directly

Partners have also been recording UKOER tag and GEESOER tag in their repositories

Looking at mechanism for partners to move metadata directly to OpenJorum

Partners Repositories Southampton - edshare ; OU Openlearn ; Keele - DSpace?

When originally using UPlaCe repository were basing metadata on Jorum's model

JorumOpen: no guidance about Author name ordering; best practice needed for browsing / searching

JorumOpen: Other fields that would be useful: resource type and education level (although limitations of edu level acknowledged)

JorumOpen: Concern over lack of date when resource made and associated institution (which is frequently the owner)

JorumOpen: Concerns over lack of guidance about how to fill in information into OpenJorum tool; lack of institutional field; noting people using fields in very different ways

As a project they aren't using a central repository. Project partners provide items/ links. Three using institutional repositories and three providing materials being uploaded directly to Jorum

Repurposing some older TLTP materials - seeing if they can become OERs; looking at two approaches and using Xerte for these

Moved to JorumOpen as central repository; use of UPlaCe diminished; concern though about being able to showcase GEES specific content in JorumOpen

Check what standards UPlaCe uses

Release project?

Support for Adobe Authorware remains a concern for the projects