This page describes similarities and key differences between DAMS1 and DAMS2
General concepts
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. This is functionally similar to datastreams in DAMS1.
Assets are still bundles of files: Similar to DAMS1, which bundled different types of datastreams under a Fedora object, DAMS2 assets Nodes are typically associated with different Media entities: the ‘main’ asset file, derivatives, OCR results, transcripts or captions (if applicable). Upon ingest, the DAMS software automatically creates certain types of derivatives.
User accounts
User accounts will be created upon request by a DAMS manager. You will find your credentials in Stache.
If you change your password in the DAMS interface, the Stache user credentials will not be updated automatically. Please contact a DAMS manager if you need to reset your password.
Content models
Audio
Allowed file extensions: mp3, wav, aac, m4a
A transcript is required for publishing audio assets with linguistic content
Ingesting an audio file will trigger creation of an MP3 derivative
Audio content published to the Collections Portal or the HRDI Portal will be streamed via the Wowza media server.
Binary
Avoid this content model
Allowed file extensions: txt, rtf, doc, docx, ppt, pptx, xls, xlsx, xml, pdf, odf, odg, odp, ods, odt, fodt, fods, fodp, fodg, key, numbers, pages, tiff, tif, jp2, jpf, zip
Ingesting files using this content model will not trigger derivative generation.
The content cannot be published.
Collection
Used to organize content into hierarchical groups.
Image
Newspaper
Parent content type for Publication Issue, represents the entire series
Page
Paged Content
Publication Issue
Video
Not in use
The following two content models are currently not available:
Compound Object
Digital Document
Metadata
Metadata is prepared in spreadsheet form. A transformation to XML will not be necessary anymore.
DAMS2 contains managed vocabularies ('taxonomies') for some pieces of metadata, to improve the uniformity of metadata across assets. Some of these are open ended, meaning they can be extended as needed during ingest.
During batch ingests, taxonomy terms must be created before the Node metadata that reference a term. When creating metadata, look up terms in the existing taxonomies and reuse terms as appropriate, making sure that the spelling matches exactly.