Chapter 1. Important CONTENTdm® concepts

Table of Contents

Architecture
Objects and collections
Persistence & retrieval
Authentication
Web templates
Administration module
APIs & custom development

CONTENTdm® could be thought of as consisting of two main "facets": the "librarian" side, consisting of metadata authoring; and the "public" side, consisting of the web templates and the infastructure that drives them. dmBridge has nothing to do with the former, but a prerequisite of making sense of dmBridge is understanding the basics of the latter.

[Note]Note

This information has been accumulated from personal experience and is not authoritative. For definitive information about CONTENTdm®, contact OCLC.

Architecture

The architecture of CONTENTdm® has changed somewhat from version 5 to 6. Most notable has been the addition of a separate "website" component (Figure 1.1, “High-level architecture of CONTENTdm® 5.x”, Figure 1.2, “High-level architecture of CONTENTdm® 6.x”).

Figure 1.1. High-level architecture of CONTENTdm® 5.x

High-level architecture of CONTENTdm 5.x
[Note]Note

The separate web servers indicate components that can, but do not have to, run on separate web servers. dmBridge is grayed-out to indicate that it is optional.


Figure 1.2. High-level architecture of CONTENTdm® 6.x

High-level architecture of CONTENTdm 6.x
[Note]Note

The separate web servers indicate components that can, but do not have to, run on separate web servers. dmBridge is grayed-out to indicate that it is optional.