1 / 47

LRE Metadata Application Profile v4.0

LRE Metadata Application Profile v4.0. David Massart, EUN Budapest, Hungary – Nov. 2, 2009. Outline. LRE Overview LRE Limitations LRE Metadata Application Profile v4.0 Managing and Using Vocabularies Identifying Resources ASPECT Service Center . LRE Metadata Application Profile.

cirila
Download Presentation

LRE Metadata Application Profile v4.0

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LRE Metadata Application Profile v4.0 David Massart, EUN Budapest, Hungary – Nov. 2, 2009

  2. Outline • LRE Overview • LRE Limitations • LRE Metadata Application Profile v4.0 • Managing and Using Vocabularies • Identifying Resources • ASPECT Service Center

  3. LRE Metadata Application Profile • http://fire.eun.org/LREMAPv4p0.pdf

  4. LRE Portal

  5. It isNOT a centralised portal… But a frameworkthat supports semantic and technical interoperability of content repositories LRE Vision

  6. Learning Resource Exchange An infrastructure for • Federating applications that provide learning resources (e.g.,  learning resource repositories, authoring tools) • Offering a seamless access to these resources to educational applications that consume them (e.g., educational portals, VLEs, IWBs)

  7. A Metadata Problem

  8. LREv3.0 Limitations (LOM)

  9. LREv4.0 (ILOX + LOM)

  10. Expression (version)

  11. Description

  12. Vocabulary Type

  13. Expression Description Facets VBE Vocabulary Identifier: LRE.expressionDescriptionFacetValues

  14. Identifier Type

  15. Manifestation (format)

  16. Item (copy)

  17. Item Location • URI (resolvable location: e.g., a URL or a persistent identifier for a copy of the LO - handle, DOI, PURL) • Description: Metadata (optional)

  18. Item Sub-elements • “location.uri” should be resolvable • Either it resolves to the location of the object (no location.metadata permitted) • Or it resolves to the location of a service that gives access to the object (mandatory location.metadata to describe the access control service) • Non-resolvable identifier should be put in item.identifier • Other descriptions should be put in item.description

  19. Describing Expressions with IEEE LOM • No mandatory elements • Mandatory way to use elements (controlled vocabularies) • Core elements • Recommended elements • Optional elements • Unused elements

  20. Core Elements • General.Language – LOM 1.3 • Educational.Learning Resource Type – LOM 5.2 • Rights – LOM 6 • CORE = Optional but necessary

  21. Recommended Elements • General.Title - LOM 1.2 • General.Description - LOM 1.4 • General.Keyword - LOM 1.5 • Life Cycle.Contribute – LOM 2.3 • Meta-Metadata.Language - LOM 3.4 • Educational.Intended End User Role - LOM 5.5 • Educational.Learning Context - LOM 5.6 • Educational.Typical Age Range – LOM 5.7 • Classification – LOM 9 • Recommended = Optional but good to have

  22. Unused Elements • Technical – LOM 4 • Classification.Keyword – LOM 9.4 • Unused = Should not be used (conflict with other elements)

  23. Optional Elements • All the elements that do not belongs to the ‘core’, ‘recommended’ and ‘unused’ categories are optional • Might be safely ignored but • When used, some usage rules might have to be followed

  24. LRE Controlled Vocabularies • Key to deal with • Multilingualism • Processable semantics • Managed in a Vocabulary Bank for Education (VBE) where • Each vocabulary and vocabulary term is identified • Term translations are kept • Crosswalks are stored

  25. http://aspect.vocman.com/

  26. Rights.Cost – LOM 6.1 http://aspect.vocman.com/vbe/user/download/LOM/costValues.vdex http://aspect.vocman.com/vbe/user/download/LOM/costValues.zthes

  27. Encoding Vocabulary Term • Authorized values • Source: <VBE Vocabulary Identifier> • Value: <VBE Vocabulary Term Identifier> • Example: • Source = “costValues” • Value = “yes”

  28. Identifiers

  29. What to Identify?

  30. Expression Identifier • Content providers are strongly encouraged • To identify at least LO expressions • To consistently use identifiers • It is possible to use more than one identifier

  31. Metadata Travels

  32. Metadata Travels

  33. >25 Content Providers

  34. LRE Identity Service

  35. Trusted Identifier

  36. Trusted Identifier

  37. Trusted Identifier

  38. Trusted Identifier

  39. Trusted Identifier

  40. Trusted Identifier

  41. Trusted Identifier

  42. Trusted Identifier

  43. Trusted Identifier

  44. Trusted Identifier

  45. Handle System • “Persistent” identifier for LO expression • Stamp (quality label) trusted between LRE members • Can be resolved • Content providers • LRE version of the metadata • Signature verification

  46. Service Center • LOR Registry • Vocabulary Bank • App Profile Registry • Automatic metadata language translation • Automatic metadata format transformation • Automatic content format transcoding • Compliance testing • Identifier service – handle • Access to known interoperability issues

More Related