The B.media Content Manager allows Users to create and manage all of the content that comprises the web and print publications. Within the Content Manager the Content Hierarchy allows Users to organize and manage non-Product content such as images, media files, and documents. Users can also group products and non-product Assets to organize Publications.
B.media has extensive Digital Asset Management functionality. Assets in B.media may be images, movies, sound files, or documents. Unlike many Content Management programs, which provide limited control over Asset content, B.media stores Asset files and allows customers to manage them directly. Customers can create their own Asset Types with custom Attributes to store metadata and publishing content about Assets. The direct management of Assets by B.media enables Check-Out/Check-In and Versioning. If they have been given appropriate permissions, Users may check out and open Assets in their native editing applications, then check them in as new versions. Old versions are saved, and each version has its own metadata.
*Note that B.media renders the clipping path on the chair image thumbnail
B.media's internal image engine also supports the automated creation of unique renditions of image files. This means that transformations may be applied to images at any stage of the production process to create new file formats, resolutions, sizes, and colorspaces. A common application is to have all images ingested into the system automatically render a web-appropriate, lower-resolution JPEG file for use in the web publishing workflow.
Blocks allow the User to create product offers by grouping Products and Assets together. Blocks can be used to group content for both print and online use. The Content Hierarchy allows the User to organize publications and manage Blocks and other related Assets, like Adobe InDesign or QuarkXPress page documents. Generally, a Block will contain all of the information, including headlines, product copy, product information, and images, to specify an integrated product offer.
Blocks can have their own Attributes, just like Products and Assets. B.media has a number of tools for managing Attributes, including configurable UI Controls (for example, drop-downs, combos boxes, and field masks), Unicode Special Characters for cross-platform consistency, and definable Text Tags for applying formatting.
When Products, Assets, or Blocks are complete, Users may export the Attributes, metadata, and even underlying Assets using Publishing Targets. The Publishing Target exports data as XML, and can also export files according to rules set by the User - for example specifying that a particular, web-appropriate rendition of an Asset is to be exported. The Publishing Target process is integrated with the internal web architecture of the site, meaning that web updates with timely, accurate information are generated from the same data source from which the print pages will be produced.
Publishing Targets allow Users to export data without waiting for an entire update cycle to be completed, meaning that new Products and updated information are available immediately. Users can define a Publishing Target to include as little or as much data as they want for a particular use. Because B.media manages Assets directly, this export can include asset files as well as Attributes. Using B.media Transformations, Users can even create Publishing Targets which generate new Renditions of Assets on export - for example, a thumbnail view of a catalog page.
