xtent

With thousands of already produced books, publishers cannot rely only on a DAM to search for granular content to reuse, but need a publisher specific Content Manager that easily permit to use existing blocks (chapters, spreads, pages) allowing the designer to directly create new publications inside CMS. This approach maximizes production efficiency and avoids wasting time exporting the individual elements (images, InDesign templates, texts,…) outside CMS and losing the relations with their previous uses.


It is an enormous advantage to allow the publisher to browse through the DAM, identify individual content assets, pages or complete books using semantic searches, metadata and categories that can be used to build a new one and create it with a few clicks. The publisher can select in a page dashboard whatever groups of pages are relevant from different editions and link them to the blank pages of the new book. This means that the new book will be built easily using pieces from the different parent publications which also means that any update in the parent publication will update the new book. Designers can access CMS with an InDesign plugin, doing whatever changes needed in the InDesign document and ensuring that whatever edition they do (images, texts, layouts) is automatically stored in CMS. Moreover if we want to make a local change in this book that will not affect the parent, the designer only needs to set pages to be local pages and a copy of the original doc will be create to allow complete edits that will not affect the parent. Once all of the pages of the publication are completed, the server will process the book to recreate all the final pages, folios and indexes automating the production process.


Source : http://www.seinet.com/beyond-dam/

  Show me the Seinet Xtent solutions