The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH in the remainder of this document) provides an application-independent interoperability framework based on metadata harvesting. There are two classes of participants in the OAI-PMH framework:
- Data Providers administer systems that support the OAI-PMH as a means of exposing metadata; and
- Service Providers use metadata harvested via the OAI-PMH as a basis for building value-added services.
In this document the key words "must", "must not", " required", "shall", "shall not", "should", " should not", "recommended", "may", and "optional " in bold face are to be interpreted as described in RFC 2119 . An implementation is not conformant if it fails to satisfy one or more of the "must" or "required" level requirements for the protocols it implements.
This document refers in several places to "community-specific" practices to which individual protocol implementations may conform. These practices are described in an accompanying Implementation Guidelines document.
The OAI framework is based on a client/server architecture using two groups of services: the data provider (for example; repositories) and the service provider (for example; a metadata harvester such as OAIster). The data provider services are generally embedded into the repository or open archive software and provide a mechanism to allow open access to the metadata held within the repository. Service providers make use of the OAI-PMH interfaces provided by the data providers to harvest the metadata to a central location. Using this aggregated metadata, the service provider can then offer value added services such as search and dissemination tools.
Subcribe on Youtube - IGNOU SERVICE
For PDF copy of Solved Assignment
WhatsApp Us - 9113311883(Paid)
0 Comments
Please do not enter any Spam link in the comment box