<?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 &#187; Website Redesign</title>
	<atom:link href="http://library.duke.edu/blogs/digital-collections/category/website-redesign/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, 04 Nov 2009 21:32:13 +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>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>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>2</slash:comments>
		</item>
		<item>
		<title>Redesigning Duke Digital Collections</title>
		<link>http://library.duke.edu/blogs/digital-collections/2009/09/08/redesigning-duke-digital-collections/</link>
		<comments>http://library.duke.edu/blogs/digital-collections/2009/09/08/redesigning-duke-digital-collections/#comments</comments>
		<pubDate>Wed, 09 Sep 2009 02:21:39 +0000</pubDate>
		<dc:creator>Sean Aery</dc:creator>
				<category><![CDATA[Interface Features]]></category>
		<category><![CDATA[Website Redesign]]></category>

		<guid isPermaLink="false">http://library.duke.edu/blogs/digital-collections/?p=1061</guid>
		<description><![CDATA[
This fall, we&#8217;re redesigning the web interface to our Digital Collections.  And we want your help.
We unveiled our current interface back in January 2008, starting with a modest six collections, mostly of photographs and other images.  The system/website we built was pretty sufficient for that group of content.  It did some things well that marked [...]]]></description>
			<content:encoded><![CDATA[<div style="align:right; float: right;"><a href="http://library.duke.edu/digitalcollections/duc.ducpp19260901EC0182/pg.1/"><img class="alignright" title="Lilly Library under construction" src="http://library.duke.edu/digitalcollections/images/duc/dupp/thm/19260901EC0182.jpg" alt="" width="150" height="122" /></a></div>
<p>This fall, we&#8217;re redesigning the web interface to our Digital Collections.  And we want your help.</p>
<p>We unveiled our <a href="http://library.duke.edu/digitalcollections">current interface</a> <a href="http://library.duke.edu/blogs/digital-collections/2008/01/18/newsite/">back in January 2008</a>, starting with a modest six collections, mostly of photographs and other images.  The system/website we built was pretty sufficient for that group of content.  It did some things well that marked significant progress at the time: it let you search across collections, it gave you facets to narrow your search results, and it gave you nicely bookmarkable URLs for items and search results.</p>
<p>Fast forward 18 months to today.  Our Digital Collections Program is firmly established and clicking on all cylinders (<a href="http://library.duke.edu/blogs/digital-collections">see our past blog posts for a recap of the past year &amp; a half</a>).  We&#8217;re now hosting almost 30 collections in this system, and we&#8217;re introducing new collections all the time.  We have a diverse and growing range of digital formats like videos and books.   We have explored hosting content in places like <a href="http://www.youtube.com/dukelibdigitalcoll">YouTube</a>, <a href="http://deimos3.apple.com/WebObjects/Core.woa/Browse/new.duke.edu.2256724776">iTunes</a>, <a href="http://www.flickr.com/photos/dukeyearlook/">Flickr</a>, and <a href="http://www.archive.org/details/CartoonsFromThehindiPunch1904">Internet Archive</a>.  The Web has been rapidly evolving around us.  And our site has now been around long enough for us&#8211;and our users&#8211;to have kicked its proverbial tires to get a good sense of what it&#8217;s doing well versus where it&#8217;s falling short.  It&#8217;s getting pretty clear that we have outgrown this site.  It&#8217;s time to take it to the next level.</p>
<p>It&#8217;s the perfect time for a redesign.  Change is in the air.  Our team has been working hard on <a href="http://library.duke.edu/blogs/digital-collections/category/trident/">building our new repository, metadata editor tool, and index</a> (Codename: Trident), and all that behind-the-scenes wizardry opens up a wealth of opportunities for improving the ways that you, as someone who uses our website, will be able to discover our digital treasures.</p>
<p>We have some ideas of our own for improvements, and we&#8217;ll share them here on the blog shortly.  But we really want to hear from you about <em>your</em> ideas.  Join in the conversation here on this blog in the comments section.  Tune into this new category (<a href="http://library.duke.edu/blogs/digital-collections/category/website-redesign/">Website Redesign</a>), where we&#8217;ll share information throughout the fall, including updates, mockups, analysis, and more.   You can also <a href="http://library.duke.edu/digitalcollections/redesign-feedback.html">give us feedback privately at this page</a>, if you prefer.  Everything&#8217;s fair game, from aesthetics to information organization to functionality.</p>
<p>We&#8217;re looking forward to hearing from you soon!</p>
]]></content:encoded>
			<wfw:commentRss>http://library.duke.edu/blogs/digital-collections/2009/09/08/redesigning-duke-digital-collections/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>
