Collection/Group Databases
- Current version uses a relational database called dlxs
- Underlying format can be CSV, MySQL, Oracle. Logical format is
handled through Perl DBI .
- managed through a CGI program called the Collection
Manager (collmgr)
- Collection Database Schema
- Collection table to hold fields common to all collections
classes
- Class tables to hold fields that are specific to each class
- Backup tables, version table
- Groups Database
- A group of collections (for collection coordinators to logically
group collections for searching)
- Other information required by the middleware that is kept in databases
- Parts of the dlxs database:
- Pageview (for which we recommend against CSV because of functionality,
performance, scalability)
- Portfolios (BookBagDB table)
- These are databases, but are not part of the dlxs database
as such; temporary
- Sessions, which hold search history, and other collection/group
information needed during the running of the CGI program. In
TextClass and FindaidClass, sessions also hold bookbag information.
In ImageClass, portfolios are held in a separate MySQL table.
- Middleware use of databases
- For example: CioFactory object compares requested collections and
groups, authorized collections (see AUTHZD_COLL) and groups
- See the DLXS
documentation for more information on the databases
- Database maintenance
- dbconv:
one time program to convert DLXS users' colldb's (from any release
prior to #8) to a database (either CSV or MySQL) for subsequent
versions.
- dbmove:
program to convert from CSV to MySQL versions of the same database
structure (We at DLPS will also use this to release CSV versions
of new database structures as time goes by)
- collmgr (Collection Manager)
- upgrade_1_2, upgrade_2_3 and upgrade_3_4 and
(most recently) upgrade_4_5 :
for moving database information (from DLXS version 8 to version 9,
from version 9 to version 10, from version 10 to version 11, and
from version 11 to version 12, respectively)