[OAI-implementers] Migrating from 1.1 to 2.0
Jose Blanco
blancoj@umich.edu
Tue, 30 Jul 2002 11:03:03 -0400
This is a multi-part message in MIME format.
------=_NextPart_000_002F_01C237B8.ACF80240
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I am in the process of registering my cgi (broker, from the University =
of Michigan) to be compliant with 2.0. Presently broker is compliant =
with 1.1, once I register it will no longer be compliant with 1.1, and =
therefore those harvesters accessing it thinking it is 1.1 will get =
errors. Is there a way to unregister it as 1.1 and then register it as =
2.0? What is the suggested procedure for this? Should I keep broker =
1.1 compliant and register a new broker, say broker20 to be 2.0 =
compliant?
Any thoughts?
Jose
------=_NextPart_000_002F_01C237B8.ACF80240
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>I am in the process of registering =
my cgi=20
(broker, from the University of Michigan) to be compliant with =
2.0. =20
Presently broker is compliant with 1.1, once I register it will no =
longer be=20
compliant with 1.1, and therefore those harvesters accessing it thinking =
it is=20
1.1 will get errors. Is there a way to unregister it as 1.1 and =
then=20
register it as 2.0? What is the suggested procedure for =
this? =20
Should I keep broker 1.1 compliant and register a new broker, say =
broker20 to be=20
2.0 compliant?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Any thoughts?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial =
size=3D2>Jose</FONT></DIV></FONT></DIV></BODY></HTML>
------=_NextPart_000_002F_01C237B8.ACF80240--