| Table of Contents | ||||
|---|---|---|---|---|
|
Assets in the DAMS can be made publicly accessible through different endpoints:
...
- , a separate computer system providing a ‘view’ on select digital assets, with browsing and search functionality aimed at patrons. Content curators decide which assets can be made publicly available
- the HRDI platform
- as IIIF manifest-only, e.g. for use on the Primeros Libros de las Américas portal or in Spotlight
Upon publishing of an asset to the Collections Portal either endpoint, a subset of the asset's metadata is copied from the DAMS to the public access portal. In addition, the publishing software component applies some changes to the metadata, to create a more user-friendly display on the Collections Portalpublic endpoint.
An asset's components (image(s) and metadata) available on the Collections Portal published to any endpoint from the DAMS will remain in the version that is current at the time of publishing. Later changes to metadata and/or digital objects in the DAMS will not be carried over to any of the Collections Portal publishing endpoints until you un-publish and re-publish the asset.
The public URL for a published asset on the Collections portal follows this pattern: https://collections.lib.utexas.edu/catalog/<PID>
Public access
Publicly accessible content and metadata is available to anyone on the internet. It can for instance be shared, downloaded, copied and indexed by search engines or metadata aggregators. Per Policy, Content Curators have to make sure that assets and their metadata are intended and suitable for public access, given copyright status, privacy rules and other applicable standards and regulations.
| Note | ||
|---|---|---|
| ||
|
Content owners can decide between different options to make content and/or metadata available in the Collections Portal by selecting a value for "Rights - Restriction on Access" in the DAMS MODS input form or by assigning the respective value to the accessCondition[@type="restriction on access"] element in metadata for batch ingest.
| Note |
|---|
Currently only the values "Public access" and "Metadata only" are implemented for the publishing process. |
- Public Access: Allow the whole world see the object images and metadata for an asset
- Metadata Only: The Metadata is the only component of an asset that will be visible to the world
What is published?
...
Currently,
...
content stored with one of the following content models can be published to the Collections Portal: Large Image, Book, Issue, Audio, Video.
Large Image
The publishing software component uses a JPEG 2000 (JP2) derivative image that is automatically created from the OBJ datastream upon ingest. The JPEG 2000 derivative is made available to the Collections PortalLibraries' s IIIF image server, which for instance serves images to the embedded viewer on the Collections Portal asset landing pages.
A subset of the asset's metadata in the DAMS is copied to the search index of the Collections Portal. The publishing software component applies some changes to the metadata during the copying process, to create a more user-friendly display on the Collections Portal. The DAMS metadata remains unchanged by this process, however. Check the metadata technical documentation for a particular metadata element for more information on whether the element is copied to the Collections Portal and how the data is transformed in the process.
...
| Note |
|---|
Only book/issue-level assets can be published; it is not possible to separately publish individual pages of a book/issue. It is also not possible to store or publish descriptive metadata on the level of page assets associated with a book or issue. The DAMS allows to store OCR data and PDF representations for each page in a book/issue and in aggregated form for the entire book or issue. Neither The OCR data nor PDF versions are currently publishable currently cannot be published to the Collections Portal. |
...
A subset of the book/issue-level asset's metadata in the DAMS is copied to the search index of the Collections Portal. The publishing software component applies some changes to the metadata during the copying process, to create a more user-friendly display on the Collections Portal. The DAMS metadata remains unchanged by this process, however. Check the metadata technical documentation for a particular metadata element for more information on whether the element is copied to the Collections Portal and how the data is transformed in the process.
Public access
Publicly accessible content and metadata is available to anyone on the internet. It can for instance be shared, downloaded, copied and indexed by search engines or metadata aggregators. Per Policy, Content Curators have to make sure that assets and their metadata are intended and suitable for public access, given copyright status, privacy rules and other applicable standards and regulations.
Content owners can decide between different options to make content and/or metadata available in the Collections Portal by selecting a value for "Rights - Restriction on Access" in the DAMS MODS input form or by assigning the respective value to the accessCondition[@type="restriction on access"] element in metadata for batch ingest.
| Note |
|---|
Currently only the values "Public access" and "Metadata only" are implemented for the publishing process. |
...
If a PDF datastream is available at the Book/Issue level, you can publish this file to the Collections Portal (see instructions for manual publishing) as an additional download.
| Note |
|---|
Content Curators must consider the following aspects before deciding to make PDF derivatives available for download:
|
Audio
The publishing software component uses a derivative audio file that is either automatically created from the OBJ datastream upon ingest, or provided by the DAMS user. The derivative audio file is served through the AV player component embedded on the Collection Portal asset landing page.
| Note | ||
|---|---|---|
| ||
An Audio transcript is required for publishing: See Content models#AUDIOContentmodel for details. |
| Note | ||
|---|---|---|
| ||
By default, Audio content is published by making an MP3 derivative file available to the Portal's AV player component as a progressive download. The MP3 file can downloaded in full by members of the public with relative ease, with no technical hurdles to protect the content. Audio content can instead be published as streaming media, which adds a limited technical hurdle against a simple download of the complete audio file. If you prefer to deliver audio content as streaming media, you need to externally create an MP4 derivative and ingest it into a datastream labeled PROXY_MP4. Please submit a DAMS support ticket for details on this step. The DAMS and Collections Portal have no mechanism in place to enforce 'strict' Digital Rights Management for AV content, and there is no mechanism to add a watermark to content. |
A subset of the asset's metadata in the DAMS is copied to the search index of the Collections Portal. The publishing software component applies some changes to the metadata during the copying process, to create a more user-friendly display on the Collections Portal. The DAMS metadata remains unchanged by this process, however. Check the metadata technical documentation for a particular metadata element for more information on whether the element is copied to the Collections Portal and how the data is transformed in the process.
Video
The publishing software component uses a derivative video file that is automatically created from the OBJ datastream upon ingest. The derivative video file is served as streaming media through the AV player component embedded on the Collection Portal asset landing page.
| Note | ||
|---|---|---|
| ||
Video captions are required for publishing: See Content models#VIDEOContentmodel for details. |
| Note | ||
|---|---|---|
| ||
Video content is published as streaming media, which adds a limited technical hurdle against a simple download of the complete video file. The DAMS and Collections Portal have no mechanism in place to enforce 'strong' Digital Rights Management for AV content, and there is no mechanism to add a watermark to content. |
A subset of the asset's metadata in the DAMS is copied to the search index of the Collections Portal. The publishing software component applies some changes to the metadata during the copying process, to create a more user-friendly display on the Collections Portal. The DAMS metadata remains unchanged by this process, however. Check the metadata technical documentation for a particular metadata element for more information on whether the element is copied to the Collections Portal and how the data is transformed in the process.
Requirements for publishing assets
...
If the asset does not contain linguistic content, use "not applicable" (no capitalization).
Valid repository name
...
- Alexander Architectural Archives, University of Texas Libraries, The University of Texas at Austin
- Architecture and Planning Library, University of Texas Libraries, The University of Texas at Austin
- Architecture and Planning Library Special Collections, University of Texas Libraries, The University of Texas at Austin
- Benson Latin American Collection, LLILAS Benson Latin American Studies and Collections, The University of Texas at Austin
- Fine Arts Library, University of Texas Libraries, The University of Texas at Austin
- Human Rights Documentation Initiative
- Perry-Castañeda Library Maps, University of Texas Libraries, The University of Texas at Austin
- Primeros Libros
- Walter Geology Library, University of Texas Libraries, The University of Texas at Austin
- University of Texas Libraries, The University of Texas at Austin
- (HRDI partner institutions)
- (Primeros Libros partner institutions)
How to publish an asset
Manual publishing
- Navigate to the DAMS landing page for the asset you want to publish.
- Click on the "Manage" tab.
If the asset has a content model that allows for publishing, you will see a grey button sub-tab labeled "Publish". Click on the sub-tab link labeled "Publish".
If the asset is already in published status, the button will be labeled "Unpublish".Click on the button labeled "Publish".You will see a table of the available publishing endpoints and the publishing status, detailing whether an asset is available on a particular endpoint.
Select the radio button for the publishing action you want to perform.
Select additional datastreams you want to publish, for instance a video transcript, or a PDF derivative of a paged content asset.
Click the button labeled "Submit"
warning
A green message box will appear, saying that your publish request has been sent.
The publishing button's label will change from "Publish" to "Unpublish".
You will receive an email message with information about the status of your publish request.
The If you published to the Collections Portal, the asset will be accessible on the Collections Portal under the URL https:// collections.lib.utexas.edu/catalog/<PID>Possible status email loop!
DO NOT submit another publishing request until your previous publishing request has finished.
Depending on the size of the asset being published, the publication process can take several minutes, especially for paged content. Check the criteria listed above or under "Verifying publication".
Note You should receive a status notification approximately 15 minutes after pressing the "Publish"/"Unpublish" button. The notification contains either an error message or a confirmation that the publish request was processed successfully.
If you do not receive an email within ca. 15 minutes, please submit a trouble ticket to the DAMS managers.
...
In the DAMS, the publication status of an asset can be checked by navigating to the asset's landing page "Publish" page, accessible from the "Manage" tab (https://dams.lib.utexas.edu/islandora/object/<PID>/manage/publish). If the asset has been successfully published to the Collections Portal, the landing "Publish" page will show a small globe icon in the upper right corner. In addition, the label of the publishing button located on the "Manage" tab will change from "Publish" to "Unpublish"an asset's status as published on the publishing endpoint selected.
If you need to check the publication status of multiple assets in a subcollection, you can use a Python script to generate an asset status report. You can find the script under the following URL: https://github.austin.utexas.edu/mmh4428/dams_user_tools
...
- Navigate to the DAMS landing page for the asset you want to unpublish.
- Click on the "Manage" tab.
If the asset has a content model that allows for publishing, you will see a grey button sub-tab link labeled "Publish". - Click on the sub-tab link labeled "UnpublishPublish".
If the asset is already in unpublished status, the button will be labeled "Publish"You will see a table of the available publishing endpoints and the publishing status, detailing whether an asset is available on a particular endpoint. - Select the radio button for the unpublishing action you want to perform.
Click on the button labeled "UnpublishSubmit".
A green message box appears, saying that your request has been sent.
You will receive an email message with information about the status of your unpublish request.Note You should receive a status notification approximately 15 minutes after pressing the "PublishSubmit" /"Unpublish" button. The notification contains either an error message or a confirmation that the publish unpublish request was processed successfully. If you do not receive an email within ca. 15 minutes, please submit a trouble ticket to the DAMS managers.
...