Learning Object Repository (UBC – Applied Science)
At one time, I thought eventually we would end up with one large, dominant repository for learning objects. Instructors and developers would use this central repository for adding, selling, acquiring learning objects. That view has changed. It seems that learning object repositories are more like web pages – every institution has one (or will have one)…and each will have functionality, look, and feel in keeping with the branding of the organization. This personalized, decentralized approach is probably a good thing…but some standardization is needed. If this is trend (everyone creating their own repository), then two things are needed in order for repositories to be useful to others outside of a particular institution (after all, repositories are most useful when they can connect and foster learning resource exchange between collleges/universities/schools…not just internally):
- A standard for learning object repositories. HTML is simple, flexible, effective. Yet it allows browsers to access most websites. A similar standard is needed for LORs…but it has to be simple. This standard should dictate how learning objects are exposed to tools seeking to locate/explore them. I’m not sure if RSS is the final answer…
- A search service. Google makes the Internet valuable. 4 billion pages without organization has no more value than 1000. The organization is the value. Learning objects need to be “findable” to have value.