[OAI-general] System Architecture

Young,Jeff jyoung@oclc.org
Fri, 14 Feb 2003 11:34:35 -0500


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C2D446.F58CA11B
Content-Type: text/plain;
	charset="iso-8859-1"

Here's an idea for a simple service provider implementation.
 
Having harvested and aggregated from a number of OAI data providers into a
database, it should be fairly easy to implement an SRW/SRU service (
http://www.loc.gov/z3950/agency/zing/srw/
<http://www.loc.gov/z3950/agency/zing/srw/> ) to search/retrieve the data.
This would give you the power of Z39.50 with a simple HTTP GET or SOAP
interface rather than the troublesome traditional Z39.50 interface. The user
interface would amount to nothing more than HTML forms with the SRU server
as the action target. The responses would come back in XML (SOAP in the case
of SRW). It would be possible, though, to include an XSL stylesheet in the
response so that it can be rendered as HTML in a browser.
 
Here's an example (but which lacks an XSL stylesheet):
http://alcme.oclc.org/axis/SOAR/services/SearchRetrieveService?query=educati
on
<http://alcme.oclc.org/axis/SOAR/services/SearchRetrieveService?query=educat
ion&maximumRecords=1> &maximumRecords=1 
 
This solution would give you not only a simple HTML form-based user
interface, but also a web service interface that other services could
incorporate.
 
Just a thought.
 
Jeff
-----Original Message-----
From: Downes, Stephen [mailto:Stephen.Downes@nrc-cnrc.gc.ca]
Sent: Friday, February 14, 2003 9:59 AM
To: 'Young,Jeff'; oai-general@oaisrv.nsdl.cornell.edu
Subject: RE: [OAI-general] System Architecture


I am writing an article for The Technology Source on OAI. It would be useful
for me if I could find some instances of good implementations. The sort of
thing I would find most useful is the sort of thing that would be
appreciated by a more general audience. For example, while XTCat is a very
nice implementation, there doesn't seem to be any way to search for records.
Also, the casual visitor is going to have no idea what to out into the
'indentifier' field, say.
 
You can preview the article here - it's in draft form so please don't
circulate this too widely just yet.
http://ts.mivu.org/default.asp?show=article
<http://ts.mivu.org/default.asp?show=article&id=2005> &id=2005
 
Any examples would be most appreciated. Additionally, any suggestions from
the OAI community would greatly enhance the usefulness and accuracy of this
article. It will be published May 1, 2003.
 
-- Stephen
 
----------------------------------------------------------------------------
- 
Stephen Downes ~ Senior Researcher ~ National Research Council 
Moncton, New Brunswick, Canada 
http://www.downes.ca <http://www.downes.ca/>    stephen@downes.ca   
stephen.downes@nrc.ca   http://www.iit.nrc.ca/e-learning.html
<http://www.iit.nrc.ca/e-learning.html>  
Subscribe to my free daily newsletter featuring news and articles 
about online knowledge, learning, community 
http://www.downes.ca/cgi-bin/website/subscribe.cgi
<http://www.downes.ca/cgi-bin/website/subscribe.cgi>  
or read it at http://www.downes.ca/news/OLDaily.htm
<http://www.downes.ca/news/OLDaily.htm>  
----------------------------------------------------------------------------
- 
-----Original Message-----
From: Young,Jeff [mailto:jyoung@oclc.org]
Sent: Friday, February 14, 2003 10:38 AM
To: oai-general@oaisrv.nsdl.cornell.edu
Cc: 'Hatfield, Amy J'
Subject: RE: [OAI-general] System Architecture


Amy,
 
DSpace is a wonderful product, but OAI-compliance is a very small part of
what DSpace is about. If you merely want to add OAI capability to a system
that already exists, DSpace would be overkill and would probably make your
job much harder. Because DSpace is an fairly elaborate system, using it as a
model for your own architecture probably wouldn't be appropriate either.
 
OAI-compliance can most easily be achieved by downloading one of the OAI
implementations found on http://www.openarchives.org/tools/tools.html
<http://www.openarchives.org/tools/tools.html> . This page is a little
misleading, though, because many of the tools listed are much more than mere
implementations of the OAI protocol (e.g. DSpace).
 
I'm only familiar with two of the implementations that are available. If
you're most comfortable working in Perl, the VTOAI OAI-PMH2 PERL
implementation.seems to be popular
(http://www.dlib.vt.edu/projects/OAI/software/vtoai/vtoai.html
<http://www.dlib.vt.edu/projects/OAI/software/vtoai/vtoai.html> .) If you're
most comfortable using Java, I would suggest OAICat (
http://www.oclc.org/research/software/oai/cat.shtm
<http://www.oclc.org/research/software/oai/cat.shtm> ) which runs under a
J2EE-compliant servlet engine (such as Apache's Tomcat). I am the author of
the OAICat and would be glad to help you get it set up for your needs. BTW,
DSpace uses the OAICat implementation to provide its OAI repository
functionality.
 
OAICat can be customized to work with any database engine that supports a
Java API. Implementations are available for JDBC as well as a simple
file-based system. Other databases can be accommodated by implementing a set
of abstract Java classes. Implementations are also available for Newton and
the open-source Pears database engines which are used in OCLC's SiteSearch
product.
 
BTW, if you have an unusually large repository (or even if you don't) you
may even want to consider using the open-source Pears database (
http://www.oclc.org/research/software/pears/
<http://www.oclc.org/research/software/pears/> ). I use it for our XTCat
repository ( http://alcme.oclc.org/xtcat/ <http://alcme.oclc.org/xtcat/> )
which contains over 4.2 million records.
 
Hope this helps.
 
Jeff
-----Original Message-----
From: Hatfield, Amy J [mailto:ajhatfie@iupui.edu]
Sent: Friday, February 14, 2003 8:50 AM
To: oai-general@oaisrv.nsdl.cornell.edu
Subject: [OAI-general] System Architecture


Hello -
 
I am currently exploring our institution's ability to create an
institutional repository that is OAI compliant.  I feel I have a fair
understanding of the standards, functionality, etc. involved - and am
leaning toward DSpace as a model - but there is one aspect that I don't see
discussed very much...  system architecture!
 
I would be grateful if folks would share with me some architecture
configurations they have developed.  I am most interested in the storage
aspect.  I have looked at jukebox technology as a storage backend, but am
not sure about the retrieval aspect.  We also have a super computer with
lots of storage capacity - but it is not designed to handle small files, but
rather large datasets.  Any information you would like to share will be most
appreciated.
 
Feel free to respond directly to me if you would rather not post to the
list.
 
Kind regards,
Amy
 
Amy Jo Hatfield, Systems Librarian
Ruth Lilly Medical Library
Educational Technology
(317)278-8402
975 West Walnut Street
IB-100 Room 102A
Indianapolis, IN 46202-5121
 
 
 
 

------_=_NextPart_001_01C2D446.F58CA11B
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<META content=3D"Microsoft Word 10" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C2D406.0D8CF8B0" =
rel=3DFile-List><o:SmartTagType=20
name=3D"PostalCode"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"State"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"City"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"place"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"Street"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"address"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]--><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Comic Sans MS;
}
P.MsoNormal {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Comic Sans MS"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: Arial
}
LI.MsoNormal {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Comic Sans MS"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: Arial
}
DIV.MsoNormal {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Comic Sans MS"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: Arial
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-bidi-font-family: Arial; =
mso-style-type: personal-compose; mso-style-noshow: yes; =
mso-ansi-font-size: 10.0pt; mso-bidi-font-size: 10.0pt; =
mso-ascii-font-family: Arial; mso-hansi-font-family: Arial
}
SPAN.SpellE {
	mso-style-name: ""; mso-spl-e: yes
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]--></HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dpurple =
link=3Dblue>
<DIV><SPAN class=3D731481216-14022003><FONT color=3D#0000ff =
size=3D2>Here's an idea=20
for a simple service provider implementation.</FONT></SPAN></DIV>
<DIV><SPAN class=3D731481216-14022003><FONT color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D731481216-14022003><FONT color=3D#0000ff =
size=3D2>Having harvested=20
and aggregated from a number of OAI data providers into a database, it =
should be=20
fairly easy to implement an SRW/SRU service (<A=20
href=3D"http://www.loc.gov/z3950/agency/zing/srw/">http://www.loc.gov/z3=
950/agency/zing/srw/</A>)=20
to search/retrieve the data. This would give you the power of Z39.50 =
with&nbsp;a=20
simple HTTP GET or SOAP interface rather&nbsp;than the troublesome =
traditional=20
Z39.50 interface. The user interface would amount to nothing more than =
HTML=20
forms with the SRU server as the action target. The responses would =
come back in=20
XML (SOAP in the case of SRW). It would be possible, though, to include =
an XSL=20
stylesheet in the response so that it can be&nbsp;rendered as HTML in a =

browser.</FONT></SPAN></DIV>
<DIV><SPAN class=3D731481216-14022003><FONT color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D731481216-14022003><FONT color=3D#0000ff =
size=3D2>Here's an example=20
(but which lacks an XSL stylesheet): </FONT><FONT color=3D#0000ff><FONT =
size=3D2><A=20
href=3D"http://alcme.oclc.org/axis/SOAR/services/SearchRetrieveService?q=
uery=3Deducation&amp;maximumRecords=3D1">http://alcme.oclc.org/axis/SOAR=
/services/SearchRetrieveService?query=3Deducation&amp;maximumRecords=3D1=
</A><SPAN=20
class=3D731481216-14022003> </SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D731481216-14022003><FONT color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D731481216-14022003><FONT color=3D#0000ff =
size=3D2>This solution=20
would give you not only a simple HTML form-based user interface, but =
also a web=20
service interface that other services could =
incorporate.</FONT></SPAN></DIV>
<DIV><SPAN class=3D731481216-14022003><FONT color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D731481216-14022003><FONT color=3D#0000ff =
size=3D2>Just a=20
thought.</FONT></SPAN></DIV>
<DIV><SPAN class=3D731481216-14022003><FONT color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D731481216-14022003><FONT color=3D#0000ff=20
size=3D2>Jeff</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Downes, Stephen=20
  [mailto:Stephen.Downes@nrc-cnrc.gc.ca]<BR><B>Sent:</B> Friday, =
February 14,=20
  2003 9:59 AM<BR><B>To:</B> 'Young,Jeff';=20
  oai-general@oaisrv.nsdl.cornell.edu<BR><B>Subject:</B> RE: =
[OAI-general]=20
  System Architecture<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D299185214-14022003>I am=20
  writing an article for The Technology Source on OAI. It would be =
useful for me=20
  if I could find some instances of good implementations. The sort of =
thing I=20
  would find most useful is the sort of thing that would be appreciated =
by a=20
  more general audience. For example, while XTCat is a very nice =
implementation,=20
  there doesn't seem to be any way to search for records. Also, the =
casual=20
  visitor is going to have no idea what to out into the 'indentifier' =
field,=20
  say.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D299185214-14022003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D299185214-14022003>You=20
  can preview the article here - it's in draft form so please don't =
circulate=20
  this too widely just yet. <A=20
  =
href=3D"http://ts.mivu.org/default.asp?show=3Darticle&amp;id=3D2005">htt=
p://ts.mivu.org/default.asp?show=3Darticle&amp;id=3D2005</A></SPAN></FON=
T></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D299185214-14022003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D299185214-14022003>Any=20
  examples would be most appreciated. Additionally, any suggestions =
from the OAI=20
  community would greatly enhance the usefulness and accuracy of this =
article.=20
  It will be published May 1, 2003.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D299185214-14022003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D299185214-14022003>--=20
  Stephen</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
  <P><FONT face=3D"Courier New"=20
  =
size=3D2>---------------------------------------------------------------=
--------------</FONT>=20
  <BR><FONT face=3D"Courier New" size=3D2>Stephen Downes ~ Senior =
Researcher ~=20
  National Research Council</FONT> <BR><FONT face=3D"Courier New" =
size=3D2>Moncton,=20
  New Brunswick, Canada</FONT> </P>
  <P><FONT face=3D"Courier New" size=3D2><A =
href=3D"http://www.downes.ca/"=20
  target=3D_blank>http://www.downes.ca</A>&nbsp;&nbsp;=20
  stephen@downes.ca&nbsp;&nbsp; </FONT><BR><FONT face=3D"Courier New"=20
  size=3D2>stephen.downes@nrc.ca&nbsp;&nbsp; <A=20
  href=3D"http://www.iit.nrc.ca/e-learning.html"=20
  target=3D_blank>http://www.iit.nrc.ca/e-learning.html</A></FONT> </P>
  <P><FONT face=3D"Courier New" size=3D2>Subscribe to my free daily =
newsletter=20
  featuring news and articles </FONT><BR><FONT face=3D"Courier New" =
size=3D2>about=20
  online knowledge, learning, community</FONT> <BR><FONT =
face=3D"Courier New"=20
  size=3D2><A =
href=3D"http://www.downes.ca/cgi-bin/website/subscribe.cgi"=20
  =
target=3D_blank>http://www.downes.ca/cgi-bin/website/subscribe.cgi</A>=20
  </FONT><BR><FONT face=3D"Courier New" size=3D2>or read it at <A=20
  href=3D"http://www.downes.ca/news/OLDaily.htm"=20
  target=3D_blank>http://www.downes.ca/news/OLDaily.htm</A></FONT> =
<BR><FONT=20
  face=3D"Courier New"=20
  =
size=3D2>---------------------------------------------------------------=
--------------</FONT>=20
  </P>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> Young,Jeff=20
    [mailto:jyoung@oclc.org]<BR><B>Sent:</B> Friday, February 14, 2003 =
10:38=20
    AM<BR><B>To:</B> oai-general@oaisrv.nsdl.cornell.edu<BR><B>Cc:</B>=20
    'Hatfield, Amy J'<BR><B>Subject:</B> RE: [OAI-general] System=20
    Architecture<BR><BR></DIV></FONT>
    <DIV><SPAN class=3D235290214-14022003><FONT color=3D#0000ff=20
    size=3D2>Amy,</FONT></SPAN></DIV>
    <DIV><SPAN class=3D235290214-14022003><FONT color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D235290214-14022003><FONT color=3D#0000ff =
size=3D2>DSpace is a=20
    wonderful product, but OAI-compliance is a very small part of what =
DSpace is=20
    about. If you merely want to add OAI capability to a system that =
already=20
    exists, DSpace would be overkill and would probably make your job =
much=20
    harder. Because DSpace is an fairly elaborate system, using it as a =
model=20
    for your own architecture probably wouldn't be appropriate=20
    either.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D235290214-14022003><FONT color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D235290214-14022003><FONT color=3D#0000ff=20
    size=3D2>OAI-compliance can most easily be achieved by downloading =
one of the=20
    OAI implementations found on <A=20
    =
href=3D"http://www.openarchives.org/tools/tools.html">http://www.openarc=
hives.org/tools/tools.html</A>.=20
    This page is a little misleading, though,&nbsp;because many of the =
tools=20
    listed are much more than mere implementations of the OAI protocol =
(e.g.=20
    DSpace).</FONT></SPAN></DIV>
    <DIV><SPAN class=3D235290214-14022003><FONT color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D235290214-14022003><FONT color=3D#0000ff =
size=3D2>I'm only=20
    familiar with two of the implementations that are available. If =
you're most=20
    comfortable working in Perl, the VTOAI OAI-PMH2 PERL =
implementation.seems to=20
    be popular&nbsp;<A=20
    href=3D"http://www.dlib.vt.edu/projects/OAI/software/vtoai/vtoai.htm=
l">(http://www.dlib.vt.edu/projects/OAI/software/vtoai/vtoai.html</A>.) =

    If you're most comfortable using Java, I would suggest =
OAICat&nbsp;(<A=20
    =
href=3D"http://www.oclc.org/research/software/oai/cat.shtm">http://www.o=
clc.org/research/software/oai/cat.shtm</A>)=20
    which&nbsp;runs under a J2EE-compliant servlet engine (such as =
Apache's=20
    Tomcat).&nbsp;I am the author of the OAICat and would be glad to =
help you=20
    get it set up for your needs. BTW, DSpace uses the OAICat =
implementation to=20
    provide its OAI repository functionality.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D235290214-14022003><FONT color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D235290214-14022003><FONT color=3D#0000ff =
size=3D2>OAICat can be=20
    customized to work with any database engine that supports a Java =
API.=20
    Implementations are available for JDBC as well as a simple =
file-based=20
    system. Other databases can be accommodated by implementing a set =
of=20
    abstract Java classes. Implementations are also available for =
Newton and the=20
    open-source Pears database engines which are used in OCLC's =
SiteSearch=20
    product.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D235290214-14022003><FONT color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D235290214-14022003><FONT color=3D#0000ff =
size=3D2>BTW, if you=20
    have an unusually large repository (or even if you don't) you may =
even want=20
    to consider using the open-source Pears database&nbsp;(<A=20
    =
href=3D"http://www.oclc.org/research/software/pears/">http://www.oclc.or=
g/research/software/pears/</A>).=20
    I use it for our XTCat repository (<A=20
    =
href=3D"http://alcme.oclc.org/xtcat/">http://alcme.oclc.org/xtcat/</A>) =
which=20
    contains over 4.2 million records.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D235290214-14022003><FONT color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D235290214-14022003><FONT color=3D#0000ff =
size=3D2>Hope this=20
    helps.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D235290214-14022003><FONT color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D235290214-14022003><FONT color=3D#0000ff=20
    size=3D2>Jeff</FONT></SPAN></DIV>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
      size=3D2>-----Original Message-----<BR><B>From:</B> Hatfield, Amy =
J=20
      [mailto:ajhatfie@iupui.edu]<BR><B>Sent:</B> Friday, February 14, =
2003 8:50=20
      AM<BR><B>To:</B> =
oai-general@oaisrv.nsdl.cornell.edu<BR><B>Subject:</B>=20
      [OAI-general] System Architecture<BR><BR></FONT></DIV>
      <DIV class=3DSection1>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hello=20
      -<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I am currently =
exploring our=20
      institution's ability to create an institutional repository that =
is OAI=20
      compliant.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>I feel =
I have a=20
      fair understanding of the standards, functionality, etc. involved =
- and am=20
      leaning toward DSpace as a model - but there is one aspect that I =
don't=20
      see discussed very much...<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
      </SPAN>system architecture!<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I would be grateful =
if folks=20
      would share with me some architecture configurations they have=20
      developed.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>I am =
most=20
      interested in the storage aspect.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
      </SPAN>I have looked at jukebox technology as a storage backend, =
but am=20
      not sure about the retrieval aspect.<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
      </SPAN>We also have a super computer with lots of storage =
capacity - but=20
      it is not designed to handle small files, but rather large =
datasets.<SPAN=20
      style=3D"mso-spacerun: yes">&nbsp; </SPAN>Any information you =
would like to=20
      share will be most appreciated.<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Feel free to =
respond directly=20
      to me if you would rather not post to the=20
      list.<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Kind=20
      regards,<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Amy<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3D"Comic Sans MS" size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; mso-no-proof: yes">Amy Jo =
Hatfield,&nbsp;Systems=20
      Librarian<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3D"Comic Sans MS" size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; mso-no-proof: yes">Ruth Lilly Medical=20
      Library<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3D"Comic Sans MS" size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; mso-no-proof: yes">Educational=20
      Technology<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3D"Comic Sans MS" size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; mso-no-proof: =
yes">(317)278-8402<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><st1:Street><st1:address><FONT face=3D"Comic =
Sans MS"=20
      size=3D2><SPAN style=3D"FONT-SIZE: 10pt; mso-no-proof: yes">975 =
West Walnut=20
      Street</SPAN></FONT></st1:address></st1:Street><SPAN=20
      style=3D"mso-no-proof: yes"><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Comic Sans MS" size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; mso-no-proof: yes">IB-100 Room=20
      102A<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><st1:place><st1:City><FONT face=3D"Comic =
Sans MS"=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; mso-no-proof: =
yes">Indianapolis</SPAN></FONT></st1:City><SPAN=20
      style=3D"mso-no-proof: yes">, </SPAN><st1:State><SPAN=20
      style=3D"mso-no-proof: yes">IN</SPAN></st1:State><SPAN=20
      style=3D"mso-no-proof: yes"> </SPAN><st1:PostalCode><SPAN=20
      style=3D"mso-no-proof: =
yes">46202-5121</SPAN></st1:PostalCode></st1:place><SPAN=20
      style=3D"mso-no-proof: yes"><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Comic Sans MS" size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; mso-no-proof: =
yes">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3D"Comic Sans MS" size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; mso-no-proof: =
yes">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3D"Comic Sans MS" size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; mso-no-proof: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></P>
      <P class=3DMsoNormal><FONT face=3D"Comic Sans MS" size=3D2><SPAN=20
      style=3D"FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BLOCKQUOTE=
></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2D446.F58CA11B--