This page describes similarities and key differences between DAMS1 and DAMS2
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 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.