...
Every asset is a Node: The new version of the DAMS is based on Drupal, a web content management system. Content in Drupal is referred to as a “Node”. Every asset in the DAMS, including collections, serials, books/issues, pages, is represented by a Node, which has a unique ID. The Node stores the metadata which describes an asset.
Assets in DAMS2 technically have two IDs: a running-number node ID, which is unique only within the context of the current DAMS2 instance, and a UUID, which is generally unique. Users will typically interact with assets through the DAMS2 GUI using the Node ID.
DAMS1 PIDs were retained during the migration, in order for Collections Portal URLs to remain stable. New content that is published to the Collections Portal will also receive a UUID-based URL.
Paged Content is modeled similar to DAMS1 by creating a ‘sparse’ Node for each page and associating the page Nodes with a book/issue-level asset Node.
Every file is represented by a Media entity: Media entities in Drupal allow to associate files with (technical) metadata about a file. When adding files to the DAMS, they are associated with a Node that represents an asset.
Media entities are functionally similar to datastreams in DAMS1.
Similar to the different types of datastreams in DAMS1, DAMS2 distinguishes different types of Media entity (representing for instance the main asset file, derivatives/service files, thumbnails, transcripts, etc.).
Assets are bundles of files: Similar to DAMS1, which bundled different types of datastreams under a Fedora object/PID, asset Nodes in DAMS2 are typically associated with different Media entities: the ‘main’ asset file, derivatives, OCR results, transcripts or captions (if applicable). It depends on the Content Model of a particular asset, which types of Media will be available.
Upon ingest, the DAMS software automatically creates certain types of derivatives.
Media entities other than the ‘main’ file entity will be automatically named.
...