[WEB4LIB] Re: MS-Access database - for archives

[Karen Harker]

I've been trying to find the same thing out.  I did create one, but it seemed so complex that I was worried about its scalability...would it break-down under heavy load?  I was somehow (can't remember how) put in contact with a gentleman in Houston who created an Access system for the University of Texas, Houston archives.  He sent me the database structure so I could compare it with what I've developed.

Interestingly, our Archives Team has recently decided against a separate database, given that the Library will be purchasing a "digital library solution" package (either EnCompass or MetaLib) for much broader purposes, but it will also be able to handle our archives collection as an XML "database".  So we have set our Access/SQL Server plans aside and will concentrate on learning EAD.




Karen R. Harker, MLS
UT Southwestern Medical Library
5323 Harry Hines Blvd.
Dallas, TX  75390-9049
214-648-1698
http://www.swmed.edu/library/

>>> Craighton Hippenhammer <CHHammer at olivet.edu> 8/23/01 11:01:21 AM >>>
Has anyone created an MS-Access database template for archives they'd be willing to share?



----- Original Message -----
From: "Glynis Andersson" <gandersson at bctf.bc.ca>
To: "Multiple recipients of list" <web4lib at webjunction.org>
Sent: Wednesday, August 22, 2001 3:11 PM
Subject: [WEB4LIB] MS-Access database


> Tony New asked about a MS-Access template for inventory. I'm wondering
> about an MS-Access template for tracking web resources. I'm particularly
> interested in any MS-Access databases of this type that have been used in
> conjunction with cold fusion to create a web-based dynamic database. A
> database-driven web page on "Resources by subject" is my final goal.
>
> Thanks.
> B.C. Teachers' Federation
> http://www.bctf.bc.ca 
>


Craighton Hippenhammer
Information Technology Librarian
Olivet Nazarene University
chhammer at olivet.edu



*********************************************************************
Due to deletion of content types excluded from this list by policy,
this multipart message was reduced to a single part, and from there
to a plain text message.
*********************************************************************