Your SlideShare is downloading. ×
Metadata and Content Aggregation for UKOER
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Metadata and Content Aggregation for UKOER

977
views

Published on

Basis of webinar for HE Academy/JISC OER programme. Aims: …

Basis of webinar for HE Academy/JISC OER programme. Aims:
Make sure the projects know about CETIS and our role in the UKOER programme.
Make sure the projects are familiar with the programme level technical & metadata requirements.
Get projects to think about their own metadata and technical requirements.
Discuss the relationship of the third of these to the first two.


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
977
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Ask how many projects have contact with inst. Library.
  • Mention out of scopes (except where relevant to aims): IPR, copyright, creative commons; how people use OER , JORUM (next up, Thu 17 Sept).
  • Mention the blogs.
  • Stress uses of metadata mentioned in B
  • Mention contact with libraries
  • Ask who knows what OPML is.
  • Transcript

    • 1. Metadata and Content Aggregation for UKOER
      • Phil Barker <philb@icbl.hw.ac.uk>
      • R. John Robertson <robert.robertson@strath.ac.uk>
      • http://jisc.cetis.ac.uk/
    • 2. Warning!
      • Person-to-person chat is visible to session moderators
    • 3. Introductions
      • What is your role in UK OER?
      • A: Institutional strand
      • B: Individual strand
      • C: Subject strand
      • D: Support / Management / Other
      • [vote]
    • 4. Introductions
      • What is your role in your project?
      • A: Technical / developer
      • B: Manager
      • C: Educator
      • D: Librarian
      • [vote]
    • 5. Session aims
      • Make sure the projects know about CETIS and our role in the UKOER programme.
      • Make sure the projects are familiar with the programme level technical & metadata requirements.
      • Get projects to think about their own metadata and technical requirements.
      • Discuss the relationship of the third of these to the first two.
    • 6. About JISC CETIS
      • JISC Innovation Support Centre: Educational Technology and Interoperability Standards
      • provide strategic technical advice to JISC, supporting its development programmes
      • representing JISC on international standardisation initiatives
      • work with the wider educational community to facilitate the use of standards-based eLearning.
      • support various JISC Programmes, including UK OER
    • 7. Domains and working groups
      • Domains
      • Accessibility
      • Assessment
      • Educational Content (EC)
      • E-Portfolio
      • Enterprise
      • Metadata and Digital Repositories (MDR)
      • Lifelong Learning
      • Pedagogy
      • Working groups :
      • Short life span, specific outputs, smaller in scale than SIGs.
      • Responding to needs of community
      • Some associated with a JISC project or programme
      • E.g.
        • Semantic technologies in teaching and learning;
        • widgets & mashups
        • cloud computing & institutions
        • Content transcoder
        • OER
    • 8. Contacts
      • CETIS Web site: http://jisc.cetis.ac.uk/
      • OER resources: http://wiki.cetis.ac.uk/Educational_Content_OER
      • R. John Robertson <robert.robertson@strath.ac.uk>
      • Phil Barker: <philb@icbl.hw.ac.uk>
      • Lorna M Campbell: <lmc@strath.ac.uk>
      • Sheila MacNeill: <s.macneill@strath.ac.uk>
      • Li Yuan: <L.Yuan@bolton.ac.uk>
    • 9. CETIS OER Support
      • Programme level support for JISC and projects
      • Technical guidelines, e.g.
        • what packaging and syndication formats are used/appropriate
        • what dissemination platforms are used/appropriate
        • what resource descriptions are used/appropriate
        • why and how of resource tracking, versioning, lifecycles
      • Don’t want to be intrusive, but we have some expectation that projects will communicate with us 
      • For more details on how CETIS works see http://www.slideshare.net/philb/jisc-cetis-support-for-ukoer (Slides from UKOER start-up meeting)
    • 10. Metadata: choose your definition?
      • A: data about data
      • B: structured information that describes, explains, locates, or otherwise makes it easier to retrieve, use, or manage an information resource
      • C: pretty much any information about anything.
      • D: any of the above
      • [vote]
    • 11. Activity
      • Think about what one needs to know in order to
        • identify
        • find
        • select
        • use
        • cite
        • manage
      • a resource.
      • Write down what information you think it necessary, and why, under each (some) of these headings.
    • 12. Feedback
      • Use the chat to list share your list
      • One heading at a time please. . .
        • identify
        • find
        • select
        • use
        • cite
        • manage
    • 13. Comments
      • You haven’t had time to finish this activity
      • You (probably) haven’t thought of all scenarios
      • What people want and what you can deliver may be different
    • 14. UKOER Programme Metadata requirements
      • See http://blogs.cetis.ac.uk/lmc/2009/03/30/metadata-guidelines-for-the-oer-programme/
        • ukoer tag
        • Rights
        • Title
        • Author/owner/contributor
        • Date (...)
        • url
        • File format
        • Size
      • How does your list compare? Use the chat to comment on anything you don’t understand or think is not necessary.
    • 15. Exposing metadata
      • Most platforms for sharing/managing resources show lots of metadata (even if you don’t realise it).
      • E.g.
        • http://www.slideshare.net/philb/jisc-cetis-support-for-ukoer
        • http://www.flickr.com/photos/philbarker/376795274/
        • http://www.youtube.com/watch?v=LRBIVRwvUeE
      • Useful for resource discovery via Google
    • 16. Structured Metadata
      • Useful if you want computers to understand the metadata
        • Not necessary for resource discovery via Google
        • Useful for resource management
      • Using a standard structure is useful if you want to share it between computers
        • But does this happen? (vote)
    • 17. Sharing Metadata
      • Did you think of sharing structured metadata in repository-land
        • eg LOM, DC, OAI-PMH, IMS-CP . . .
      • or in web-land?
        • eg RSS, ATOM, OPML . . .
      • (or maybe you thought of library-land
        • eg MARC, RDA, Z39.50, SRU . . .
      • )
    • 18. How will you disseminate your resources?
      • As well as the JorumOpen, how do you plan to make your resources available?
      • A: Nothing else, just the Jorum
      • B: Our own/our partners’ website(s)
      • C: Our own/our partners’ instance of repository s/w (DSpace, ePrints, Intralibrary &c)
      • D: Sites such as Flickr, SlideShare, YouTube, Blogs, iTunes U, YouTube ... (as well or instead of own hosting)
      • (Use chat for alternative answers)
    • 19. RSS/ATOM feeds
      • Will you be providing feeds about your resources?
      • A: No plans / not applicable
      • B: We’ll have one feed for latest resource
      • C: We’ll have feeds for key sets, e.g. all resources for given topic, or results of custom search, ...
      • D: We’ll have feeds for everything, right down to content of individual resources.
      • See OER Technical Considerations Guidance to Bidders http://ie-repository.jisc.ac.uk/280/ (slide 7)
    • 20. Example uses of feeds
      • (hopefully you know about the obvious examples, personal feed readers, blog aggregators, podcasts, netvibes / iGoogle / PageFlakes?)
      • Journals’ Tables of Contents aggregation http://www.tictocs.ac.uk/
      • Podcast aggregation: http://podcast.steeple.org.uk/content/view/133/98/
        • See also http://www.steeple.org.uk/wiki/images/e/ef/EnsembleOverview.gif
      • Publishing to iTunesU
      • CETIS Website
      • Resource content feed: WordPress XML export/import
        • See also http://ouseful.wordpress.com/2009/07/09/single-page-rss-feeds-so-what-so-this/
    • 21. OPML files
      • Will you be providing OPML files for your feeds?
      • A: No plans, haven’t thought about it yet.
      • B: Not applicable, there’ll just be the one feed.
      • C: Yes.
      • D: No (even though we have several feeds).
    • 22. Summary
      • Think of your projects requirements for describing resuorces
        • Remember there are lots of contexts
      • Decide whether & how the resource description needs to be structured / machine readable
        • Remember there are lots of contexts
      • Bear in mind the programme requirements
    • 23. Questions, comments, discussion . . .
    • 24.
      • This work is licensed under the Creative Commons Attribution 2.5 UK: Scotland Licence. To view a copy of this licence, visit http://creativecommons.org/licenses/by/2.5/scotland/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California 94105, USA.