ADAM 5.7 Release Notes

ADAM version 5.7

LINKS


HIGHLIGHTS


  • Content modeling
    ADAM 5.7 introduces the content model, allowing you to configure content types. By default, the video, product and catalog content types are available now. The products and catalog content types will only be available if you also have Products installed.

    See the ADAM Administrator Guide > Content types in ADAM

  • Videos extended functionality
    The Videos functionality has been extended with a new ADAM Videos fields group, new time-related metadata, new details and (pre)view pages, giving the user considerably more options for (pre)viewing and working with Videos.

    See the ADAM Administrator Guide > UI Configuration in ADAM studios > Configuring the details page for the Video content type

    See the ADAM Administrator Guide > Fields > ADAM Video Fields

    See the ADAM Administrator Guide > Fields > Data type specific: Cue points

    See the ADAM Administrator Guide > Post-installation tasks > Install FFmpeg as media engine > Configuring video preview specification

  • ETL support extended
    It is now possible to do bulk uploading of record, classification and content type data into ADAM. ETL is, however, optimized to load product data. The uploading includes the update and creation of data only, as this is the most relevant need.
    The new ADAM ETL Service is built on top of the ADAM REST API. Users can use their ETL tool of choice to convert data from an external system, like a database or ERP system, to CSV files, which in turn can be loaded into ADAM.
    To further assist users in doing this, ADAM provides a number of templates for Pentaho, which are available in the ADAM Knowledge Base: https://support.adamsoftware.net/hc/enus/categories/201785966-Knowledge-Base.

    See the ADAM Administrator Guide > ETL for more information about the ETL possibilities in ADAM

  • Unique identifiers
    Unique identifiers are fields that only allow values that are unique throughout the ADAM database. These fields are ideal for storing identifying information, such as product Ids, reference numbers, etc. These fields can then be used to load records directly, just like using a record or classification ID to load. This allows you to not use a search expression, which might not return results immediately after an update.

    See the ADAM Administrator Guide > Fields > Unique Identifiers

  • REST API for Products
    The REST API now exposes the content type for records and classifications, and allows you to specify new content types. By default, the content types Record and Video are available. If the Products studio is installed and licensed, then the content types Product and Catalog are also available. This means that you can manage and create products and catalogs through the ADAM REST API.
    You can now also create product catalogs through the REST API. Updating categories to catalogs is not yet supported.
  • ADAM code no longer obfuscated
    The compiled source code of ADAM is no longer obfuscated.

NEW FEATURES


  • Text list fields can now be used in advanced search.

  • New command line tool to display file store and volume information

  • A new default media engine is available, based on ImageMagick, which allows for better conversions between color spaces or of transparent files.

    See ADAM Administrator Guide > Media Engines > Managing color profiles

  • SQL Server 2016 is now supported

    See ADAM Installation Guide > Prerequisites

  • Windows Server 2016 is now supported

    See ADAM Installation Guide > Prerequisites

  • You can now enable diacritic-insensitive searching for records and classifications

    See ADAM Administrator Guide > Enterprise search configuration > Enable diacritic-insensitive searching

  • 2 new field scopes are added: Record content type dependent and Classification content type dependent

    See ADAM Administrator Guide > Fields > Creating and modifying field definitions

  • There is a new Content modeling guide page where you can map content type dependent fields and file extensions to a specific content type

  • A new field group ADAM Video Fields is added

    See ADAM Administrator Guide > Fields > ADAM Video Fields

  • The new Cue points field type can now be created from the Create new field page in ADAM System. This field allows you to add time-based metadata to video and other multi-media assets.

    For more information see the ADAM Administrator Guide > Fields > Data type specific: Cue points

  • A set of default metadata fields are added to support video-related metadata. These fields are preconfigured with default values. Only a limited set of properties for those field definitions are editable.

    See ADAM Administrator Guide > Fields > ADAM Video Fields

  • Content types now have a label property in addition to the name. To search for content using the content type you can use the following searchable properties: Contenttype.Name, Contentype.Label and Contenttype - which is short for Contenttype.label.

  • There is a new Preview list view added to ADAM Assets.

    See ADAM Administrator Guide > UI Configuration on ADAM studios > Changing how records are displayed in ADAM Assets

  • There is a new details page for viewing video content added to ADAM Assets.

    See ADAM Administrator Guide > UI Configuration on ADAM studios > Configuring the Videos details page

  • There are 2 new attribute values available for the format attribute, which is part of the Reference Attributes. The format attribute now also allows for 'frequency' and 'bitrate' for Int64 numbers.

    See ADAM Administrator Guide > References > About references > Reference Attributes

  • It is now possible to assign 1 movie preview configuration to be the master preview. Only the master movie preview is shown on the dedicated details page for video content types.

    See ADAM Administrator Guide > Configuring the details page for the Video content type > Configuring the Video details page

  • It is now possible to define a start time from which point a movie preview should be created.

    See ADAM Administrator Guide > Configuring the details page for the Video content type > Configuring the Video details page

  • It is now possible to change the quality of the previews generated by the FFmpeg media engine.

    See ADAM Administrator Guide > Configuring the details page for the Video content type > Configuring the Video details page

  • The new .ffmpegStills setting allows you to configure different ways of generating stills when ingesting a video.

    See ADAM Administrator Guide > Post-installation tasks > Install FFmpeg as media engine

  • A new catalog action CreateMovieStills was added to all default video file types.

    See ADAM Administrator Guide > Post-installation tasks > Install FFmpeg as media engine

  • It is possible to change a poster image by promoting a still to a poster image.

    See ADAM Administrator Guide > Post-installation tasks > Install FFmpeg as media engine > Configuring video preview specifications

  • The Read movie info also reads chapter information stored in the metadata of the video container

BREAKING CHANGES


  • Windows Server 2008 and Windows Server 2008 R2 are no longer supported

  • 32 bit installers are no longer available

  • The content type name property is no longer included in the full-text index. Searching for content based on a content type is instead supported using search expressions.

  • The built-in LeadTools media engine has been replaced by ImageMagick

    See ADAM Administrator Guide > Media Engines > Managing default target profiles used by ImageMagick

  • A built-in media engines that is capable of creating a preview image for DCS files (an older file format used for the first Kodak digital cameras) is no longer available

  • The Combine method property for watermarks has been deprecated, and is replaced by the composition operator Over for all watermarks applied by the new ImageMagick media engine. This means that the watermark (for example: a transparent PNG file) is applied as-is on top of the source image file.
    If necessary, adjust your watermarks to make them compatible with this change.
    Watermarks that weren't applied by the LeadTools media engine aren't affected.

  • The option Max File Size / File Size when ordering or downloading a resized image is ignored if ImageMagick is assigned as resizing media engine for the file type of the original image.

    See The ADAM Administrator Guide > File Types > Creating and modifying file types for more information about assigning media engines to file types.

  • The compression factor for PNG preview and thumbnails cannot be specified for the new ImageMagick media engine.

  • It is now only possible to specify the maximum height of a movie preview. The height is translated to lines, meaning that for horizontal videos it will be the height, for vertical videos it will be the width

  • The catalog actions to generate file previews and thumbnails now have priority 998.

CHANGES


  • When opening a record with a parent-child record link field in view/read mode, any empty parent or child panels in the record link field are now hidden

  • In Advanced Search you can no longer select a language when searching on a single language field

  • When creating a new indexer, the default behavior is now set to Auto Detect: this means that indexed file types are automatically assigned to the appropriate content type, as defined on the Content type configuration guide page and in the .fileExtensiontoContenttypemapping setting. If you are upgrading from a previous ADAM version, you need to update this setting for your existing indexers as well.

  • The readmovieinfo catalog action is added to all out-of-the-box video file types. Reading the video information is an immediate action and will attempt to run when ingesting video files. The readmovieinfo catalog action now also reads the chapter information stored in the metadata of the video container.

  • The .iccProfiles setting is now also used to link color profiles with color spaces

    See ADAM Administrator Guide > Media Engines > Managing color profiles for more information.

  • The preview dialog in ADAM Assets can show fields and optionally classifications. Up to 3 important actions can be added to be directly available to the user. There is also an Add to selection feature from that Preview dialog.

    See the ADAM Administrator Guide > UI configuration in ADAM studios > Configuring the video details page for more information.

  • The default preview movie creation behavior was changed: ADAM now generates a low quality, full length preview video. The setting .ffmpegPreviews has been updated to reflect these changes, and if the setting was changed, the first preview in the list will be set as the master preview.

  • The preview image section in the .ffmpegPreviews setting was changed to Poster image. The generated image is shown in video players before the video is actively playing

  • In the APIs you can now load records and classifications using a unique field value without having to use a search expression.

  • Change tracking is now disabled for new installations. If you're upgrading from ADAM 5.5 or later and not using change tracking, it is recommended to disable it again.

    • When change tracking is disabled, the change tracking table is still used for synchronization to enterprise search. However, it is cleaned much more frequently to keep the table size to a minimum.

    • When change tracking is enabled, the cleaning is done taking into account the cleaning interval set in the setting .timeToKeepChangeHistory, and the fixed 5 days for Enterprise search synchronization. This means that records are deleted from the change tracking table if they are older then the interval set, and processed by the respective process, such as Publish/Subscribe.

      See the ADAM Administrator Guide > Publish and subscribe for more information

  • Enterprise search change tracking information is now automatically cleaned to save space on the database.

  • You can now load classifications by their name path in the APIs.

  • You can now create product catalogs through the REST API. Updating categories to catalogs is not supported yet.

  • It's now possible to immediately update the search index when creating or updating records and classifications thanks to the direct push mechanism in REST.

  • It is no longer required to manually call the /setup endpoint to initially configure REST

  • Indexers now use the .contentTypeConfiguration by default

    See ADAM Administrator Guide > Indexer > Creating and modifying indexers > Indexer properties & property groups

  • The translations for the following actions were changed:
    • the Download master file action was changed to Download
    • the Check-in master file action was changed to Check-in ...
    • the Check-out master file action was changed to Check-out ...
    • the Undo check-out master file action was changed to Undo check-out

FIXED BUGS


  • 7504
    Send as Attachment failed when switching to Ftp Resort Order and the file was not zipped

  • 7892, 8408, 9555
    The default sort order of a display was not used on initial page load of record-mosaic views

  • 8041, 9741
    There were differences in the way the classification tree was displayed when browsing assets and browsing during record edit

  • 9299, 9437, 9534, 9535, 9584, 9647, 9738
    When doing an advanced search for records using a multilingual field, an exception was thrown

  • 9343
    Field was not operator searchable when the default value was calculated using custom code

  • 9387
    When using the >=, >, <= and < operators when searching using a Date field, the search results were incorrect

  • 9433
    CreateWarehouseDatabase command uses incorrect credentials to connect to the ADAM server

  • 9597
    Syncing with the enterprise search index took too long when using custom storage providers

  • 9607
    When two processes were sending information on an item to Elasticsearch using immediate propagation, that could result in a concurrency issue and fail.

  • 9667
    Search using RecordHelper.GetFileVersionIds was broken since 5.5.x
  • 9621
    UpgradeServer command failed if the .registeredMaintenanceActions setting of the Default site was set to a custom value
  • 9645
    Uploading the same file multiple times via the REST service sometimes threw an exception
  • 9687
    On heavy load the Enterprise search Synchronization service could cause a memory overload and threw the exception "Data stream was not legible"
    Enterprise search Synchronization service logged an error "Cannot build FieldDto for FieldDefinition '{field_id}'. Fields of this FieldDefinition do not need indexing." for field definitions with their storage mode set to "None"
  • 9795
    EnableDatabase command failed on Azure
  • 9839
    In some situations a null pointer exception could occur while synchronizing records to Enterprise search.
  • 9891
    For the property ExporterSettings.ExportReadOnlyFields, the values from the read-only fields were not read correctly
  • 9847
    A large amount of simultaneous record updates could lead to the Synchronization service stopping.
  • 9914
    The UninstallStudio and UninstallWebService commands required the exact same path (incl. trailing backslash) as specified in the installation phase
  • 9916
    When the database and the sync service are running on different servers, in case of connectivity issues this leads to an error.
  • 9943
    The video metadata extraction for videoWidth was incorrect, it included also the height
  • 9981
    "Send as Attachment"
    failed when switched to ftpresortorder and file is not zipped
  • Text list field values were always shown in lower case in read/view mode
  • It wasn't possible to do an advanced search for records using the File > CreatedBy property
  • In view/read mode the text list field values were shown in an incorrect font
  • If you used an ampersand (&) in a text list field value it was replaced by its character code
  • When you wanted to upload a GIF file as watermark you got an error saying that this file format isn't supported, although it is.
  • The Preview Image dialog didn't correctly show very small images
  • Text List Fields are not rendered correctly in a manual EditRecord activity in Workflow
  • It was not possible to use special characters in some guide pages.
  • An unhandled exception was thrown after log-in, when a user had multiple browser windows open, the session expired and the user tried to interact with ADAM in a different window than the one in which the log-in was initially done.
  • The Mosaic widget did not handle custom search expressions in combination with the View more link
  • It was not possible to create synonym rules containing diacritics

KNOWN ISSUES


  • The import framework does not respect it when ExportReadOnlyFields is set to false in an export settings file. Exports using an exports settings file will always export read-only fields.

  • Partial pattern matching won't find a match if the pattern (and related patterned values) contain a hyphen.

  • For ETL:

    • Incorrect word 'delimeter' in the ETL schema validation: one of the attributes in the XSD schema that is used to validate values in the .etlSchemas setting is spelled incorrectly - "delimeter" instead of "delimiter"

    • Creating a record and linking it to one of the designated ADAM Products classifications causes an error: ADAM allows creating records that are not of the Product content type and linking them to any of the ADAM Products classifications, both via ETL and ADAM Assets. However, navigating to that record in ADAM Products will throw an exception.

    • There is no shortcut in the Start menu to run the ETL command line

DOCUMENTATION CHANGES


ADAM Administrator Guide

  • Installing iFilters as media engines: a new topic is available in the ADAM Administrator Guide on how to install and set up iFilters to extract text content from certain file formats during ingestion.

    See ADAM Administrator Guide > Post Installation Tasks > Install iFilters as Media Engine

  • Content modeling in ADAM
    New section on how ADAM now allows you to model content by offering you content types.

    See the ADAM Administrator Guide > Content types in ADAM

  • Configuration options for the Videos preview and details page
    As a result of the introduction of the video content type, you can now configure the details page and the preview for Videos

    See the ADAM Administrator Guide > UI Configuration in ADAM Studios > Configuring the video details page

 

Was this article helpful?

0 out of 0 found this helpful