Metadata and Content Aggregation for UKOER


Published on

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.

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

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.
  • Metadata and Content Aggregation for UKOER

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