<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Product Catalog Software Blog &#187; General</title>
	<atom:link href="http://apsiva.com/blog/category/general/feed/" rel="self" type="application/rss+xml" />
	<link>http://apsiva.com/blog</link>
	<description>Multi-Channel Catalog Publishing to Print, Web, PDF and CD</description>
	<lastBuildDate>Mon, 21 Jun 2010 20:09:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Catalog Software Basics</title>
		<link>http://apsiva.com/blog/2010/06/catalog-software-basics/</link>
		<comments>http://apsiva.com/blog/2010/06/catalog-software-basics/#comments</comments>
		<pubDate>Mon, 21 Jun 2010 20:09:20 +0000</pubDate>
		<dc:creator>steku</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://apsiva.com/blog/?p=42</guid>
		<description><![CDATA[As your product catalogs grow, you may find yourself overwhelmed with the sheer volume of product updates. If it is taking far too long to update your products and publish a catalog, Apsiva Catalog Software can be of great help.
Apsiva catalog software provides an easy way to organize and publish products. With many options available, [...]]]></description>
			<content:encoded><![CDATA[<p>As your product catalogs grow, you may find yourself overwhelmed with the sheer volume of product updates. If it is taking far too long to update your products and publish a catalog, Apsiva Catalog Software can be of great help.</p>
<p>Apsiva catalog software provides an easy way to organize and publish products. With many options available, the intended use of the catalog software varies. Apsiva catalog software is designed to:</p>
<p>1.	Aid in easy storage, organization and retrieval of products, descriptions and their images<br />
2.	Allow for several people to contribute to and share product information<br />
3.	Control access to products based on a user role<br />
4.	Link up images with products<br />
5.	Reduce repetitive duplicate input<br />
6.	Simplify publishing</p>
<p>Apsiva can be deployed either as an enterprise wide system or for Print or Web publishing. To learn more about Apsiva, visit www.apsiva.com or call us at 847-299-0900.</p>
]]></content:encoded>
			<wfw:commentRss>http://apsiva.com/blog/2010/06/catalog-software-basics/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bridging the Gap Between “Page Pump” Automation and Creative Layouts</title>
		<link>http://apsiva.com/blog/2009/08/bridging-the-gap-between-%e2%80%9cpage-pump%e2%80%9d-automation-and-creative-layouts/</link>
		<comments>http://apsiva.com/blog/2009/08/bridging-the-gap-between-%e2%80%9cpage-pump%e2%80%9d-automation-and-creative-layouts/#comments</comments>
		<pubDate>Tue, 04 Aug 2009 19:35:33 +0000</pubDate>
		<dc:creator>steku</dc:creator>
				<category><![CDATA[Catalog Software]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Print Catalog Publishing]]></category>

		<guid isPermaLink="false">http://apsiva.com/blog/?p=34</guid>
		<description><![CDATA[

It might be too simplistic to suggest that B2B companies are mainly interested in pumping out catalog pages, while B2C companies care more about creativity and the presentation of the catalog page as an individual work of art.  However, there is an underlying fundamental truth at play.  While B2B must win over the “brain” with [...]]]></description>
			<content:encoded><![CDATA[<p><!--[if gte mso 10]><br />
<mce:style><!    /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:10.0pt; 	font-family:"Times New Roman";}  --></p>
<p><!--[endif]--></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">It might be too simplistic to suggest that B2B companies are mainly interested in pumping out catalog pages, while B2C companies care more about creativity and the presentation of the catalog page as an individual work of art.  However, there is an underlying fundamental truth at play.  While B2B must win over the “brain” with detailed and accurate specifications, B2C intends to win over the more unpredictable “heart” by getting the customer emotionally involved with the products they are trying to sell.</span></p>
<p class="MsoNormal">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">The typical “page pump” solution involves a pre-set library of rigid templates that are merged with product information, specifications, and other technical data to create charts and tables.  While this approach is fine for many B2Bers (not to mention some B2Cers), more than ever we are starting to see a desire for better-looking output…regardless of industry.  Part of the problem is that “page pumps” are often indistinguishable from one another.  While it may convey the nitty-gritty details, it does not necessarily set your company apart from your competition.</span></p>
<p class="MsoNormal">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">A more modern approach is to infuse some of the creativity and design aspects from the B2C realm into the typically staid B2B pages.  Granted, there is a fine line to walk.  You can’t lose sight of what the customer wants and needs, and you don’t want to needlessly complicate the process of creating catalog page output.   In most cases, however, it is entirely possible to enliven your pages with a more creative, flexible, yet still <em>fully automated</em> approach.</span></p>
<p class="MsoNormal">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">With a choice between a bland,  “cookie cutter” page and one that grabs your attention, why continue to choose the “Blah” approach?   The time has come when choosing to spice up your catalog pages no longer means it can’t be automated, or easy.</span></p>
<p class="MsoNormal">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">We are very excited to announce our all-new product, PRINTexpress™.  It’s the same game, but we’ve just changed the rules!</span></p>
]]></content:encoded>
			<wfw:commentRss>http://apsiva.com/blog/2009/08/bridging-the-gap-between-%e2%80%9cpage-pump%e2%80%9d-automation-and-creative-layouts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Reducing Catalog Emissions &#8211; Part 1</title>
		<link>http://apsiva.com/blog/2009/05/reducing-catalog-emissions-part-1/</link>
		<comments>http://apsiva.com/blog/2009/05/reducing-catalog-emissions-part-1/#comments</comments>
		<pubDate>Mon, 11 May 2009 14:18:37 +0000</pubDate>
		<dc:creator>steku</dc:creator>
				<category><![CDATA[Catalog Software]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Personalized Catalogs]]></category>
		<category><![CDATA[Print Catalog Publishing]]></category>
		<category><![CDATA[Product Information Management]]></category>

		<guid isPermaLink="false">http://apsiva.com/blog/reducing-catalog-emissions-part-1.html</guid>
		<description><![CDATA[

Printing is sometimes necessary and unavoidable. However the burden on the environment is enormous. Based on a mixture of softwood and hardwood trees, 40 feet tall and 6-8 inches in diameter, it would take a rough average of 24 trees to produce a ton of printing and writing paper, using a certain pulping process.

As the [...]]]></description>
			<content:encoded><![CDATA[<p><!--[if gte mso 10]><br />
<mce:style><!    /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:10.0pt; 	font-family:"Times New Roman";}  --></p>
<p><!--[endif]--></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">Printing is sometimes necessary and unavoidable. However the burden on the environment is enormous. Based on a mixture of softwood and hardwood trees, 40 feet tall and 6-8 inches in diameter, it would take a rough average of 24 trees to produce a ton of printing and writing paper, using a certain pulping process.</span></p>
<p class="MsoNormal">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">As the world gets more environmentally conscious, there is a growing trend to use less paper. Consumers are adopting this by increasing their paperless habits. Apsiva is making it easy so catalogers can aid this process and help the environment by reducing paper use.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">Many catalogers have already realized the need to reduce the number of pages in catalogs. The fewer the pages in the catalog, the less trees get gobbled up. Some catalogers have gone even further by re-designing and shrinking their page margins to .75 or less. This is barely noticeable, but the savings add up.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">Though these strategies are useful, they don&#8217;t go far enough. Apsiva&#8217;s products are environmentally friendly and with Apsiva&#8217;s products, you can do more. In the first part of this article, we will focus on how to use Apsiva&#8217;s web catalog software.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">Apsiva&#8217;s Private catalogs module can be used to email personalized catalogs to your customers instead of print catalogs. Apsiva&#8217;s private catalogs can be setup for individual customers or businesses by selecting the products only that customer can use. This capability offers a few key advantages:</span></p>
<ol style="margin-top: 0in" type="1">
<li class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">It allows the customer to get      their specific prices</span></li>
<li class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">It displays only the products      that are a fit for the customer</span></li>
<li class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">Pricing and products are      dynamic.</span></li>
</ol>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">Many organizations are taking advantage of web based private catalogs, public catalogs and e-commerce sites with Apsiva&#8217;s catalog software: WEBsource. As always, WEBsource draws data from a centralized content management system, hence eliminating the need for managing content in multiple databases. Apsiva&#8217;s catalog creation tools are all built on the same platform.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">In part 2, we will discuss how Apsiva&#8217;s PDFsource software allows you to reduce your catalog emissions.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://apsiva.com/blog/2009/05/reducing-catalog-emissions-part-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Focusing on Ease of Use</title>
		<link>http://apsiva.com/blog/2009/04/focusing-on-ease-of-use/</link>
		<comments>http://apsiva.com/blog/2009/04/focusing-on-ease-of-use/#comments</comments>
		<pubDate>Sat, 04 Apr 2009 16:24:35 +0000</pubDate>
		<dc:creator>steku</dc:creator>
				<category><![CDATA[Catalog Software]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[InDesign Mojo]]></category>
		<category><![CDATA[Print Catalog Publishing]]></category>
		<category><![CDATA[Product Information Management]]></category>

		<guid isPermaLink="false">http://apsiva.com/blog/focusing-on-ease-of-use.html</guid>
		<description><![CDATA[

The complexity of publishing to each catalog channel has grown. This is primarily due to the evolution of each channel in its offerings. The result has been that the tools that provide centralized content management have also grown in complexity. While having the opportunity to work with many different catalogers over the years, Apsiva has [...]]]></description>
			<content:encoded><![CDATA[<p><!--[if gte mso 10]><br />
<mce:style><!    /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:10.0pt; 	font-family:"Times New Roman";}  --></p>
<p><!--[endif]--></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">The complexity of publishing to each catalog channel has grown. This is primarily due to the evolution of each channel in its offerings. The result has been that the tools that provide centralized content management have also grown in complexity. While having the opportunity to work with many different catalogers over the years, Apsiva has found one constant: not all users within an organization have the same degree of skill when using software. Some users are comfortable with Excel, some with Word, and some with Adobe InDesign. So, with the right user interface, a catalog designer can be freed from much of the tedious work which allows them to spend that time creating.</span></p>
<p class="MsoNormal">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">Apsiva&#8217;s new catalog building software solutions have evolved to make this process as effortless as possible. Apsiva&#8217;s new version 7.0 is easy to use but yet, at any moment, a user can dive deep into any specific area of the application to get more detail.</span></p>
<p class="MsoNormal">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">If we simply replace the wasted time spent on performing repetitive data-entry and error-checking tasks with wasted time spent on stumbling and fumbling through a tool that isn&#8217;t intuitive, we haven&#8217;t gained anything.  That is why Apsiva has made the user interface a focus:  in the end, the success of any software hinges on the user experience.  Powerful features don&#8217;t necessarily have to translate into a jumble of menus and buttons; with Apsiva, the complexity is hidden in the background, deep in the tool itself, where it belongs.  We don&#8217;t want novice users to feel intimidated by our tool; we want them to actually use it and get the value from it starting Day 1.  At the same time, we don&#8217;t want to alienate the power users out there who prefer the no-nonsense, nitty-gritty approach.  So a power users functionality is still available, just not out front-and-center.  Allowing the end user to choose an interface of his/her choice is how Apsiva makes the return on your investment quick.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://apsiva.com/blog/2009/04/focusing-on-ease-of-use/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Open Standards based Product Database</title>
		<link>http://apsiva.com/blog/2009/03/open-standards-based-product-database/</link>
		<comments>http://apsiva.com/blog/2009/03/open-standards-based-product-database/#comments</comments>
		<pubDate>Thu, 19 Mar 2009 13:22:44 +0000</pubDate>
		<dc:creator>steku</dc:creator>
				<category><![CDATA[Catalog Software]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Print Catalog Publishing]]></category>
		<category><![CDATA[Product Information Management]]></category>

		<guid isPermaLink="false">http://apsiva.com/blog/open-standards-based-product-database.html</guid>
		<description><![CDATA[

Apsiva is built entirely on open standards which offers various benefits as discussed in this post. The main function of Apsiva is to empower creative teams by making digital assets easily accessible. As Apsiva makes manages content, it does so in a way that rights and permissions to content are publicly available to other applications. [...]]]></description>
			<content:encoded><![CDATA[<p><!--[if gte mso 10]><br />
<mce:style><!    /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:10.0pt; 	font-family:"Times New Roman";}  --></p>
<p><!--[endif]--></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">Apsiva is built entirely on open standards which offers various benefits as discussed in this post. The main function of Apsiva is to empower creative teams by making digital assets easily accessible. As Apsiva makes manages content, it does so in a way that rights and permissions to content are publicly available to other applications. A benefit of this approach is users outside of Apsiva can continue using products such as Adobe Bridge to search for digital assets based on product links. While Bridge has many powerful and useful features, it can be completely nullified if digital assets are poorly linked to products or have no linking to begin with.  Apsiva&#8217;s technology puts enough keywords in the digital assets to make assets searchable and accessible and up-to-the-minute accurate from external tools and systems. External systems (like the web) can also benefit from this approach since assets don&#8217;t need to be duplicated across systems.</span></p>
<p class="MsoNormal">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">The core of Apsiva&#8217;s capability is to link products with their corresponding digital assets, supplier logos, certifications, etc.   Apsiva&#8217;s strength lies in automatically linking images with products. This linking does not &#8216;relocate&#8217; the image to Apsiva&#8217;s internal structure, but leaves the images in neatly organized folders.  This is the open standards approach.   This makes assets easy to find and fosters reusability which in turn saves time and money.</span></p>
<p class="MsoNormal">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">This capability makes Apsiva&#8217;s implementation &#8216;Open&#8217;, and hence gives you more than one way to get to your digital assets without duplication.</span></p>
<p class="MsoNormal">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">By centralizing digital assets, Apsiva brings an organized approach to digital assets and improves searchability across all the members in the creative team.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://apsiva.com/blog/2009/03/open-standards-based-product-database/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why Apsiva Manages Content in Granular Detail</title>
		<link>http://apsiva.com/blog/2009/02/catalog-management-terminology-%e2%80%9ccontent-granularity%e2%80%9d/</link>
		<comments>http://apsiva.com/blog/2009/02/catalog-management-terminology-%e2%80%9ccontent-granularity%e2%80%9d/#comments</comments>
		<pubDate>Tue, 10 Feb 2009 00:13:34 +0000</pubDate>
		<dc:creator>steku</dc:creator>
				<category><![CDATA[Catalog Software]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Print Catalog Publishing]]></category>
		<category><![CDATA[Product Information Management]]></category>

		<guid isPermaLink="false">http://apsiva.com/blog/?p=5</guid>
		<description><![CDATA[

What does it mean when content is &#8216;granular&#8217; in nature, and how much is enough?  If all copy for a given product were to be stored as one large blob of text, it might be fine for display on a website, but it would be unwieldy when it came to print copy.  Storing [...]]]></description>
			<content:encoded><![CDATA[<p><!--[if gte mso 10]><br />
<mce:style><!    /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:10.0pt; 	font-family:"Times New Roman";}  --></p>
<p><!--[endif]--></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">What does it mean when content is &#8216;granular&#8217; in nature, and how much is enough?  If all copy for a given product were to be stored as one large blob of text, it might be fine for display on a website, but it would be unwieldy when it came to print copy.  Storing this content instead at a more granular level:  for instance, breaking down copy into a headline, sub head, main copy, and features makes the same text far more useful. In this form, we can now pick and choose which elements are best suited for a particular channel; at the same time, we can easily update a specific element such as Price and have it instantly available to all channels, without updating it in multiple places.</span></p>
<p class="MsoNormal">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">Almost as bad as &#8220;not granular enough&#8221;, however, is &#8220;too granular&#8221;.  Yes, it is entirely possible to get carried away and break content down into too many elements to the point where it stops being useful and instead becomes a maintenance chore.</span></p>
<p class="MsoNormal">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">Finding the right balance when it comes to content granularity is key. We recommend that content should be broken down to the extent necessary but only to the detail we can get away with. There are no hard set rules, and it&#8217;s going to be different for every company.  The challenge is in understanding the pros and cons, and striking the right balance.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://apsiva.com/blog/2009/02/catalog-management-terminology-%e2%80%9ccontent-granularity%e2%80%9d/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Welcome !</title>
		<link>http://apsiva.com/blog/2007/06/hello-world/</link>
		<comments>http://apsiva.com/blog/2007/06/hello-world/#comments</comments>
		<pubDate>Thu, 14 Jun 2007 13:37:35 +0000</pubDate>
		<dc:creator>steku</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[

Welcome to my blog on Multi-Channel Catalog Publishing. I hope to help you stay in touch with the ground realities of multi-channel catalog publishing and to provide opinion, insights, content and expertise in catalog publishing.
]]></description>
			<content:encoded><![CDATA[<p><!--[if gte mso 10]><br />
<mce:style><!    /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:10.0pt; 	font-family:"Times New Roman";}  --></p>
<p><!--[endif]--></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial">Welcome to my blog on Multi-Channel Catalog Publishing. I hope to help you stay in touch with the ground realities of multi-channel catalog publishing and to provide opinion, insights, content and expertise in catalog publishing.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://apsiva.com/blog/2007/06/hello-world/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

