Compare Picturepark Content Systems

Primary use cases

Key features

Connect, Manage and route any type of content, be it file-based, “fileless” or remote content
Create fileless content that is strictly-structured
Manage content using semantic relationships, multidimensional lists and Adaptive Metadata™
Route decentralized content between connected systems on a large scale
Publishing content via fully customized Microsites
API-first design for ease of integration and extensibility
Customizable reference setups
Ready-made automation

Adaptive Metadata™ Layers
Unlimited metadata fields
Content type definitions Predefined configurations of metadata for different content types such as publish dates for press kits.
Semantic metadata Provides contextual associations between items so that users e.g. can find content using search terms that aren’t explicitly assigned as tags or legends can be provided related to specific usages of an image.
Controlled vocabularies
Auto-tagging based on visual recognition	()	Optional matching with a custom or ready-made controlled vocabulary
Multi-dimensional lists: Lists that store and provide additional attributes about each list item which again can be related to other lists and list items, all indexed as required and found when searching or tagging. For instance, the term “Switzerland” can store key information about the country such as population, size, languages spoken, tourist destinations etc.
Synonyms
Multi-language metadata

File-based content
“Fileless” content Strictly-structured content that can be accessed in a “headless” approach for multi-channel publishing based on the API and SDKs.
Remote content Linked content stored anywhere and tagged in the Content Platform such as competitor website pages, stock photos or other content accessible via URL.
Semantic relationships Content can be related to other content multi-dimensionally via user-defined relationships e.g. associating historic, source or format versions, or any other relationship.	() Basic parent-child relationships for e.g. versioning
Content processing and conversions		() Default format conversion for 1.x releases with custom format conversion available via API, added to the core in later releases.

Account & token-based access Users are managed in roles which are permitted on content, metadata and system functions. Additionally, collections can be access-permitted via secure tokens.
Permission granularity	Item-level and field-level	Item-level and layer-level

“Headless” content publishing   Manage single-source content that is published via API/SDK on multiple channels exactly the way it’s needed.
Share content via email or social media
Built-in CDN support Content distribution network fastly.com can be used for fast and reliable global content delivery.
Microsites & Portals Interactive sites that integrate into existing websites, landing pages or apps, or that can serve as standalone content portals such as press corners, product resource finders, and similar.	()
Mobile apps delivery Content can be published via API to mobile apps that pull content on-demand directly from the Content Platform.	()

API-first approach 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.
API	SOAP/WDSL	JSON/REST
SDK		C#/.NET, Angular.js and Fetch samples with growing amount of open-sourced code for Microsites, embed templates and Microservices. Additional SDKs in other languages such as Java and PHP to be released.
Front-end technologies	Sencha, HTML, CSS	AngularJS, HTML, CSS
Back-end technologies	C# / .NET, SQL Server, Windows Server	C# / .NET, ElasticSearch, Windows Server/LINUX
Microservices		Microservice architecture enabling certified developers to hook into a livestream of events, process document change history etc. and tightly or loosely integrate
Load balancing	() Available only to application and rendering services.	All system services. “Self healing” components and services to withstand outages.
Multiple storages Multiple storage technologies, providers and locations are supported.	() All content managed by Picturepark DAM is stored directly within the system.	() Remote content from multiple storages can be linked to provide a single virtual access point via Content Platform but file-based and fileless content is stored directly within the system. This will become extended at a later point in time with native support for storage providers such as AWS, Azure, and similar.

Interested to learn more about the forthcoming Content Platform?