Resource discovery survey has had a good response.

API Tool for web 2.0 tools

Tracking mechanisms options: trackback (as in blogs); software updater tool built into resource

Quite a lot of content locally inaccessible without authentication (to support customisation and improve teaching/ feedback), so institutional url doesn't actually help check currency

Thinking about pingback mechanism, tracking mechanism, to help support currency and usage information

Having control to take something down is seen as important for risk mitigation.

Project finding that taking resources out of context means that they loose value. Project considers sharing metadata to be better approach than shipping content.

In subject area, resource creators are very keen to keep resources on local servers.

Jorum upload: working on RSS deposit,

Taking resources as comes will interact with and deposit at that granularity.

CP as format received, not as export or working format

MySQL to fit with Subject Centre website

Database primarily as staging tool for creation of OERs, considering whether or not to have local repository as well as JorumOpen

Will need to add metadata at point of upload. For example: licensing, expiry date

Local metadata for resources, storing: author, institution, title (at institution), format, duration (time material plays for), description, subject area (no specific area but could be translated to one), student groups using resource (pedagogical context/ audience), curriculum dependencies (area of knowledge or prior/ subsequent resources), associated credit (not credit bearing or number of credits), and resource management info (status, upload status, created, modified)

Also collecting a significant amount of learning materials and basic metadata about them. Currently working through how much of this material can be released as OERs.

Project focused on looking at processes around clinical materials. IPR, copyright, and patient consent