and the introduction of sponsored links, has resulted in the common scenario of millions of
results returned from a search, with a rating system based on commercial gains. As a result
online catalogues of web based resources have emerged that offer access to just educational
resources and provide a more valid rating system such as peer review and star rating.
Examples of these online catalogues of web based learning resources include MERLOT
1
, the
Resource Discovery Network
2
and EdNA Online
3
(also see Section 2 of this report).
1.5.5 Supporting a community
There are at least two scenarios regarding the creation of a learning repository to support a
community.
The first is that a community exists and has a requirement for repository functionality. It may
be the core functionality such as storage and retrieval, or it may be the additional functionality
found with (most) learning repository initiatives such as discussion forums, mailing lists and
authoring tools.
The second scenario is that a learning repository is implemented with the intention of building
a community of users.
Repositories are created in the hope that a community of practice will arise
around them and that this community of practice will use the materials made
available to it and, in many cases, improve the collection of those materials.
[ADL 2003, p.5]
1.6 User Expectations of a Repository System
It is often the case that technology can drive the requirements, articulated as a solution in
search of a problem. It is very important that learning repositories are built with a focussed
strategy and purpose in mind. One of the most effective methods for this is awareness of the
community that the repository aims to serve and support. By establishing the expectations
and requirements of the users the intended goals and objectives of the repository can be
established. This is not to suggest that users always know what they need; it is often stated
that users didn't require Google before it was invented. However, establishing a community's
expectations and their needs is a valid and important starting point.
In 2004 the Academic ADL Co Lab conducted a series of informal surveys, surveying
partners, project representatives, and interested parties regarding the functionalities they
expected and preferred to find within a repository system [ADL 2004]. This section draws out
the expectations of users resulting from this research and examines the associated issues
arising from these requirements in relation to feasible implementations.
1.6.1 Main Requirements
The main user requirements covered in this section are metadata management, content
management, interoperability and community support. Additional requirements are listed but
form the subject of separate reports.
Metadata Management
1
Merlot website at
www.merlot.org
2
Resource Discovery Website at
www.rdn.ac.uk
3
EdNA Online website at
www.edna.edu.au
Page 11 of 84
Unlimited Web Hosting
|
|
TotalRoute.net Business web hosting division of Vision Web Hosting Inc. All rights reserved. |