This document summarizes research analyzing metadata from over 630,000 learning objects using the Learning Object Metadata (LOM) standard. The analysis found that LOM instances take up around 5KB of storage space on average. Only 20 of LOM's 50 elements are used frequently, capturing similar information to the Dublin Core standard. Educational elements are underused and dependent on individual communities. Validation found loose implementation of LOM's XML structure results in good interoperability despite unclear value spaces. Metadata quality is varied, showing a need for quality assurance processes. The conclusion advocates for more studies of this kind to improve metadata standards and learning technologies.

1. On the use of Learning Object Metadata the GLOBE experienceXavier Ochoa, ESPOLJorisKlerkx, KULeuvenBram Vandeputte, KULeuvenErik Duval, KULeuven

2. http://www.slideshare.net/xaoch

3. LOM is known and widely usedBut its real use is not known

4. How much space 1000 LOM instances will take?What are the most used elements of LOM?Is it really a “standard”?Has it been extended as designed?What is the information stored in real instances?Is it better than Dublin Core for Educational Resources?

5. We need: Large-Scale, Real-World, HeterogeneousWe select: GLOBE

6. GLOBE

7. http://www.globe-info.org/

8. Large-Scale: 630.000+ instances Real-World: being used and createdHeterogeneous: 7 networks of LORs 4 continents

9. ResultsThe interesting stuff

10. Size

11. Size≈ 5 Kb

12. LOM Elements UseWhat parts of LOM are used anyway?

14. G.TitleG.IdentifierG.LanguageG.DescriptionG.KeywordL.ContributionRoleL.ContirubtionEntityM.IdentifierM.ContributorRoleM.ContributorEntityM.ContributorDateT.LocationT.FormatE.LearningResourceTypeR.CopyrightR.CostR.DescriptionC.TaxonPathC.PurposeC.Taxon

15. G.TitleG.IdentifierG.LanguageG.DescriptionG.KeywordL.ContributionRoleL.ContirubtionEntityM.IdentifierM.ContributorRoleM.ContributorEntityM.ContributorDateT.LocationT.FormatE.LearningResourceTypeR.CopyrightR.CostR.DescriptionC.TaxonPathC.PurposeC.TaxonCreatorIdentifierTitleDateTypeSubjectDescriptionLOMDC

16. G.TitleG.IdentifierG.LanguageG.DescriptionG.KeywordL.ContributionRoleL.ContirubtionEntityM.IdentifierM.ContributorRoleM.ContributorEntityM.ContributorDateT.LocationT.FormatE.LearningResourceTypeR.CopyrightR.CostR.DescriptionC.TaxonPathC.PurposeC.TaxonCreatorIdentifierTitleDateTypeSubjectDescriptionLOMDC

17. LOM uses 20 out of 50 elementsBut captures more information than DC

18. Educational Section

19. 4 out of 11 Educational elements Community dependent

20. LOM Vocabulary UsageWhat is stored on LOM?

21. Educational.Context

22. Right.Cost

23. Rights.Copyrights

24. If you too want to play...http://is.gd/globemetadata

25. LOM ExtensionsWhat LOM forgot…

26. Only 3 additions:General – Learning Object Kind (MACE) 30.000 InstancesTechnical – Geolocation (MACE)7.000 InstancesGeneral – Subtitle (KERIS)5.000 Instances

27. There is little need of extensionNobody wants more electronic fields!

28. LOM XMLValidation AnalysisIs it an interoperability standard?

29. LOM validation

30. Most common errors (loose)

31. LOM XML loose is widely implementedLOM XML strict is not

32. Good structural interoperabilityAlthough the value space is not clear

33. vCard causes 68% errorsLOM developers hate vCard

34. LOM Metadata Quality AnalysisThose pesky indexers…

35. Diversity of Vocabulary usage

36. Diversity of Vocabulary usage

37. Diversity of Vocabulary usage

38. Quality of Textual Descriptions

39. Quality of Textual Descriptions

40. Quality of Textual Descriptions

41. Quality of Textual Descriptions

42. There must be a QA processThat is true for bothautomatic and manual metadata

43. Conclusion of the ConclusionsThis kind of studies should be made an integral part of the development of LOM(or any other metadata standard)(or any other Learning technology)

44. Want the data?Want the code?https://sites.google.com/site/globemetadata/

45. Gracias / Thank you / GrazieXavier Ochoaxavier@cti.espol.edu.echttp://ariadne.cti.espol.edu.ec/xavierTwitter: @xaoch