<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule">

<channel>
	<title>Digital Collections Blog</title>
	<atom:link href="http://library.duke.edu/blogs/digital-collections/feed/" rel="self" type="application/rss+xml" />
	<link>http://library.duke.edu/blogs/digital-collections</link>
	<description>Notes from the Digital Collections Team at Duke</description>
	<lastBuildDate>Wed, 03 Feb 2010 21:52:38 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/us/</creativeCommons:license>		<item>
		<title>Presentation on Initial Wireframes (2/3/10)</title>
		<link>http://library.duke.edu/blogs/digital-collections/2010/02/03/presentation-on-initial-wireframes-2310/</link>
		<comments>http://library.duke.edu/blogs/digital-collections/2010/02/03/presentation-on-initial-wireframes-2310/#comments</comments>
		<pubDate>Wed, 03 Feb 2010 21:50:28 +0000</pubDate>
		<dc:creator>Sean Aery</dc:creator>
				<category><![CDATA[Website Redesign]]></category>

		<guid isPermaLink="false">http://library.duke.edu/blogs/digital-collections/?p=3691</guid>
		<description><![CDATA[
.prezi-player { width: 450px; } .prezi-player-links { text-align: center; }


Duke Digital Collections Website: Analysis &#38; Wireframes 2/3/10 on Prezi


This morning, I gave a presentation to our library staff to show and discuss our possible wireframe prototypes, as well as the analysis that informed the designs.  It&#8217;s a sort of visual summary of our redesign-related [...]]]></description>
			<content:encoded><![CDATA[<div class="prezi-player">
<style type="text/css" media="screen">.prezi-player { width: 450px; } .prezi-player-links { text-align: center; }</style>
<p><object id="prezi_vfhv59d_iv9y" name="prezi_vfhv59d_iv9y" classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="450" height="350"><param name="movie" value="http://prezi.com/bin/preziloader.swf"/><param name="allowfullscreen" value="true"/><param name="allowscriptaccess" value="always"/><param name="bgcolor" value="#ffffff"/><param name="flashvars" value="prezi_id=vfhv59d_iv9y&amp;lock_to_path=0&amp;color=ffffff&amp;autoplay=no"/><embed id="preziEmbed_vfhv59d_iv9y" name="preziEmbed_vfhv59d_iv9y" src="http://prezi.com/bin/preziloader.swf" type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="450" height="350" bgcolor="#ffffff" flashvars="prezi_id=vfhv59d_iv9y&amp;lock_to_path=0&amp;color=ffffff&amp;autoplay=no"></embed></object>
<div class="prezi-player-links">
<p><a title="Duke University Libraries Digital Collections web redesign project, featuring analysis &amp; wireframe mockups.    More info: http://library.duke.edu/blogs/digital-collections/category/website-redesign/  Share your feedback: http://library.duke.edu/digita" href="http://prezi.com/vfhv59d_iv9y/">Duke Digital Collections Website: Analysis &amp; Wireframes 2/3/10</a> on <a href="http://prezi.com">Prezi</a></p>
</div>
</div>
<p>This morning, I gave a presentation to our library staff to show and discuss our possible wireframe prototypes, as well as the analysis that informed the designs.  It&#8217;s a sort of visual summary of our <a href="http://library.duke.edu/blogs/digital-collections/category/website-redesign/">redesign-related blog posts</a> to this point.  The embedded version here is small, but you can <a href="http://prezi.com/vfhv59d_iv9y/">view the full presentation here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://library.duke.edu/blogs/digital-collections/2010/02/03/presentation-on-initial-wireframes-2310/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Collection Homepages: Prototypes, Analysis, &amp; Inspiration</title>
		<link>http://library.duke.edu/blogs/digital-collections/2010/02/02/collection-homepages-prototypes-analysis-inspiration/</link>
		<comments>http://library.duke.edu/blogs/digital-collections/2010/02/02/collection-homepages-prototypes-analysis-inspiration/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 16:17:57 +0000</pubDate>
		<dc:creator>Sean Aery</dc:creator>
				<category><![CDATA[Website Redesign]]></category>

		<guid isPermaLink="false">http://library.duke.edu/blogs/digital-collections/?p=3211</guid>
		<description><![CDATA[At long last, here&#8217;s the final group of wireframes we&#8217;ll blog about for our site redesign project: the individual collection homepages.  Here&#8217;s an annotated look at one of our current collection homepages:
View this feedback (Collection Homepage &#8211; Current Site) on Notable
Prototypes
Here are six possibilities (A &#8211; F).  We&#8217;ve used Ad*Access as an example, [...]]]></description>
			<content:encoded><![CDATA[<p>At long last, here&#8217;s the final group of wireframes we&#8217;ll blog about for our <a href="http://library.duke.edu/digitalcollections/redesign-feedback.html">site redesign project</a>: the individual collection homepages.  Here&#8217;s an annotated look at one of our current collection homepages:</p>
<p><script src='https://seanaery.notableapp.com/public/31943/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/31943/Collection-Homepage-Current-Site'>View this feedback (Collection Homepage &#8211; Current Site) on Notable</a></noscript></p>
<h3>Prototypes</h3>
<p><a href="http://gomockingbird.com/mockingbird/index.html?project=6e65a763010f6e8bb72ed9bbe94bffb72603f559">Here are six possibilities (A &#8211; F)</a>.  We&#8217;ve used <a href="http://library.duke.edu/digitalcollections/adaccess/">Ad*Access</a> as an example, as it is our most-visited collection:</p>
<p><a href="http://gomockingbird.com/mockingbird/index.html?project=6e65a763010f6e8bb72ed9bbe94bffb72603f559"><img src="http://library.duke.edu/blogs/digital-collections/wp-content/uploads/2010/02/adaccesshomemockup.jpg" alt="adaccesshomemockup" title="adaccesshomemockup" width="450" height="220" class="aligncenter size-full wp-image-3601" /></a></p>
<h2>Analysis</h2>
<p>The ideas in the prototypes stem from our analysis of the current site, per the following:<br />
<span id="more-3211"></span></p>
<h3>Web Analytics</h3>
<ul>
<li>Collection homepages are big attractions.  How big?  Our most popular <a href="http://library.duke.edu/blogs/digital-collections/2009/02/02/collection-usage-stats-for-2008/">collections&#8217; homepages are visited even more often than our portal</a> page.  Other than our <a href="http://library.duke.edu">main library homepage</a> and our <a href="http://library.duke.edu/research/citing/index.html">guide to citing sources</a>, the <a href="http://library.duke.edu/digitalcollections/adaccess/">AdAccess</a>, <a href="http://library.duke.edu/digitalcollections/adviews/">AdViews</a>, &amp; <a href="http://library.duke.edu/digitalcollections/eaa/">EAA</a> homepages were the most-visited pages in our entire library website (<em>from June-Dec 2009</em>).</li>
<li>From our portal page, <a href="http://library.duke.edu/blogs/digital-collections/2009/02/23/homepage-economics/">people are 3x more likely</a> to browse to a collection homepage than they are to do a cross-collection search.</li>
</ul>
<h3>Interviews With Collection Sponsors</h3>
<ul>
<li>Make it clear and obvious what a user should do upon visiting.  Most people either want to search or browse.  Put the search &amp; browse options front &amp; center.</li>
<li>Move the paragraphs of text to a separate &#8216;about&#8217; page.</li>
<li>Give a visual taste of what kinds of things are in the collection.</li>
<li>Show the most popular items in each collection.</li>
<li>Let people more easily browse all of the available metadata for each collection (e.g., browse all companies in an ad collection).</li>
<li>Use a better combination of fonts &amp; colors to help the pages from feeling boring.</li>
<li>Give each collection more character by using graphics that enforce branding.</li>
</ul>
<h3>Feedback Forms &amp; Other User Feedback</h3>
<ul>
<li>Avoid the &#8220;wall of text&#8221;; make the &#8220;home page copy read more like web copy.&#8221;</li>
<li>Feature timelines more prominently</li>
<li>Having two search boxes (one for inter-collection &amp; one for intra-collection searches) is confusing.</li>
</ul>
<h3>Ideas From the Implementation Team</h3>
<ul>
<li>Build a smart template that is 1) unified enough to make collection-publishing efficient and the user experience consistent, but 2) flexible enough to allow each collection to be individually branded (if desired) and to present the most optimal arrangement of browsing options given what&#8217;s in the collection.</li>
<li>Incorporate blog posts on collection homepages, so experts have the ability to write about each collection on an ongoing basis.</li>
<li>Provide advanced navigation options (like linked term clouds, timelines) for all collections.</li>
</ul>
<h2>Inspiring Examples from Around the Web</h2>
<p><script src='https://seanaery.notableapp.com/public/29607/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/29607/Brooklyn-Museum-Collection-Homepage'>View this feedback (Brooklyn Museum Collection Homepage) on Notable</a></noscript></p>
<p><script src='https://seanaery.notableapp.com/public/29594/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/29594/Hulu-Collection-Page'>View this feedback (Hulu &#8220;Collection&#8221; Page) on Notable</a></noscript></p>
<p><script src='https://seanaery.notableapp.com/public/29709/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/29709/Hugh-Morton-Collection-Homepage'>View this feedback (Hugh Morton Collection Homepage) on Notable</a></noscript></p>
<p><script src='https://seanaery.notableapp.com/public/31939/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/31939/Internet-Archive-Moving-Images-Archive'>View this feedback (Internet Archive: Moving Images Archive) on Notable</a></noscript></p>
<p>What do you think?  Join in the conversation here in the comments, or <a href="http://library.duke.edu/digitalcollections/redesign-feedback.html">comment anonymously via our feedback form</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://library.duke.edu/blogs/digital-collections/2010/02/02/collection-homepages-prototypes-analysis-inspiration/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Portal Page: Prototypes, Analysis &amp; Inspiration</title>
		<link>http://library.duke.edu/blogs/digital-collections/2010/01/15/portal-page-prototypes-analysis-inspiration/</link>
		<comments>http://library.duke.edu/blogs/digital-collections/2010/01/15/portal-page-prototypes-analysis-inspiration/#comments</comments>
		<pubDate>Fri, 15 Jan 2010 21:14:09 +0000</pubDate>
		<dc:creator>Jessica Weber</dc:creator>
				<category><![CDATA[Website Redesign]]></category>

		<guid isPermaLink="false">http://library.duke.edu/blogs/digital-collections/?p=3251</guid>
		<description><![CDATA[We’d like to share some of our ideas for the future portal page to Duke Digital Collections.  We have included highlights from user feedback that draw attention to important navigation elements, as well as examples of websites that have informed these designs. Please let us know what you think!
Prototypes
You can review our five initial [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://gomockingbird.com/mockingbird/index.html?project=839721456e4a71b8d9fb428301705a7bedafa41c"><img class="size-full wp-image-3411 alignright" style="float:right;" title="homemockup" src="http://library.duke.edu/blogs/digital-collections/wp-content/uploads/2010/01/homemockup.jpg" alt="homemockup" width="250" height="232" /></a>We’d like to share some of our ideas for the future portal page to Duke Digital Collections.  We have included highlights from user feedback that draw attention to important navigation elements, as well as examples of websites that have informed these designs. Please let us know what you think!</p>
<h2>Prototypes</h2>
<p>You can review our <a href="http://gomockingbird.com/mockingbird/index.html?project=839721456e4a71b8d9fb428301705a7bedafa41c">five initial prototypes (A through E) here</a>.</p>
<p>Emphasis has been placed on ways to ease navigation by providing clear, easy ways to browse and prominently displaying visual content that highlights an assortment of interesting materials from our collections.<strong> </strong></p>
<h2>Analysis</h2>
<p>We’ve uncovered several important requirements for the new portal page through the variety of research methods we employed:<br />
<span id="more-3251"></span></p>
<h3>Web Analytics</h3>
<p>1. Many search queries are for formats, decades, and collection names. It is essential we provide a means to filter items accordingly.</p>
<p>2.  Based on web analytics collected in 2008, people are nearly three times more likely to visit individual collection homepages than to conduct a cross-collection search. These numbers show how important it is to put our collection list front and center so it can be easily identified and browsed.</p>
<h3>Usability Tests (Spring 2008)</h3>
<p>1.  Undergraduates liked the carousel of images because they could see actual items from the collections.</p>
<p>2.  The overall design and appearance of the current page was described as &#8220;clean&#8221;, &#8220;simple&#8221;, &#8220;nice&#8221; and &#8220;easy to understand&#8221;.  These are fundamentals that should take precedent when reformulating the portal page.</p>
<h3>Feedback Forms and Other User Feedback</h3>
<p>1.  Discovery could be improved if image collections are listed by both first and last name in the Browse A-Z list, as many people look for the photographer by surname, e.g. consider putting the Sidney D. Gamble photograph collection in both the Ss and the Gs.</p>
<p>2. Flatten the navigation and reduce the necessary clicks to get to collections and items.</p>
<h3>Interviews with Our Collection Sponsors</h3>
<p>Most highly desired improvements:</p>
<p>1.  The current label of “featured collection” is confusing and should be clarified or eliminated.</p>
<p>2.  Remove anchor links, reduce scrolling, and give collections more prominence.</p>
<p>3.  Add a way to get items by format, as that is a common use case.</p>
<h3>Ideas from the Implementation Team<span style="text-decoration: underline;"> </span></h3>
<p>1.  Create more visualization discovery tools like maps, timelines, and term clouds.</p>
<p>2.  Increase the dynamic content to liven up the page and keep it from feeling stale.</p>
<p>3.  Fashion interface elements that cycle through content, hide/show elements, and load new content without loading a new page.</p>
<p>4.  The portal page should provide more previews of what’s in the collections to give users a better visual taste of what’s interesting.</p>
<p>5. Feature timely, relevant posts from our blog(s) and better integrate what we and others are saying about our collections using social media tools.</p>
<h2>Inspiring Examples</h2>
<p>Below are a few example websites that demonstrate thoughtful and innovative solutions to many of our requirements (<a href="https://dukedigitalcollections.notableapp.com/workspaces/ddc/sets/1975">see the whole set here</a>):</p>
<p><script src="https://dukedigitalcollections.notableapp.com/public/27521/thumbnail/med.js"></script><noscript>&amp;amp;amp;lt;a href=&#8221;https://dukedigitalcollections.notableapp.com/website-feedback/27521/Smithsonian-Collections-Search-Center&#8221; mce_href=&#8221;https://dukedigitalcollections.notableapp.com/website-feedback/27521/Smithsonian-Collections-Search-Center&#8221;&amp;amp;amp;gt;View this feedback (Smithsonian Collections Search Center) on Notable&amp;amp;amp;lt;/a&amp;amp;amp;gt;</noscript> <script src="https://dukedigitalcollections.notableapp.com/public/28424/thumbnail/med.js"></script><noscript>&amp;amp;amp;lt;a href=&#8221;https://dukedigitalcollections.notableapp.com/website-feedback/28424/BYU-Digital-Collections&#8221; mce_href=&#8221;https://dukedigitalcollections.notableapp.com/website-feedback/28424/BYU-Digital-Collections&#8221;&amp;amp;amp;gt;View this feedback (BYU Digital Collections) on Notable&amp;amp;amp;lt;/a&amp;amp;amp;gt;</noscript></p>
<p><script src="https://dukedigitalcollections.notableapp.com/public/28501/thumbnail/med.js"></script><noscript>&amp;amp;amp;lt;a href=&#8221;https://dukedigitalcollections.notableapp.com/website-feedback/28501/ECU-Digital-Collections&#8221; mce_href=&#8221;https://dukedigitalcollections.notableapp.com/website-feedback/28501/ECU-Digital-Collections&#8221;&amp;amp;amp;gt;View this feedback (ECU Digital Collections) on Notable&amp;amp;amp;lt;/a&amp;amp;amp;gt;</noscript></p>
]]></content:encoded>
			<wfw:commentRss>http://library.duke.edu/blogs/digital-collections/2010/01/15/portal-page-prototypes-analysis-inspiration/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Search Results: Prototypes, Analysis &amp; Inspiration</title>
		<link>http://library.duke.edu/blogs/digital-collections/2009/12/08/search-results-prototypes-analysis-inspiration/</link>
		<comments>http://library.duke.edu/blogs/digital-collections/2009/12/08/search-results-prototypes-analysis-inspiration/#comments</comments>
		<pubDate>Tue, 08 Dec 2009 15:14:11 +0000</pubDate>
		<dc:creator>Sean Aery</dc:creator>
				<category><![CDATA[Assessment]]></category>
		<category><![CDATA[Website Redesign]]></category>

		<guid isPermaLink="false">http://library.duke.edu/blogs/digital-collections/?p=2881</guid>
		<description><![CDATA[As we continue our redesign, we&#8217;re getting some really helpful feedback on our mockups for item pages.  By all means, keep it coming!  Here are some new prototypes for our search results screens, as well as our analysis of our current search results and examples of others systems we like.  What do [...]]]></description>
			<content:encoded><![CDATA[<p>As we continue <a href="http://library.duke.edu/blogs/digital-collections/2009/09/08/redesigning-duke-digital-collections/">our redesign</a>, we&#8217;re getting some really helpful feedback on our <a href="http://library.duke.edu/blogs/digital-collections/2009/11/25/item-pages-prototypes/">mockups for item pages</a>.  By all means, keep it coming!  Here are some new prototypes for our search results screens, as well as our analysis of our current search results and examples of others systems we like.  What do you think?</p>
<h2>Prototypes</h2>
<p><a href="http://gomockingbird.com/mockingbird/index.html?project=54bf09f2e451b776fba1ae66e40230e8a3d4a1d8"><img src="http://library.duke.edu/blogs/digital-collections/wp-content/uploads/2009/12/serp-prototypes.jpg" alt="serp-prototypes" title="serp-prototypes" width="450" height="201" class="alignnone size-full wp-image-3081" /></a></p>
<p>There are <a href="http://gomockingbird.com/mockingbird/index.html?project=54bf09f2e451b776fba1ae66e40230e8a3d4a1d8">five examples here</a>; some are searching across all collections and others are searching within a single collection.  Particular areas of interest for us:  location of the &#8216;Narrow by&#8217; facets, display of results for matching digital collections or matching digital exhibits, collection branding &#038; info. </p>
<h2>Analysis</h2>
<p><script src='https://seanaery.notableapp.com/public/21052/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/21052/Search-Results-CrossCollection-Existing-Interface'>View this feedback (Search Results (Cross-Collection): Existing Interface) on Notable</a></noscript><br />
Here&#8217;s what we have learned about our search interface from our various evaluation methods:</p>
<h3>Web Analytics</h3>
<ol>
<li> About <span style="background-color: lightyellow; font-weight: bold;">75% of searches are within-collection</span> searches; 25% are cross-collection.</li>
<li><a href="http://library.duke.edu/blogs/digital-collections/2009/11/24/search-analysis-what-weve-learned/">The majority of searches are for various topics</a>, though many <span style="background-color: lightyellow; font-weight: bold;">users search for items from a particular decade (&#8221;1920s&#8221;)</span>,  format (&#8221;advertisements&#8221;), or collection (&#8221;Gamble&#8221;).</li>
<li>Some users attempt to <span style="background-color: lightyellow; font-weight: bold;">retrieve every item possible</span> through search (&#8221;*&#8221;, &#8220;all&#8221;, &#8220;a&#8221;)</li>
</ol>
<h3>Usability Tests (Spring 2008)</h3>
<p><span id="more-2881"></span></p>
<ol>
<li>Users found it <span style="background-color: lightyellow; font-weight: bold;">easy to narrow results</span> using the facets on left, though some wanted this section to be more legible.</li>
<li>Users were able to <span style="background-color: lightyellow; font-weight: bold;">easily toggle between the grid and list</span> views of results.</li>
<li>Users were only <span style="background-color: lightyellow; font-weight: bold;">moderately successful distinguishing searches</span> within a single collection versus searching across all collections.</li>
<li>Most users <span style="background-color: lightyellow; font-weight: bold;">didn&#8217;t understand that they could remove their &#8220;narrow by&#8221; selections</span> in the breadcrumb trail.</li>
</ol>
<h3><a href="http://library.duke.edu/digitalcollections/redesign-feedback.html">Feedback Forms</a> and Other User Feedback</h3>
<ol>
<li>It&#8217;s unclear what the difference is between the<span style="background-color: lightyellow; font-weight: bold;"> &#8220;search this collection&#8221; box versus the &#8220;search all collections&#8221;</span> box.</li>
<li>Searching should enable people to discover more Duke content &amp; collections<span style="background-color: lightyellow; font-weight: bold;"> beyond the items that are in this particular system</span>.</li>
</ol>
<h3>Interviews with our Collection Sponsors</h3>
<p>Most highly desired improvements:</p>
<ol>
<li>Provide an <span style="background-color: lightyellow; font-weight: bold;">Advanced Search</span> option.</li>
<li>Return <span style="background-color: lightyellow; font-weight: bold;">collections in search results</span> in addition to items.</li>
<li>Return our <span style="background-color: lightyellow; font-weight: bold;">digital exhibits in search results</span>.</li>
<li>Better <span style="background-color: lightyellow; font-weight: bold;">distinguish intra- and cross-collection</span> searching.</li>
<li>Support the <span style="background-color: lightyellow; font-weight: bold;">exploration of a particular format (images, video) or time period (1960s)</span> regardless of the &#8216;collection&#8217;.</li>
<li>Have <span style="background-color: lightyellow; font-weight: bold;">persistent navigation </span>where users can explore broad categories from any page.</li>
<li>Enable users to <span style="background-color: lightyellow; font-weight: bold;">navigate from one item to the next</span> in a search result.</li>
<li>Let users mark items for later use (<span style="background-color: lightyellow; font-weight: bold;">shopping cart</span>).</li>
<li><span style="background-color: lightyellow; font-weight: bold;">Connect people to Duke&#8217;s relevant resources outside of this system</span> that match the keyword searches.  Especially important in &#8216;no results found&#8217; screen.<a href="http://library.duke.edu/trac/dc/wiki/Tripod/Redesign09/Interviews/Report"><br />
</a></li>
</ol>
<ul style="margin-left: 100px;">
<li><a href="http://library.duke.edu/trac/dc/wiki/Tripod/Redesign09/Interviews/Report">See all feedback</a> <em>(Duke library staff access only)</em></li>
</ul>
<h3><a href="http://cit.duke.edu/">CIT&#8217;s</a> Ideas for Helping our Collections be Used for Instruction</h3>
<ol>
<li>Enable users to <span style="background-color: lightyellow; font-weight: bold;">create their own collections </span>of items.</li>
<li>Provide a <span style="background-color: lightyellow; font-weight: bold;">slideshow view</span>.</li>
<li>Be able to <span style="background-color: lightyellow; font-weight: bold;">search our collections from within other systems</span> like Wordpress (Flickrpress model).</li>
</ol>
<h3>Other Ideas from the Implementation Team</h3>
<p>Here are some additional ideas we&#8217;ve had in our implementation team discussions:</p>
<ol>
<li>Add <span style="background-color: lightyellow; font-weight: bold;">search term highlighting</span> (to present the matching keyword in context), especially for texts</li>
<li>Provide navigable <span style="background-color: lightyellow; font-weight: bold;">visualizations of results</span> (timelines, maps)</li>
<li>Spell-check (<span style="background-color: lightyellow; font-weight: bold;">Did you mean?</span>) feature</li>
<li><span style="background-color: lightyellow; font-weight: bold;">RSS feed</span> for search results</li>
<li>Enable a <span style="background-color: lightyellow; font-weight: bold;">blank search</span> to retrieve every object in the system (or collection)</li>
</ol>
<h2>Inspiring Examples</h2>
<p>Below are a few example sites that provide compelling and inspiring solutions to some of the design challenges we&#8217;re facing.  See the <a href="https://seanaery.notableapp.com/workspaces/digitalcollections/sets/1384">whole set, with annotations, at Notable</a>.</p>
<p><script src='https://seanaery.notableapp.com/public/21421/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/21421/Flickr'>View this feedback (Flickr) on Notable</a></noscript></p>
<p><script src='https://seanaery.notableapp.com/public/21512/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/21512/Portal-to-Texas-History'>View this feedback (Portal to Texas History) on Notable</a></noscript></p>
<p><script src='https://seanaery.notableapp.com/public/21424/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/21424/Europeana'>View this feedback (Europeana) on Notable</a></noscript></p>
]]></content:encoded>
			<wfw:commentRss>http://library.duke.edu/blogs/digital-collections/2009/12/08/search-results-prototypes-analysis-inspiration/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Item Pages &#8211; Prototypes</title>
		<link>http://library.duke.edu/blogs/digital-collections/2009/11/25/item-pages-prototypes/</link>
		<comments>http://library.duke.edu/blogs/digital-collections/2009/11/25/item-pages-prototypes/#comments</comments>
		<pubDate>Wed, 25 Nov 2009 17:01:41 +0000</pubDate>
		<dc:creator>Sean Aery</dc:creator>
				<category><![CDATA[Website Redesign]]></category>

		<guid isPermaLink="false">http://library.duke.edu/blogs/digital-collections/?p=2671</guid>
		<description><![CDATA[
We have learned a lot about how to improve our item pages and we&#8217;ve gathered great examples from around the web as inspiration.  We&#8217;re now ready to share some wireframe prototypes.
There are four different wireframe prototypes here. Use the &#8216;Jump To&#8217; section at the top to look at versions A, B, C, and D.  Preferences? [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://gomockingbird.com/mockingbird/index.html?project=fc9eb1fc03ff475679fe322089824537e0f06380"><img class="alignnone size-full wp-image-2731" title="itempage-prototype-c-thumb" src="http://library.duke.edu/blogs/digital-collections/wp-content/uploads/2009/11/itempage-prototype-c-thumb1.jpg" alt="itempage-prototype-c-thumb" width="450" height="450" /></a></p>
<p>We have <a href="http://library.duke.edu/blogs/digital-collections/2009/10/19/item-pages-what-weve-learned/">learned a lot</a> about how to improve our item pages and we&#8217;ve <a href="http://library.duke.edu/blogs/digital-collections/2009/10/23/item-pages-inspiring-sites/">gathered great examples</a> from around the web as inspiration.  We&#8217;re now ready to share some wireframe prototypes.</p>
<p>There are <a href="http://gomockingbird.com/mockingbird/index.html?project=fc9eb1fc03ff475679fe322089824537e0f06380">four different wireframe prototypes here</a>. Use the &#8216;Jump To&#8217; section at the top to look at versions A, B, C, and D.  Preferences? Ideas? Concerns? Questions? Let us know what you think!</p>
<p>In addition to incorporating the feedback and ideas we&#8217;ve gathered so far, here are a few additional key things these designs attempt to address:<br />
<span id="more-2671"></span></p>
<ul>
<li>Bring the objects to life by enabling comments and both encouraging and capturing discourse around them in other places on the web (like Twitter, blogs, Facebook).  We&#8217;re looking at different services to help meet this objective.</li>
<li>Add a main navigation bar to help people more easily browse for <a href="http://library.duke.edu/blogs/digital-collections/2009/11/24/search-analysis-what-weve-learned/">the kinds of things we know they often look for via searches</a>.</li>
<li>Increase engagement with the site from the item pages by providing enticing leads to related stuff, whether entire collections or individual objects.  We want to see item pages less as destination pages, and more as jumping-off points to the rest of our content.</li>
<li>Let items belong to multiple &#8216;collections&#8217; though maintain strong context, branding, and contact info for the item&#8217;s primary collection.</li>
<li>Help the site better serve an international audience. We&#8217;re considering using the <a href="http://googleblog.blogspot.com/2009/09/translate-your-website-with-google.html">Google Translate widget</a> as one approach.  You can see it in action at sites like the <a href="http://www.museumoflondon.org.uk/English/">Museum of London</a> and <a href="http://www.powerhousemuseum.com/">Powerhouse Museum.</a></li>
<li>Incorporate new posts from our <a href="http://library.duke.edu/blogs/digital-collections">blog</a> &amp; <a href="http://twitter.com/dukedigitalcoll">Twitter account</a> to keep fresh content on the page and encourage people to connect with us.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://library.duke.edu/blogs/digital-collections/2009/11/25/item-pages-prototypes/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Search Analysis: What We&#8217;ve Learned</title>
		<link>http://library.duke.edu/blogs/digital-collections/2009/11/24/search-analysis-what-weve-learned/</link>
		<comments>http://library.duke.edu/blogs/digital-collections/2009/11/24/search-analysis-what-weve-learned/#comments</comments>
		<pubDate>Tue, 24 Nov 2009 16:27:28 +0000</pubDate>
		<dc:creator>Jessica Weber</dc:creator>
				<category><![CDATA[Assessment]]></category>
		<category><![CDATA[Website Redesign]]></category>

		<guid isPermaLink="false">http://library.duke.edu/blogs/digital-collections/?p=2371</guid>
		<description><![CDATA[

We’re taking a user-centered approach in planning the new Digital Collections web interface to ensure that our new design meets the needs and expectations of the people who use it.  One way to discover those needs is to analyze our web traffic in an attempt to decipher user intent when searching and browsing materials in [...]]]></description>
			<content:encoded><![CDATA[<p><script type="text/javascript"></script></p>
<div style="margin: 5px 0pt 5px 5px; float: right; width: 300px;"><a href="http://library.duke.edu/digitalcollections/adaccess.R0712/pg.1/"><img class="size-full wp-image-1831" title="Stop searching for records- just flip a lever; Ad*Access. Item R0712." src="http://library.duke.edu/digitalcollections/images/adaccess/R/R07/R0712/R0712-lrg.jpeg" alt="Stop searching for records- just flip a lever; Ad*Access. Item R0712." width="300" height="415" /></a></div>
<p>We’re taking a user-centered approach in planning the new Digital Collections web interface to ensure that our new design meets the needs and expectations of the people who use it.  One way to discover those needs is to analyze our web traffic in an attempt to decipher user intent when searching and browsing materials in our site.  Valuable patterns exist in this data that can help us optimize the site’s utility and performance by supporting actual user information-seeking behaviors.  Lou Rosenfeld recently wrote a terrific blog post about this “bottom-up analysis” on <em><a href="http://www.alistapart.com/articles/beyond-goals-site-search-analytics-from-the-bottom-up/">A List Apart</a></em>.</p>
<p>Using aggregated data from Google Analytics, we studied searches performed in our site from the period between May 1<sup>st</sup> and November 1<sup>st</sup> this year.  We found that Duke Digital Collections was searched approximately 131,000 times during this six month period; that’s an average of 717 searches per day.  The average user spent about three minutes on the site after entering his or her search query and viewed nearly four pages.  Visitors also adjusted their searches with keyword refinement 26% of the time.<span id="more-2371"></span></p>
<p>Only three percent of these unique searches were entered from the <a href="http://library.duke.edu/digitalcollections/">homepage</a>.  Eight percent— a whopping 11,121 unique searches—were entered directly from the <a href="http://library.duke.edu/digitalcollections/adaccess/">Ad*Access</a> portal page, while other popular start pages included the <a href="http://library.duke.edu/digitalcollections/hasm/">Historic American Sheet Music</a> collection (5%), the <a href="http://library.duke.edu/">Duke Libraries homepage</a> (5%), and the <a href="http://library.duke.edu/digitalcollections/eaa/">Emergence of Advertising in America</a> collection (3%).  Search engines and referring sites are responsible for the majority (81.8%) of DDC’s traffic, helping to explain this phenomenon.  Links from search engine results and links from social media services like StumbleUpon (19.2% of all referrals), Digg (1.9%),  Facebook (1.3%), and Twitter (0.9%) often lead users directly to item pages, bypassing our portals or homepages entirely.</p>
<p>Over 62,000 distinct searches were conducted, though we’ll focus on the top 500.  The most frequent search, “beauty,” was entered 643 times; by comparison, the #500 search, “clean,” was entered 24 times.  The bulk of keyword searches in our system (421 of the top 500, 84.2%) were entered in the form of single term queries.  These queries were largely topical and exploratory in nature, allowing the user to browse through various results.  In other cases, entire phrases or names of persons were entered into the system when a user had a more specific subject in mind (this was especially true for searches conducted in Historic American Sheet Music, where users often looked for specific titles of scores or names of composers).</p>
<p>Many searches (37 of the top 500), were for years, whether for a specific year or an entire decade.  Top examples include: 1920 (312), 1950 (147), 1920s (138), 1911 (99), 1850 (88), 1930 (88), 1920’s (87).</p>
<p>Other users search for items of a particular format (18 of the top 500 queries).  Examples:  music (187), advertising (127), book (76), poster (74), ad (75), cookbooks (68), sheet music (65), advertisements (58).</p>
<p>Some users search for entire collections by name&#8211;e.g. gamble (68), Gamble (50), adviews (44)&#8211;though the system currently doesn’t adequately support that function, since it only indexes and returns matching items.</p>
<p>And finally, some users appear to want a way to see everything that can possibly come back in search results, using queries like “a” (71), “all” (41), and the “*” wild card (32); our system does not currently perform this kind of retrieval.</p>
<p>Using the <a href="http://manyeyes.alphaworks.ibm.com/manyeyes/">Many Eyes</a> toolkit we have created three data visualizations of the most frequent search queries in two of our most popular collections, Ad*Access and Historic American Sheet Music, and one for the website at large.  Various search terms can easily be parsed at a glance, allowing one to see their frequency and trends.</p>
<p>A couple of caveats about the data that will help to qualify and clarify:</p>
<ul>
<li>Searches performed within the AdViews collection—launched July 21st—are mostly not      reflected in this data.  Up until Oct 21st, the AdViews site used a different method of searching (relying on  MIT’s SIMILE EXHIBIT code that searched on-the-fly after each keystroke without generating a new URL).</li>
<li>Links to search results (canned searches) count as searches.  Going to page 2 of search results counts as doing a new search, too, as does toggling list/grid view.</li>
</ul>
<p><strong>Top 500 Duke Digital Collections Search Terms</strong></p>
<p><a style="margin: 0pt; padding: 0pt;" href="http://manyeyes.alphaworks.ibm.com/manyeyes/visualizations/top-500-duke-digital-collections-s/comments/fab4d098ce2911debe43000255111976"> <img style="border: 1px solid #AF755D; margin: 0; padding-top: 10px; padding-bottom: 15px;" src="http://manyeyes.alphaworks.ibm.com/manyeyes/files/thumbnails/fa8429d4-ce29-11de-be43-000255111976.png?size=200x150" alt="Fa8429d4-ce29-11de-be43-000255111976" /> <img style="border: 0pt none; margin: 0pt; padding: 0pt; display: block; position: relative; top: -5px;" src="http://manyeyes.alphaworks.ibm.com/manyeyes/images/blog_this_caption.jpg" alt="Blog_this_caption" /></a></p>
<p><strong>Top 100 Historic American Sheet Music Search Terms</strong></p>
<p><a style="margin: 0pt; padding: 0pt;" href="http://manyeyes.alphaworks.ibm.com/manyeyes/visualizations/top-100-historic-american-sheet-mu/comments/3df2255cce2c11de9684000255111976"> <img style="border: 1px solid #AF755D; margin: 0; padding-top: 10px; padding-bottom: 15px;" src="http://manyeyes.alphaworks.ibm.com/manyeyes/files/thumbnails/3d998f32-ce2c-11de-9684-000255111976.png?size=200x150" alt="3d998f32-ce2c-11de-9684-000255111976" /> <img style="border: 0pt none; margin: 0pt; padding: 0pt; display: block; position: relative; top: -5px;" src="http://manyeyes.alphaworks.ibm.com/manyeyes/images/blog_this_caption.jpg" alt="Blog_this_caption" /></a></p>
<p><strong>Top 50 Ad*Access Search Terms</strong></p>
<p><a style="margin: 0pt; padding: 0pt;" href="http://manyeyes.alphaworks.ibm.com/manyeyes/visualizations/top-50-ad-access-search-terms-5-1-/comments/d4455b54ce2d11de9e24000255111976"> <img style="border: 1px solid #AF755D; margin: 0; padding-top: 10px; padding-bottom: 15px;" src="http://manyeyes.alphaworks.ibm.com/manyeyes/files/thumbnails/d423d7a4-ce2d-11de-94e9-000255111976.png?size=200x150" alt="D423d7a4-ce2d-11de-94e9-000255111976" /> <img style="border: 0pt none; margin: 0pt; padding: 0pt; display: block; position: relative; top: -5px;" src="http://manyeyes.alphaworks.ibm.com/manyeyes/images/blog_this_caption.jpg" alt="Blog_this_caption" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://library.duke.edu/blogs/digital-collections/2009/11/24/search-analysis-what-weve-learned/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Secrets of Duke Digital Collections &#8230; Revealed!</title>
		<link>http://library.duke.edu/blogs/digital-collections/2009/11/03/secrets-of-duke-digital-collections-revealed/</link>
		<comments>http://library.duke.edu/blogs/digital-collections/2009/11/03/secrets-of-duke-digital-collections-revealed/#comments</comments>
		<pubDate>Tue, 03 Nov 2009 14:22:08 +0000</pubDate>
		<dc:creator>Rich</dc:creator>
				<category><![CDATA[Announcements]]></category>

		<guid isPermaLink="false">http://library.duke.edu/blogs/digital-collections/?p=1941</guid>
		<description><![CDATA[
How do we make Duke Digital Collections happen?  Well, obviously, our secret is glamour, which comes as no surprise to those of you who know us.  But as with Miss Denney in this advertisement from our Ad*Access collection, there&#8217;s a bit more to it than that, and it takes a lot of work to get [...]]]></description>
			<content:encoded><![CDATA[<div style="margin: 5px 0pt 5px 5px; float: right; width: 166px;"><a href="http://library.duke.edu/digitalcollections/adaccess.BH1657/pg.1/"><img class="size-full wp-image-2061 alignnone" title="Her secret is glamour" src="http://library.duke.edu/blogs/digital-collections/wp-content/uploads/2009/11/secret-is-glamour.jpeg" alt="Her secret is glamour" width="166" height="418" /></a></div>
<p>How do we make Duke Digital Collections happen?  Well, obviously, our secret is glamour, which comes as no surprise to those of you who know us.  But as with Miss Denney in <a href="http://library.duke.edu/digitalcollections/adaccess.BH1657/pg.1/">this advertisement</a> from our <a href="http://library.duke.edu/digitalcollections/adaccess/">Ad*Access</a> collection, there&#8217;s a bit more to it than that, and it takes a lot of work to get there, especially since we try to avoid disturbing fatigue lines and &#8220;crepey throat&#8221; along the way.  (We know this ad is tiny here, but trust us, it&#8217;s worth clicking on to experience its full glory.)</p>
<p>We were recently asked to write about the Duke Digital Collections program for the <a href="http://library.duke.edu/magazine/ ">Duke University Libraries Magazine</a>.  The results appear in five articles in the Fall 2009 issue of the magazine, and you can read them online <a href="http://library.duke.edu/magazine/2009/11/digital-collections-at-duke/">here</a>.  Among other things, you can read about the history of digitization at Duke, the global reach of our digital collections, the creative interfaces we use to open the doors to our collections, the behind-the-scenes steps in the creation of a new digital collection, and how our digital collections are being used in the classroom.</p>
<p>Thanks to our friends at the magazine for giving us the opportunity to talk about the Duke Digital Collections program!</p>
]]></content:encoded>
			<wfw:commentRss>http://library.duke.edu/blogs/digital-collections/2009/11/03/secrets-of-duke-digital-collections-revealed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Item Pages: Inspiring Sites</title>
		<link>http://library.duke.edu/blogs/digital-collections/2009/10/23/item-pages-inspiring-sites/</link>
		<comments>http://library.duke.edu/blogs/digital-collections/2009/10/23/item-pages-inspiring-sites/#comments</comments>
		<pubDate>Fri, 23 Oct 2009 16:58:45 +0000</pubDate>
		<dc:creator>Sean Aery</dc:creator>
				<category><![CDATA[Website Redesign]]></category>

		<guid isPermaLink="false">http://library.duke.edu/blogs/digital-collections/?p=1801</guid>
		<description><![CDATA[
Before designing new item pages for our Digital Collections site redesign, we looked around the web to find exemplary sites to inspire us as we apply what we have learned while assessing our current item pages.
We looked for sites where items are presented with both clarity and context.  We also looked for sites that [...]]]></description>
			<content:encoded><![CDATA[<div style="float: right; width: 200px; margin: 5px 0 5px 5px;"><a href="http://library.duke.edu/digitalcollections/adaccess.BH1517/pg.1/"><img src="http://library.duke.edu/blogs/digital-collections/wp-content/uploads/2009/10/inspire-poetry.jpg" alt="&quot;Who knows, perhaps you may inspire poetry.&quot; Ad*Access. Item BH1517." title="&quot;Who knows, perhaps you may inspire poetry.&quot; Ad*Access. Item BH1517." width="200" height="278" class="size-full wp-image-1831" /></a></div>
<p>Before designing new item pages for our <a href="http://library.duke.edu/blogs/digital-collections/2009/09/08/redesigning-duke-digital-collections/">Digital Collections site redesign</a>, we looked around the web to find exemplary sites to inspire us as we apply <a href="http://library.duke.edu/blogs/digital-collections/2009/10/19/item-pages-what-weve-learned/">what we have learned while assessing our current item pages</a>.</p>
<p>We looked for sites where items are presented with both clarity and context.  We also looked for sites that present obvious ways to interact with an item (such as comment on it, bookmark it, or get a closer look) or help people discover related items to keep them engaged with exploring the site.</p>
<p>We love digital collections sites that are comparable to ours and have included some good ones here, but we were sure to look beyond library sites for inspiration as well.  Sites like <a href="http://flickr.com">Flickr</a>, <a href="http://youtube.com">YouTube</a>, and <a href="http://amazon.com">Amazon</a> are familiar to far more people than library sites, and their design patterns condition us all with certain expectations when we encounter any new or unfamiliar site.  The goal is to find good example solutions to the challenges present in each aspect of the design, and to use the best parts of each for inspiration.<br />
<span id="more-1801"></span></p>
<p>Here are 10 item page interfaces that inspire our thinking as we redesign ours.</p>
<p><script src='https://seanaery.notableapp.com/public/11791/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/11791/Item-Page-Flickr'>View this feedback (Item Page &#8211; Flickr) on Notable</a></noscript></p>
<p><script src='https://seanaery.notableapp.com/public/11784/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/11784/Item-Page-Example-ECU'>View this feedback (Item Page Example &#8211; ECU) on Notable</a></noscript></p>
<p><script src='https://seanaery.notableapp.com/public/11861/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/11861/Item-Page-Example-Brooklyn-Museum'>View this feedback (Item Page Example &#8211; Brooklyn Museum) on Notable</a></noscript></p>
<p><script src='https://seanaery.notableapp.com/public/11787/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/11787/Item-Page-Example-World-Digital-Library'>View this feedback (Item Page Example &#8211; World Digital Library) on Notable</a></noscript></p>
<p><script src='https://seanaery.notableapp.com/public/12166/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/12166/Item-Page-Example-Duke-Library-Catalog'>View this feedback (Item Page Example &#8211; Duke Library Catalog) on Notable</a></noscript></p>
<p><script src='https://seanaery.notableapp.com/public/11845/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/11845/Item-Page-Example-NLA-Trove'>View this feedback (Item Page Example &#8211; NLA Trove) on Notable</a></noscript></p>
<p><script src='https://seanaery.notableapp.com/public/11837/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/11837/Item-Page-Example-YouTube'>View this feedback (Item Page Example &#8211; YouTube) on Notable</a></noscript></p>
<p><script src='https://seanaery.notableapp.com/public/12035/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/12035/Item-Page-Example-Amazon'>View this feedback (Item Page Example &#8211; Amazon) on Notable</a></noscript></p>
<p><script src='https://seanaery.notableapp.com/public/12030/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/12030/Item-Page-Example-Worldcat'>View this feedback (Item Page Example &#8211; Worldcat) on Notable</a></noscript></p>
<p><script src='https://seanaery.notableapp.com/public/12027/thumbnail/med.js'></script><noscript><a href='https://seanaery.notableapp.com/website-feedback/12027/Item-Page-Example-UBdigit'>View this feedback (Item Page Example &#8211; UBdigit) on Notable</a></noscript></p>
<p>What do you think? Are there other sites with features we should emulate?  Leave us comments here on the blog, or <a href="http://www.notableapp.com/">create a free Notable account</a> and post your comments on the annotated screen captures above.</p>
<p>Related posts:</p>
<ol><a href="http://library.duke.edu/blogs/digital-collections/2009/10/19/item-pages-what-weve-learned/">Item Pages: What We&#8217;ve Learned</a></ol>
]]></content:encoded>
			<wfw:commentRss>http://library.duke.edu/blogs/digital-collections/2009/10/23/item-pages-inspiring-sites/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>AdViews: 3,000 New Commercials, Improved Access</title>
		<link>http://library.duke.edu/blogs/digital-collections/2009/10/21/adviews-3000-new/</link>
		<comments>http://library.duke.edu/blogs/digital-collections/2009/10/21/adviews-3000-new/#comments</comments>
		<pubDate>Wed, 21 Oct 2009 13:59:53 +0000</pubDate>
		<dc:creator>Jill Katte</dc:creator>
				<category><![CDATA[AdViews]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[advertising]]></category>

		<guid isPermaLink="false">http://library.duke.edu/blogs/digital-collections/?p=1671</guid>
		<description><![CDATA[I&#8217;m excited to announce that we&#8217;ve launched 3,000 new commercials in the AdViews digital collection on iTunes U.
http://library.duke.edu/digitalcollections/adviews/
This includes over 50 new products and brands, such as the American Association of Railroads, Burma Shave, Bounce, Eastern Airlines, Folgers, Glade, Pepto-Bismol, Prell, Sanka, and Zest. We&#8217;ve also added many new commercials for Crest, some fantastic Hasbro [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://library.duke.edu/digitalcollections/adviews.american_dental/"><img align="right" title="American Dental Association" src="http://library.duke.edu/digitalcollections/images/adviews/150/american_dental-150x150.png" alt="AdViews: American Dental Association" width="150" height="150" /></a>I&#8217;m excited to announce that we&#8217;ve launched 3,000 new commercials in the AdViews digital collection on iTunes U.<br />
<a href="http://library.duke.edu/digitalcollections/adviews/">http://library.duke.edu/digitalcollections/adviews/</a></p>
<p>This includes over 50 new <a href="http://library.duke.edu/digitalcollections/adviews/explore/">products and brands</a>, such as the American Association of Railroads, Burma Shave, Bounce, Eastern Airlines, Folgers, Glade, Pepto-Bismol, Prell, Sanka, and Zest. We&#8217;ve also added many new <a href="http://library.duke.edu/digitalcollections/adviews/search/results?t=crest">commercials for Crest</a>, some fantastic <a href="http://library.duke.edu/digitalcollections/adviews/search/results?t=hasbro">Hasbro toy commercials</a> from the 1970s, and much more.</p>
<p>The <a href="http://library.duke.edu/digitalcollections/adviews.highlights/">AdViews Highlights album</a> now features over 40 commercials with closed captioning and audio descriptions created by the <a href="http://ncam.wgbh.org/">National Center for Accessible Media</a> for users with hearing or vision impairments. Users can take advantage of these accessibility features using the Preferences and Controls menus in iTunes. We&#8217;ve also improved the indexing of the collection, making it easier to <a href="http://library.duke.edu/digitalcollections/search/results?t=adviews">search for and discover AdViews content</a> from the Libraries website.</p>
<p>Many thanks to Duke Libraries staff and interns, to Duke OIT, and to <a href="http://www.avgeeks.com/">A/V Geeks</a> for their excellent contributions to the project.</p>
<p>The digital collections team will promote some new AdViews commercials during the next few weeks on Twitter &#8212; follow us! <a href="http://twitter.com/dukedigitalcoll">http://twitter.com/dukedigitalcoll</a></p>
]]></content:encoded>
			<wfw:commentRss>http://library.duke.edu/blogs/digital-collections/2009/10/21/adviews-3000-new/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Item Pages: What We&#8217;ve Learned</title>
		<link>http://library.duke.edu/blogs/digital-collections/2009/10/19/item-pages-what-weve-learned/</link>
		<comments>http://library.duke.edu/blogs/digital-collections/2009/10/19/item-pages-what-weve-learned/#comments</comments>
		<pubDate>Mon, 19 Oct 2009 19:34:27 +0000</pubDate>
		<dc:creator>Sean Aery</dc:creator>
				<category><![CDATA[Assessment]]></category>
		<category><![CDATA[Website Redesign]]></category>

		<guid isPermaLink="false">http://library.duke.edu/blogs/digital-collections/?p=1511</guid>
		<description><![CDATA[We have been assessing our web interface to Digital Collections for some time using a healthy variety of evaluation techniques and soliciting ideas for a new &#38; improved interface.  Let&#8217;s first take a look at our item pages, with an annotated review of our current site:
&#38;amp;lt;a href=&#8221;https://seanaery.notableapp.com/website-feedback/10444/Item-Page-Existing-Interface&#8221; mce_href=&#8221;https://seanaery.notableapp.com/website-feedback/10444/Item-Page-Existing-Interface&#8221;&#38;amp;gt;View this feedback (Item Page &#8211; Existing [...]]]></description>
			<content:encoded><![CDATA[<p>We have been assessing our web interface to Digital Collections for some time using a healthy variety of evaluation techniques and soliciting ideas for a new &amp; improved interface.  Let&#8217;s first take a look at our item pages, with an annotated review of our current site:</p>
<p><script src="https://seanaery.notableapp.com/public/10444/thumbnail/med.js"></script><noscript>&amp;amp;lt;a href=&#8221;https://seanaery.notableapp.com/website-feedback/10444/Item-Page-Existing-Interface&#8221; mce_href=&#8221;https://seanaery.notableapp.com/website-feedback/10444/Item-Page-Existing-Interface&#8221;&amp;amp;gt;View this feedback (Item Page &#8211; Existing Interface) on Notable&amp;amp;lt;/a&amp;amp;gt;</noscript></p>
<p>Here&#8217;s what we have learned about the item pages, broken down by source:</p>
<h3>Web Analytics</h3>
<ol>
<li> Our most-accessed items get viewed mostly via <span style="color: #000000;">external links</span>, especially from <span style="font-weight: bold; background-color: lightyellow;">social media tools</span> (like StumbleUpon) and Google Images.</li>
<li>More than 3/4 of item page views are for the <span style="font-weight: bold; background-color: lightyellow;">medium image view</span> as opposed to the details view.</li>
</ol>
<h3>Usability Tests (Spring 2008)</h3>
<p><span id="more-1511"></span></p>
<ol>
<li>Users recognized the <span style="font-weight: bold; background-color: lightyellow;">social media tools</span> we chose to put in the &#8216;Add To&#8217; section, but didn&#8217;t anticipate using those particular services.</li>
<li>Users were able to easily <span style="font-weight: bold; background-color: lightyellow;">toggle between the details and the image view</span>.</li>
</ol>
<h3><a href="http://library.duke.edu/digitalcollections/redesign-feedback.html">Feedback Forms</a> and Other User Feedback</h3>
<ol>
<li>It&#8217;s good to have <span style="font-weight: bold; background-color: lightyellow;">multiple image sizes</span> available.</li>
<li>It&#8217;s unclear how to <span style="font-weight: bold; background-color: lightyellow;">get to all of the details</span> for an item.</li>
</ol>
<h3>Interviews with our Collection Sponsors</h3>
<p>Desired improvements:</p>
<ol>
<li>A <span style="font-weight: bold; background-color: lightyellow;">comment box</span> on items for users to contribute information.</li>
<li>Better <span style="font-weight: bold; background-color: lightyellow;">page-turning</span> for multi-paged items.</li>
<li>A way to <span style="font-weight: bold; background-color: lightyellow;">get a citation</span> for each item.</li>
<li>Connection to info about item&#8217;s <span style="font-weight: bold; background-color: lightyellow;">archival source collection</span>.</li>
<li>Easier <span style="font-weight: bold; background-color: lightyellow;">printing</span>, especially for multi-page items.</li>
<li>Clear <span style="font-weight: bold; background-color: lightyellow;">display options</span> for seeing the item and/or its metadata.</li>
<li>Multiple <span style="font-weight: bold; background-color: lightyellow;">export options</span>&#8211;especially for multi-page items.</li>
<li><span style="font-weight: bold; background-color: lightyellow;">Cleaner metadata display</span>, separating technical from descriptive metadata.</li>
<li><span style="font-weight: bold; background-color: lightyellow;">Customized presentation</span> of items for certain collections or item types.</li>
<li>Clarity to user what the <span style="font-weight: bold; background-color: lightyellow;">rights / acceptable uses</span> are for each item.</li>
<li>A way for items to be identified as <span style="font-weight: bold; background-color: lightyellow;">part of more than one &#8216;collection&#8217;</span>, especially broader collections like &#8216;documentary photographs&#8217; or &#8216;moving images.&#8217;</li>
</ol>
<h3><a href="http://cit.duke.edu/">CIT&#8217;s</a> Ideas for Helping our Images be Used for Instruction</h3>
<ol>
<li><span style="font-weight: bold; background-color: lightyellow;">Integration w/social media tools</span> (like ShareThis) and blogging platforms.</li>
<li> A <span style="font-weight: bold; background-color: lightyellow;">&#8216;download&#8217; button</span> (where allowed) w/multiple size options, esp for use in PPT.</li>
<li>Copyable &#8216;<span style="font-weight: bold; background-color: lightyellow;">Embed code</span>,&#8217; including citation.</li>
</ol>
<h3>Other Ideas from the Implementation Team</h3>
<p>To accompany all the ideas and info gathered above, here are a few additional ideas we&#8217;ve had in our implementation team discussions:</p>
<ol>
<li>Ability to <span style="font-weight: bold; background-color: lightyellow;">export items in PDF</span>, especially for multi-paged items</li>
<li>Automatically-generated &#8216;<span style="font-weight: bold; background-color: lightyellow;">Related Items</span>&#8216;</li>
<li><span style="font-weight: bold; background-color: lightyellow;">Integration with our internal metadata editor</span> so staff can edit from public interface</li>
<li>Permalinks with <span style="font-weight: bold; background-color: lightyellow;">URL handler</span></li>
<li><span style="font-weight: bold; background-color: lightyellow;">Full-text display</span> alongside images where available</li>
<li><span style="font-weight: bold; background-color: lightyellow;">Aesthetics</span>: page should be wider;  item title needs more prominence</li>
</ol>
<p>Now, what do we do with all this feedback?  First, we&#8217;ll share good example interfaces from around the web that tackle some of these same issues in various ways.  Once we&#8217;re feeling fully inspired, we&#8217;ll draw up some prototypes to share.  Stay tuned!</p>
]]></content:encoded>
			<wfw:commentRss>http://library.duke.edu/blogs/digital-collections/2009/10/19/item-pages-what-weve-learned/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
