OAI presentation location change

• To: <java-dev@xxxxxxxxxxxxxxxx>, <thredds@xxxxxxxxxxxxxxxx>
• Subject: OAI presentation location change
• From: John Weatherley <jweather@xxxxxxxx>
• Date: Wed, 28 Nov 2001 13:22:57 -0700 (MST)

The presentation has been moved to:

The Unidata Conference Room (FL4 room 1318).
Still 9:30 AM, Thursday November 29.


For those who requested driving directions:

Same building as before, different room.

The address is 3300 Mitchell ln (UCAR building FL4). From the intersection
of 47th st and Valmont, head north on 47th aprox 1/2 mile to Mitchell ln.
Our building is on the SE corner of Mitchell and 47th.  Go right at
Mitchell ln and then take the first right into the parking lot. The
entrance to the building is on the south side.

Once inside head down the east hall to the Unidata Conference Room (RM
1318) on your left.




Original announcement:

OAI Protocol for Metadata Harvesting: A Java Implementation.

Presentation:
9:30 AM, Thursday November 29.
DPC Conference Room (FL4 RM 3134) (location has changed, see above)

This presentation will provide a software architecture overview of the
DPC's OAI metadata harvesting Java implementation.

The Open Archives Initiative (OAI) protocol for metadata harvesting is an
interoperability standard that provides a convenient way to share metadata
among library repositories.  The OAI standard was developed to provide a
simple method to support the streaming of metadata from one repository to
another, and ultimately to a provider of user services such as searching,
browsing or annotation.

The OAI protocol subscribes to a solution for interoperability known as
metadata harvesting.  The framework establishes a notion of a Service
Provider - a central entity that collects or "harvests" metadata from
repositories and then provides services over the metadata such as
searching, browsing, indexing and categorization. The individual
repositories that produce metadata are known as Data Providers.  The
protocol is simple in that it allows for the transport of metadata from
one to another, but does not attempt to include more complex features
within the protocol itself such as searching.  As such it can be
implemented quickly, without the need for high overhead, making it easy
for repositories to become Data Providers while leaving searching,
browsing and other high-level functions to be handled by the Service
Provider.  Because DLESE is composed of many diverse partners both large
and small, OAI provides an excellent solution for library
interoperability.