Making Library Databases

From Staffwiki

(Difference between revisions)
Jump to: navigation, search
(New page: === Library Databases on the CSU Library Web Site === Databases are produced from access metadata maintained in mySQL on the web server. The database can be ac...)
m (Library Databases on the CSU Library Web Site)
Line 3: Line 3:
Databases are produced from access metadata maintained in [[http://www.mysql.org | mySQL]] on the web server.
Databases are produced from access metadata maintained in [[http://www.mysql.org | mySQL]] on the web server.
-
The database can be accessed from on campus sites using [[http;//www.webmin.org | webmin]].  The LISTS Director and Digital Initiatives Coordinator share the access information
+
The database can be accessed from on campus sites using [[http;//http://sourceforge.net/projects/webadmin/ | webmin]].  The LISTS Director and Digital Initiatives Coordinator share the access information
The database is: librarydatabases
The database is: librarydatabases

Revision as of 22:17, 22 November 2008

Library Databases on the CSU Library Web Site

Databases are produced from access metadata maintained in [| mySQL] on the web server.

The database can be accessed from on campus sites using webmin. The LISTS Director and Digital Initiatives Coordinator share the access information

The database is: librarydatabases The tables are: linkage,subjects,types

The name in linkage is a key to finding multiple records for subjects and/or types so that multiple instances of other fields can be displayed. This allows one database (via its name) to belong to more than one subject, e.g. psychology, and biology. The same goes for types, which is little used.

The records in the database must be maintained frequently. When changed, all pages on the web site which can access the changed database will be updated when written. This supports alphabetical and by-subject listing and collections of databases.

The scripts detect the "on campusness" of the user agent (browser), and add the bluestem proxy information and program reference to the link address so that a seamless connection will be made from on- or off-campus. The databases are IP-authenticated.

The bluestem server prompts for membership in the campus community (staff, faculty, students) to allow access to its passed URL. The user need authenticate only one per browser session.

[| PHP] and [[| Python] scripts can access these data and produce descriptions and/or links on the cgi interface of the web server. The ezProxy.cfg file is also produced from this database by running the bluestem.py script from the command line and writing the configuration to standard output as in the following.

log in to the web server attach to /home/webs/test/eresources type python bluestem.py > ezproxy.cfg

Send the file to the setup area on the bluestem server in ITD. A daemon there will awaken periodically, move the configuration file to the usage area, and restart the exproxy server to re-read the configuration file for changed directives.

Personal tools