|Rob working on
slide re: details of OCW Object Model mapping onto DSpace object model
publication. Highly normalized. Course
Resource (single file,
it. (This is a Good Thing.)
digital archive. Hierarchical model,
with ability to support cross-mappings, but at the leaf Bitstream, the
hierarchy ends and all bitstreams are siblings, despite whatever complex
hierarchical relationship they may have had in the source system (e.g. a
discussion: "Bundle" can be used somewhat akin to METS fileGrp @USE
notion. In practice, most everything goes into a single Bundle named
"Content." Other bundles for
metadata, for licenses. You could also
use for Thumbnails and similar purposes.)
|Bottom line: the
OCW course website's files, all of them, flow into one tall stack of sibling
Bitstreams in the DSpace Item.
to the rendering of the website as though the files were re-distributed back
out to a set of directories and sub-directories to be able to be the website
once more, as viewed from DSpace.
|Note that this
calls for relative paths (e.g. "../../") in the source website
pages (as would be true of any approach to making a website portable).