The tool is a news hub especially for publishers and media houses. BRIXWIRE collects stories and assets from various sources (e.g. press agencies, CMS, planning, and editorial systems), transforms the content, and integrates it, ready to publish, into target systems like CMS, editorial, or DAM systems.
An agency report comes in, is selected and is ready for publication in the WoodWing Content Station or CMS with just a few clicks.
Something like this could happen through BRIXWIRE.
The central idea: to provide a plug-in-based manual or automated input of stories and to enable a channel-specific output via various conversion options.
• Web First approaches via CMS: set up an input channel on your CMS and connect it to your print output channel. Publishing
can be automatic or interactive.
• Print-First Approaches: Set up your editorial system as an input channel and connect it to your CMS output channel. Publishing can be automatic or interactive.
Various input channels for agency reports, integrated editorial systems, etc. actively search for content or are addressed by third-party systems. Content, inclusive assets are source-specific and are thus available to all available output plug-ins.
The story is converted into the desired target formats via the PIM Transformer and made available to the output plug-ins. Examples of output plugins are: Woodwing exports as an example for editorial systems, file system to support, for example, the data transfer during editorial system change, CMS systems.
Stories that are kept in BrixWire from different sources can be published manually or automatically to all connected output plugins. The editor is supported by extensive research options and personal profiles.
Both the input and the output plugins require transformations of the stories into the respective target format. The transformations are provided by a plugin-based transformation interface. Supported are for example HTML, XML, Office documents, JSON, Indesign documents, editing system specific data formats like WCML. Stories that are kept in BrixWire from different sources can be published manually or automatically to all connected output plugins. The editor is supported by extensive research options and personal profiles.
The manual assignment: BrixWire offers a so-called StoriesBrowser, via which the data input and output is monitored. The News Browser is used to editorially edit, export or assign output channels. The manual assignment functions both as a filter function for relevant stories and as a preliminary stage in the workflow in order to provide the stories optimally for further processing (templates and attribution).
BrixWire is a browser-based HTML 5 application and works with up-to-date browsers without client installation. An installation of Flash, Air or Silverlight is therefore not necessary.
User management is done via LDAP, Active Directory or a built-in user management. The permissions apply both to functions (admin area) and to data (such as output channels).
Both in terms of formats (NewsML, InCopy, XHTML, etc.) and in terms of attribution, IPTC and ISO standards are used.
BrixWire collects input stories and keeps them available for a freely definable period of time. This makes it easy to determine a publication history and the diagnosis of configuration errors.
In the central program elements both a keyboard-based method of operation across browsers and system-specific options, such as Clipboard, are supported. Data updates (such as changed metadata or output status) are passed on synchronized for all browsers.
At all BrixWire processing levels, plug-in technologies are supported, allowing configurations to be customized. Be it the use of less common input or output channels or access to existing solutions, such as DAM systems.
The application is multilingual, the default language is stored in the user profile of the logged-in user.
For recurring tasks, such as cleanups or automated synchronization jobs with output channels, BrixWire has a scheduler ready.
BrixWire is used in failover and load balancing environments and, with appropriate hosting, can be scaled and uninterrupted.
Operational components, such as input or output plug-ins, are monitored for performance and functionality by monitoring interfaces during operation. The monitoring outputs can be adapted via plug-ins to the monitoring tool of your publishing house, so that no additional cockpit is necessary.