Compare Picturepark Content Systems

Enabling to group fields into purpose-specific layers which can be asssigned to content for tagging and exploring only those metadata values that are relevant for the particular content and its lifecycle.
Read more here

Associations between items that provide context to content and metadata, and the relationship between items. This provides better insights and search results since items are found via associated items too.
Read more here.

Via categories that provide tags for fields and feautre a strictly hierarchical relationship.

Via lists which can be parent-child related for schema propagation. List items can be related graph-alike with each others with support for circular references, and more.

Lists which have a schema and can store attributes for each list item with the possibility to semantically related lists and their items. This enables to build and maintain powerfull data architectures, and again provide better context and search results.

Flexible content type definitions that enable to define e.g. landing pages, press kits, historic milestones etc. and publish these headlessly.

Conversion of various file types such as images, audio, video, documents etc. into previews and other output formats.

In-built visual conversion and cropping tool for images.

Basic format conversion for images and video with resizing of shared or embedded images available via API. Short-term roadmap includes 3rd party integrations into image and video optimization systems.

Batch editing large amounts of content and metadata using in-built tools and rountripping via Excel spreadsheets.

Model and manage content in the Content Platform and published via API/SDK across your channels the way it is needed.

Content Delivery Networks can be used for fast and reliable global content delivery with fastly being currently integrated.

Interactive sites that integrate into existing websites or that can serve as standalone content portals such as content or press portals, product finders, and similar. Read more here

SDKs and sample code available for full customization within a short period of time.

Tagging images and videos based on visual recognition technology or tagging files with related product records via automatically recognized patterns in the file name or XMP metadata.

Optional matching with an existing (or provided) controlled vocabulary

Reading XMP, EXIF and other embedded metadata from files. Write back into files not available yet but planned for mid-term roadmap.

Out-of-the box connectors to other systems. See the Connectors overview page for details wrt. availability and types of connectors.

Limited availability of out-of-the box connectors for early releases. Possibility to build purpose specific ones via API/SDK and baseds on a growing list of blueprint apps, connectors and microsites which are all open sourced.

On level of single digital assets, single tags/categories and single fields.

On level of single content items, single lists (multiple list items) and metadata layers (multiple fields)

Permissions on content can be defined with permnission sets which feature an additive and/or exclusive logic for flexible permission modelling, e.g. for llife-cycles, embargo dates or archiving.

Users can own content and other entities, and transfer ownership to other users.

Tenants (or groups of users) can be separated within a single system so they cannot access content, metadata and users of other tenants within the same system.

No full multi-tenancy for certain functions that expose user data for administrative roles such as managers of system users.

Users are managed in roles which are permitted on content, metadata and system functions. Additionally, collections can be access-permitted via secure tokens.

Support for ADFS, Azure AD and LDAP.

Based on IdentityServer. Federated authentication possible via API. Support for ID management systems and protocols such as SAML on short-term roadmap.

Collecting user activitiy statistics on various entities. Statistics currently not exposed via API endpoint or UI but on mid-term roadmap.

System was designed with the API being the primary means for accessing and processing content. All aspects of the system are available via API which is based on modern technologies and backed with SDKs.

SDKs and sample code provided for free under MIT license.

Microservice architecture enabling certified developers to hook into a livestream of events, process document change history etc. and tightly or loosely integrate.

Clustering of services for load-balancing and fail-over resulting in faster processing and higher availability.

Available for Core application and rendering services.

Available for all system services with services built to be as “self healing” as possible when outages occur.

Support for small screen and touch-controlled mobile devices and tablets.

Support for mobile devices and tablets only for the WorldPort UI.

At the moment limited support for small-screen mobile devices in certain areas.