<?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>User Pathways &#187; Tagging</title>
	<atom:link href="http://userpathways.com/category/tagging/feed/" rel="self" type="application/rss+xml" />
	<link>http://userpathways.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Mon, 16 Aug 2010 20:58:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>What Google does</title>
		<link>http://userpathways.com/2009/04/what-google-does/</link>
		<comments>http://userpathways.com/2009/04/what-google-does/#comments</comments>
		<pubDate>Wed, 29 Apr 2009 13:47:05 +0000</pubDate>
		<dc:creator>James  Kelway</dc:creator>
				<category><![CDATA[Mental Models]]></category>
		<category><![CDATA[Metadata]]></category>
		<category><![CDATA[Semantic search]]></category>
		<category><![CDATA[Tagging]]></category>
		<category><![CDATA[Taxonomy]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[search technology]]></category>
		<category><![CDATA[Bradley Horowitz]]></category>
		<category><![CDATA[Google]]></category>

		<guid isPermaLink="false">http://userpathways.wordpress.com/2009/04/29/what-google-does/</guid>
		<description><![CDATA[&#160;



           
Bradley Horowitz at The Next Web 09 courtesy of 
           DailyM
&#160;
After Jeff Jarvis had his take on Google we had somebody from the inside – Bradley Horowitz.Horowitz was the man who advised Yahoo to [...]]]></description>
			<content:encoded><![CDATA[<p>&#160;</p>
<table cellspacing="0" cellpadding="2" width="700" border="0">
<tbody>
<tr>
<td valign="top" width="450"><a href="http://userpathways.com/2009/04/bradley-horowitz.jpg"><img title="bradley_horowitz" style="border-top-width: 0px; display: inline; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="300" alt="bradley_horowitz" src="http://userpathways.com/2009/04/bradley-horowitz-thumb.jpg" width="450" border="0" /></a>           <br /><a href="http://www.flickr.com/photos/dailym/sets/72157616775527895/" target="_blank"><br />
<h6>Bradley Horowitz at The Next Web 09 courtesy of </h6>
<p>           <a href="http://www.flickr.com/photos/dailym/sets/72157616775527895/" target="_blank">DailyM</a></a></a></td>
<td valign="top" width="28">&#160;</td>
<td valign="top" width="222">After <a href="http://userpathways.com/2009/04/22/tipping-point-beyond-20/" target="_blank">Jeff Jarvis</a> had his take on Google we had somebody from the inside – Bradley Horowitz.Horowitz was the man who advised Yahoo to buy Flickr and after redefining his role there he made them acquire Delicious. Previously he had formed Virage (video categorization engine) and sold it to Autonomy after dropping out of his degree at MIT Medialab where he worked on image categorisation technologies. <span id="more-427"></span></td>
</tr>
</tbody>
</table>
<p>&#160;</p>
</p>
<h6>&#160;</h6>
<p>It was no wonder with his background that metadata, context and categorisation formed an underlying theme to this talk. It was good to see these foundational elements of online user experience given the focus they deserve.</p>
<p><strong>Moore’s law and the aim of Google      <br /></strong>He stated that Google&#8217;s main perspective on technology was thinking big as a means of innovation. With this philosophy they have changed the world as we know it and their impact is massive. As silicon valley realised Moore’s law to be true, Google imagined a world where bandwidth, size and storage was not a problem. In doing so they created&#160; applications such as GMail.</p>
<p>Google’s aim is to provide excellent search to enable users to store and find everything. It is to solve one of the world’s biggest problems -that of information overload, its loss and its retrieval.</p>
<p><strong>Ubicomp is here      <br /></strong>He told of everyday devices that have achieved ubiquity &#8211; that can now record your entire life digitally. Ubiquity is here.&#160; The mobile phone is everywhere.</p>
<blockquote><p>The problem as he saw it was that you can record everything but you don&#8217;t get another life to review it all. The challenge is harvesting metadata and defining context to give meaning to what we do.</p>
</blockquote>
<p>So how do you use the information to a useful end? Horowitz (and Google) knows that the big problem is that we are dying from the start. Moments evaporate from the start. This fact drives Google to be fast. Latency is a key focus because time is of the essence. By being fast they give back the time to the world by speed of its services.</p>
<p><strong>Be aware of our human condition      <br /></strong>He told of, meditation, sleep, walking the dog that gives him perspective. A very pertinent point was that technology needs to adapt and enhance the human life. He asked how do we solve attention management? The moments of life that need revisiting amongst the morass of spam and junk we all wade through.</p>
<p>A key observation was that metadata is as important as the data itself. Even from biosignals. He stated that Wetware (using people’s minds and bodies as systems) will be as important as software or hardware.</p>
<p><a href="http://userpathways.com/2009/04/birdseye.jpg"><img title="birdseye" style="border-top-width: 0px; display: inline; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="333" alt="birdseye" src="http://userpathways.com/2009/04/birdseye-thumb.jpg" width="500" border="0" /></a></p>
<h6>Audience at The Next Web 09 courtesy of <a href="http://www.flickr.com/photos/dailym/sets/72157616775527895/" target="_blank">DailyM</a></h6>
<blockquote><p>Image understanding is an amazingly complex process if you expect to use machines to do this. Using humans enables it to be easy to create understanding around cognition of imagery. People can do this easily to give meaning to images and Flickr shows that by a simple means to ensure that the people can tag easily.</p>
</blockquote>
<p>Though I appreciate his statement I feel we have along way to go before the wisdom of crowds can be used effectively here.</p>
<p>He stressed that a few dedicated curators can create value for the majority. Indeed, the collective intelligence and interestingness creates a relevance metric that goes beyond just page rank algorythmns.&#160; We see this in blogs, twitter streams and facebook communities but the curators still control the quality. That is&#160; an important point I feel, and one that Google obviously realises.</p>
<p>Then he briefly showed a mental model that reflected the Google approach to data, starting at signal and working upwards.</p>
<ul>
<li>enlightenment </li>
<li>wisdom </li>
<li>knowledge </li>
<li>information </li>
<li>data </li>
<li>signal </li>
</ul>
<p>From a signal you may reach the pathway to enlightenment I guess, but it certainly has a clarity to it that is admirable.</p>
<p><strong>The web is broken      <br /></strong>What we did get from this talk was a refreshing personal perspective on the world of technology and how it affects us. He iterated that the conference had talked a lot about the current web, Twitter and real time search but he urged us to think about the <em>real</em> future.</p>
<p>In closing Horowitz stated how the browser is a bad model. It is not the optimal system to deliver the next web, the model is terribly broken, latency, code storage and caching are all frailties that have consumed countless lifetimes of development time.</p>
<p>He asked us to think about the ‘what if’ scenarios, take the long view and where the world is trending. Solving the problems that we expect to have tomorrow.</p>
<p><strong>Create space in life</strong>     <br />In many ways when somebody talks from Google you know they will not divulge what they do exactly, or certainly not their next step. They, like other successful companies, keep their products shrouded in mystery (ironic in this culture of open source and collaborative working don’t you think?).</p>
<p>With a slight nod to those who were wanting to know the next move he stated&#160; it will be Google Voice. A way of leveraging voicemail into the digital life and Gmail.</p>
<p>Closing the circle completely, he asked ‘how much do you want to invite tech into your life?’. He reminded us to create space in our lives.</p>
<p>That coming from Google was a surprise &#8211; or was it really? Their aim after all, is to make our lives easier to manage in the information age. Surely that can only be a good thing.</p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=What+Google+does+http://ankic.th8.us" title="Post to Twitter"><img class="nothumb" src="http://userpathways.com/wp-content/plugins/tweet-this/icons/tt-twitter.png" alt="Post to Twitter" /></a> <a class="tt" href="http://twitter.com/home/?status=What+Google+does+http://ankic.th8.us" title="Post to Twitter">Tweet This Post</a></p>]]></content:encoded>
			<wfw:commentRss>http://userpathways.com/2009/04/what-google-does/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The answer is in the interface</title>
		<link>http://userpathways.com/2008/06/the-answer-is-in-the-interface/</link>
		<comments>http://userpathways.com/2008/06/the-answer-is-in-the-interface/#comments</comments>
		<pubDate>Wed, 18 Jun 2008 19:45:24 +0000</pubDate>
		<dc:creator>James  Kelway</dc:creator>
				<category><![CDATA[Concept Models]]></category>
		<category><![CDATA[Design Theory]]></category>
		<category><![CDATA[Findability]]></category>
		<category><![CDATA[Information Architecture]]></category>
		<category><![CDATA[Interaction Design]]></category>
		<category><![CDATA[Mental Models]]></category>
		<category><![CDATA[Metadata]]></category>
		<category><![CDATA[Semantic search]]></category>
		<category><![CDATA[Tagging]]></category>
		<category><![CDATA[concept]]></category>

		<guid isPermaLink="false">http://userpathways.wordpress.com/2008/06/18/the-answer-is-in-the-interface/</guid>
		<description><![CDATA[&#160;




&#160;

A recent article by Alex Iskold brilliantly captures the separations of where we imagine semantic search should be and the reality. Even if it were trying to knock Google off a top spot, what he highlights is that it would be an unnecessary exercise.
Google does its thing very well. Few would argue with that. Alex [...]]]></description>
			<content:encoded><![CDATA[<p>&#160;</p>
<table cellspacing="0" cellpadding="2" width="700" border="0">
<tbody>
<tr>
<td valign="top" width="450"><a href="http://userpathways.com/2008/06/googlemaps.jpg"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="282" alt="googlemaps" src="http://userpathways.com/2008/06/googlemaps-thumb.jpg" width="450" border="0" /></a></td>
<td valign="top" width="28">&#160;</td>
<td valign="top" width="222">
<p>A <a href="http://www.readwriteweb.com/archives/semantic_search_the_myth_and_reality.php">recent article</a> by Alex Iskold brilliantly captures the separations of where we imagine semantic search should be and the reality. Even if it were trying to knock Google off a top spot, what he highlights is that it would be an unnecessary exercise.</p>
<p>Google does its thing very well. Few would argue with that. Alex suggests that semantic search should do something completely different&#8230;</p>
<p> <span id="more-243"></span></td>
</tr>
</tbody>
</table>
<p>&#160;</p>
</p>
<blockquote><p><em>To really showcase semantic search, these companies need to come up with innovative UIs that will help users to understand the power that is being put at their fingers.</em></p>
<p><em></em></p>
</blockquote>
<p>I also think it should display results differently, the interface should encourage an exploratory experience and allow lateral thought to occur during research. Iskold states we should move away from&#160; the search box, as this is the wrong type of input for a user.</p>
<p>&#160;</p>
<p><strong></strong></p>
<p><strong>Search Patterns</strong></p>
</p>
<p>Peter Morville is currently producing a book on search patterns and this will also highlight how facetted navigation enables the user to experience a different search journey. He has made the slides available <a href="http://flickr.com/photos/morville/collections/72157603785835882/">here</a> on Flickr.</p>
<p>If you look at the core of what should be shown is the relationships between items, that give relevance to the user&#8217;s query. Somehow a system needs to be designed that will reveal elements that have relationships and connections. Ontologies could be made, linking different data sets as if they were relational databases.</p>
<p>If a user found truly relevant and accurate information around an entity then a business objective could be fulfilled. Really targeted advertising would occur. Users are often more forgiving of adverts if what they see is relevant.</p>
<p>&#160;</p>
<p><strong></strong></p>
<p><strong>Images as a search device</strong></p>
<p>But the challenge is in the interface, how do you convey a fluid, &#8216;<a href="http://en.wikipedia.org/wiki/Noosphere">noosphere</a>&#8216;, visually? It has to be visual because the variety of content types are so different, and to scan and associate quickly &#8211; images could allow instant recognition.</p>
<p>&#160;</p>
<p><a href="http://www.ted.com/index.php/talks/view/id/129"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="208" alt="TED" src="http://userpathways.com/2008/06/ted.jpg" width="304" border="0" /></a></p>
<h6>Blaise Aguera y Arcas is an architect at Microsoft Live Labs, architect of Seadragon, and the co-creator of Photosynth</h6>
<p>&#160;</p>
<p>Recently <a href="http://www.shipsbiscuit.com/">Mike Laurie</a> wrote a post about the use of video, virals and such like and he ended the post highlighting the Photosynth software developed by Microsoft. The <a href="http://www.ted.com/index.php/talks/view/id/129">video</a> shows the potential of this software and it’s impressive. One quality is the ability of a system to collate images from Flickr that have been tagged with recognised terms and build those images around a 3D model.</p>
<p>&#160;</p>
<p>Another element is the resolution of some of these images is 300 megapixels allowing a user to zoom right into them and read or see the contents.</p>
<p>&#160;</p>
<p><a href="http://www.ted.com/index.php/talks/view/id/129"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="282" alt="photosynth" src="http://userpathways.com/2008/06/photosynth.jpg" width="450" border="0" /></a></p>
<h6>Photosynth showing Flickr images mapped to 3D models of the subject</h6>
<p>&#160;</p>
<p>If you think about this collation of files that have been tagged by a massive variety of users (from Flickr in this instance), it seems to be a big step to Tim Berners-Lee&#8217;s vision of the semantic web.</p>
<p>Sure these are only pictures, they are not documents, however when you think about the metadata in the file and how this can be organised to conform to a widely accepted mental model then this is really exciting.</p>
<p><strong></strong></p>
<p><strong>An interactive mental model</strong></p>
<p>Imagine an interactive concept model around a physical object, you could extract the related items around this and draw relationships between inter-linked entities. I recently designed a taxonomy for a science magazine, and it had to encompass every type of science from physics to psychology to civil engineering. How would you draw relationships between these fields?</p>
<p>Well, what I like about this model is that this would be a visual representation of a knowledge landscape (in this case using images) that could easily be with video, audio and standard web pages. It would also be a 3d representation that would encourage <strong><em>digital discovery. </em></strong></p>
<p>At the moment it is perhaps too flexible for your average user, but give it time. As more <a href="http://en.wikipedia.org/wiki/Digital_native">digital natives</a> reach maturity and form the majority of the browsing public, this interface will not phase them at all.</p>
<p><strong></strong></p>
<p><strong>Google&#8217;s repository of human entered queries</strong></p>
<p>We have a vast amount of data against document types about relationships between one and another, search engines have log files where keywords and most relevant results are displayed.</p>
<p>Around any search, even if it is a mathematical equation, there is a physical object that can be related to it. Be it the theory&#8217;s creator, university, or even the theory itself the physical entity (or even known concept) could form the basis of the visual model.</p>
<p>If we truly want to move towards a semantic web than this type of interface would offer a rich, interactive and flexible approach to showing layers of detail that would encourage digital discovery and serendipitous finding.</p>
<p>Producing a list of most relevant links is still a compromise to what we could display to our users. It could be far better to show a knowledge landscape for each query where there are paths to other areas of knowledge and layers of related data that can be sorted by a series of user interactions.</p>
<p>In a way Microsoft has produced a microfiche for the 21st century, the difference though is the librarians that have tagged it are now the users of the system and they create the content. The machine has enabled the creation of something that is entirely user&#160; generated but it will also help in organising this huge potential of harnessing the world’s knowledge.</p>
<p>&#160;</p>
<p><a href="http://userpathways.com/2008/06/googlemaps.jpg"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="282" alt="googlemaps" src="http://userpathways.com/2008/06/googlemaps-thumb.jpg" width="450" border="0" /></a></p>
<p>&#160;</p>
<p>Consider how Google are also integrating wikipedia entries to their maps and geo-locating photographs. By using the map, as mental model in this case, they are merely super imposing extra data types directly onto the two dimensional base.</p>
<p>Perhaps this is the greatest challenge to interaction designers and visual thinkers. Visually represent the knowledge available from an interlinked network of sources that are authorities around a subject area. As Alex Isold points out we are far from the solution yet.</p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=The+answer+is+in+the+interface+http://6w6ed.th8.us" title="Post to Twitter"><img class="nothumb" src="http://userpathways.com/wp-content/plugins/tweet-this/icons/tt-twitter.png" alt="Post to Twitter" /></a> <a class="tt" href="http://twitter.com/home/?status=The+answer+is+in+the+interface+http://6w6ed.th8.us" title="Post to Twitter">Tweet This Post</a></p>]]></content:encoded>
			<wfw:commentRss>http://userpathways.com/2008/06/the-answer-is-in-the-interface/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Building a metadata schema</title>
		<link>http://userpathways.com/2008/06/building-a-metadata-schema/</link>
		<comments>http://userpathways.com/2008/06/building-a-metadata-schema/#comments</comments>
		<pubDate>Sat, 07 Jun 2008 15:51:05 +0000</pubDate>
		<dc:creator>James  Kelway</dc:creator>
				<category><![CDATA[Design Practice]]></category>
		<category><![CDATA[Findability]]></category>
		<category><![CDATA[Metadata]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[Semantic search]]></category>
		<category><![CDATA[Tagging]]></category>
		<category><![CDATA[search technology]]></category>

		<guid isPermaLink="false">http://userpathways.wordpress.com/2008/06/07/building-a-metadata-schema/</guid>
		<description><![CDATA[



&#160;

A year ago I was involved in a major restructure of 7 major websites. Each had a new taxonomy and controlled vocabulary created. A clear vision of the direction of each site was drawn up and site maps and wireframes produced. The one problem we had, was there wasn&#8217;t a generic metadata schema that was [...]]]></description>
			<content:encoded><![CDATA[<table cellspacing="0" cellpadding="2" width="704" border="0">
<tbody>
<tr>
<td width="455"><a href="http://userpathways.com/2008/06/metadata-logos.jpg"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="200" alt="metadata-logos" src="http://userpathways.com/2008/06/metadata-logos-thumb.jpg" width="450" border="0" /></a></td>
<td valign="top" width="19">&#160;</td>
<td valign="top" width="228">
<p>A year ago I was involved in a major restructure of 7 major websites. Each had a new taxonomy and controlled vocabulary created. A clear vision of the direction of each site was drawn up and site maps and wireframes produced. The one problem we had, was there wasn&#8217;t a generic metadata schema that was adhered to. It was a combination of ad hoc, legacy tags. Some originated from the SEO team and some from the developers and database administrators on each site.</p>
<p> <span id="more-230"></span></td>
</tr>
</tbody>
</table>
<p><a href="http://userpathways.com/2008/06/metadata-logos.jpg"></a></p>
<p>&#160;</p>
<p>The problem was, to enable users (internal staff and external consumers) to be able to find what they needed and to discover content serendipitously, the metadata needed to be rigorously structured and adhere to recognised standards.</p>
<p>Various kinds of metadata were important to the sharing and re-use of articles, and this post will highlight these areas and also illustrate how we incorporated these into the metadata schema.</p>
<p>&#160;</p>
</p>
<h3><a name="_Toc172371113"></a>The importance of metadata</h3>
<p><strong></strong></p>
<p>The lack of metadata in a file, adversely affects search engine retrieval but also the working efficiency in collaborative teams. Data is lost, assets are not published and effort in creation is wasted. Ensuring effective metadata implementation in the documents we create and publish results in gaining competitive advantage in the search domain but also an increased efficiency in our working practice.</p>
<p>Without metadata management intellectual property rights become eroded, and liability increases. Files such as an image, PDF, video or audio all need to be tagged to provide the user or employee a method in finding valuable content.</p>
<p>A set of Metadata Standards should govern the implementation of consistent and uniform metadata architecture. Consistency in metadata is important to enable information sharing across an organisation and to make optimal use of document management tools which rely upon this.</p>
<h3><a name="_Toc172371114"></a></h3>
<p>For metadata to be effective, it must be incorporated into the workflow from creation to publication. This emphasises the importance of any content producer making a concerted effort to synchronise their information management.</p>
<p>There are significant contributors in metadata standards and after analysis the following organisation’s standards formed a basis for the metadata schema.</p>
<p>&#160;</p>
<p>These are:</p>
<ul>
<li><a href="http://dublincore.org/">Dublin Core Metadata Initiative (DCMI)</a> </li>
<li><a href="http://www.iptc.org/pages/index.php">International Press Telecommunications Council (IPTC)</a> </li>
<li><a href="http://www.prismstandard.org/">Publishing Requirements for Industry Standards Metadata (PRISM)</a> </li>
</ul>
<p>These standards are evident in the following formats that create types of metadata:</p>
<ul>
<li><a href="http://www.adobe.com/products/xmp/">Adobe Software’s Extensible Metadata Platform (XMP)</a> </li>
<li><a href="http://en.wikipedia.org/wiki/Exif">Exchangeable Image File Format (EXIF)</a> </li>
<li><a href="http://www.w3.org/RDF/">Resource Description Framework (RDF)</a> </li>
</ul>
<p>&#160;</p>
<p>To aid in classification of file format types we used the <a href="http://www.iana.org/">Internet Assigned Numbers Authority (IANA)</a> to give us a definitive list of file types. Its list, the <a href="http://www.iana.org/assignments/media-types/">Multipurpose Internet Mail Extensions (MIME)</a> covers various formats that were used and may be used in the future. All other taxonomical types of labels (countries, regions etc) we looked towards the <a href="http://www.iso.org/iso/about.htm">ISO</a> for their classifications.</p>
<h3><a name="_Toc172371115"></a></h3>
<p><a name="_Toc172371116"></a><a name="_Toc172347302"></a>There are four main areas of metadata in terms of semantic grouping.</p>
<p>&#160;</p>
<p>These are:</p>
<ul>
<li><strong>Descriptive metadata</strong> – Describes the contents of a file </li>
<li><strong>Administrative metadata</strong> – Data that can not be retrieved or inferred from the content and pertains to management of the content within a system </li>
<li><strong>Rights metadata</strong> – Asserts the ownership of the content, who owns it and who may distribute it and usually pertains to the usage of the document. </li>
<li><strong>Technical metadata</strong> – data about the physical properties of the content </li>
</ul>
<p>All four areas have specific use for different reasons. The descriptive quality helps the item properties to be found either by search or by a user interface element on the page. This can be online and also offline in an application such as Adobe Bridge.</p>
<p>&#160;</p>
<h3>&#160;</h3>
<h3>Drafting a schema</h3>
<p><strong></strong></p>
<p><a name="_Toc172371118"></a><a name="_Toc172370825"></a><a name="_Toc172367926"></a><a name="_Toc172358013"></a><a name="_Toc172347304"></a>The schema was designed to incorporate the four main uses of metadata. These different facets to metadata result in different uses throughout the workflow of a publishing process.</p>
<p><a name="_Toc172371119"></a><a name="_Toc172370826"></a><a name="_Toc172367927"></a><a name="_Toc172358014"></a><a name="_Toc172347305"></a>These are revealed through tools the Adobe suite of applications and in the content of the websites where the ability to find our information is paramount to the quality of the user experience. The importance of classifying different aspects of our content is becoming increasingly important as new technologies based on the XML platform come into fruition.</p>
<p><a name="_Toc172371120"></a><a name="_Toc172370827"></a><a name="_Toc172367928"></a><a name="_Toc172358015"></a><a name="_Toc172347306"></a>The properties are unique and their use is dependent upon the content of the resource that is being tagged.</p>
<p>The list below outlines what we thought was of most use to be tagged from the moment content was created to the moment it became published.</p>
<p>&#160;</p>
<p>&#160;</p>
<table cellspacing="0" cellpadding="2" width="400" border="0">
<tbody>
<tr>
<td valign="top" width="200"><strong>Descriptive Properties</strong></td>
<td valign="top" width="200">&#160;</td>
</tr>
<tr>
<td valign="top" width="200">Headline</td>
<td valign="top" width="200">Information Type (set)</td>
</tr>
<tr>
<td valign="top" width="200">Keywords</td>
<td valign="top" width="200">Industry Sector</td>
</tr>
<tr>
<td valign="top" width="200">Description</td>
<td valign="top" width="200">Audience</td>
</tr>
<tr>
<td valign="top" width="200">Subject</td>
<td valign="top" width="200">Coverage</td>
</tr>
<tr>
<td valign="top" width="200">Entity Type&#160; (set)</td>
<td valign="top" width="200">Genre</td>
</tr>
<tr>
<td valign="top" width="200">Scene</td>
<td valign="top" width="200">Location created</td>
</tr>
<tr>
<td valign="top" width="200">Language</td>
<td valign="top" width="200">Predominant colour</td>
</tr>
<tr>
<td valign="top" width="200"><strong>Administrative Properties</strong></td>
<td valign="top" width="200">&#160;</td>
</tr>
<tr>
<td valign="top" width="200">Unique ID</td>
<td valign="top" width="200">Title</td>
</tr>
<tr>
<td valign="top" width="200">Relation</td>
<td valign="top" width="200">Date Created</td>
</tr>
<tr>
<td valign="top" width="200">Date Modified</td>
<td valign="top" width="200">Date Published</td>
</tr>
<tr>
<td valign="top" width="200">Contact Information (set)</td>
<td valign="top" width="200">Job ID</td>
</tr>
<tr>
<td valign="top" width="200">Instructions</td>
<td valign="top" width="200">Description of writer</td>
</tr>
<tr>
<td valign="top" width="200"><strong>Rights Properties</strong></td>
<td valign="top" width="200">&#160;</td>
</tr>
<tr>
<td valign="top" width="200">Creator</td>
<td valign="top" width="200">Creator Job Title</td>
</tr>
<tr>
<td valign="top" width="200">Credit Line</td>
<td valign="top" width="200">Publisher</td>
</tr>
<tr>
<td valign="top" width="200">Copyright Notice</td>
<td valign="top" width="200">License Contact</td>
</tr>
<tr>
<td valign="top" width="200">Model Release</td>
<td valign="top" width="200">Property Release</td>
</tr>
<tr>
<td valign="top" width="200">Other Third Party Rights</td>
<td valign="top" width="200">Usage Rights</td>
</tr>
<tr>
<td valign="top" width="200">Provider</td>
<td valign="top" width="200">Source</td>
</tr>
<tr>
<td valign="top" width="200"><strong>Technical Properties</strong></td>
<td valign="top" width="200">&#160;</td>
</tr>
<tr>
<td valign="top" width="200">Format</td>
<td valign="top" width="200">Colour Space</td>
</tr>
<tr>
<td valign="top" width="200">Orientation</td>
<td valign="top" width="200">Maximum size</td>
</tr>
<tr>
<td valign="top" width="200">Original file</td>
<td valign="top" width="200">Image</td>
</tr>
<tr>
<td valign="top" width="200">Still Image</td>
<td valign="top" width="200">Moving Image</td>
</tr>
<tr>
<td valign="top" width="200">Text property</td>
<td valign="top" width="200">Sound</td>
</tr>
</tbody>
</table>
<p>&#160;</p>
<p>&#160;</p>
<p>The image below shows exactly how these fields are applied in practice.</p>
<p>&#160;</p>
<p><a href="http://userpathways.com/2008/06/cw-metadata.jpg"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="572" alt="page with metadata labels applied" src="http://userpathways.com/2008/06/cw-metadata-thumb.jpg" width="446" border="0" /></a></p>
<p>&#160;</p>
<h3>Risks of not managing your metadata</h3>
<p><strong></strong></p>
<p>Unless a unified metadata strategy is initiated there are risks that;</p>
<ol>
<li><strong>The data communication between enterprise applications will be flawed</strong>. Thereby negating any efficiency that may be gained through hardware upgrades, workflow will be inefficient, content will reside in silos . </li>
</ol>
<ol>
<li><strong>The investment of designing taxonomies needs to be implemented at a technical level and this requires taxonomy management and data architecture. </strong>Not following up the investment of a metadata implementation by employing a data architect or someone responsible for metadata management is a critical weakness in the enterprise&#8217;s information management. </li>
</ol>
<ol>
<li><strong>Little or no use can be made of existing content and it often presents a valuable commercial resource.</strong> As the file has substandard metadata we immediately lose our content but we need to profit from its creation and value. Without a way of implementing a schema, content is effectively lost as soon as it is created. </li>
</ol>
<p>With so many content creators working daily, the management of this information is our most important challenge. The content needs to be found easily, both internally amongst colleagues and externally amongst users.</p>
<p>&#160;</p>
<h3>The future</h3>
<p>Certain properties in the schema pave the way for future search technologies. For instance entity type (such as brand, product, location, event) are complex in their variety. However this label allows that complexity of context to be stated and clarified.</p>
<p>Perhaps its for this reason that I see metadata being the foundation of semantic search. Only with a rich metadata schema that incorporates several different facets will we start to enjoy highly advanced searches over content that has inherent relationships. The challenge for interaction&#160; and interface designers is to design the interface to be intuitive and allow searching in a unique, non-text field way, that is more exploratory than is possible at present.</p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=Building+a+metadata+schema+http://cftpk.th8.us" title="Post to Twitter"><img class="nothumb" src="http://userpathways.com/wp-content/plugins/tweet-this/icons/tt-twitter.png" alt="Post to Twitter" /></a> <a class="tt" href="http://twitter.com/home/?status=Building+a+metadata+schema+http://cftpk.th8.us" title="Post to Twitter">Tweet This Post</a></p>]]></content:encoded>
			<wfw:commentRss>http://userpathways.com/2008/06/building-a-metadata-schema/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Optimising images to ensure findability</title>
		<link>http://userpathways.com/2008/06/optimising-images-to-ensure-findability/</link>
		<comments>http://userpathways.com/2008/06/optimising-images-to-ensure-findability/#comments</comments>
		<pubDate>Mon, 02 Jun 2008 19:46:53 +0000</pubDate>
		<dc:creator>James  Kelway</dc:creator>
				<category><![CDATA[Content Management]]></category>
		<category><![CDATA[Design Practice]]></category>
		<category><![CDATA[Findability]]></category>
		<category><![CDATA[Metadata]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[Tagging]]></category>
		<category><![CDATA[image tagging]]></category>

		<guid isPermaLink="false">http://userpathways.wordpress.com/2008/06/02/optimising-images-to-ensure-findability/</guid>
		<description><![CDATA[&#160;




&#160;
Tagging images at source enables a standard to be reached when all images are used during a production process, both for print and online. If they are tagged properly, valuable metadata can be captured inside the JPEG file that can be read by applications later, either on or off line.   



&#160;
 Optimising images [...]]]></description>
			<content:encoded><![CDATA[<p>&#160;</p>
<table cellspacing="0" cellpadding="2" width="700" border="0">
<tbody>
<tr>
<td valign="top" width="450"><a href="http://userpathways.com/2008/06/clip-image0024.jpg"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="278" alt="Rhubarb image" src="http://userpathways.com/2008/06/clip-image0024-thumb.jpg" width="450" border="0" /></a></td>
<td valign="top" width="28">&#160;</td>
<td valign="top" width="222">Tagging images at source enables a standard to be reached when all images are used during a production process, both for print and online. If they are tagged properly, valuable metadata can be captured inside the JPEG file that can be read by applications later, either on or off line.  <span id="more-224"></span> </td>
</tr>
</tbody>
</table>
<p>&#160;</p>
<p> Optimising images enables;
</p>
<ul>
<li><strong>· speedy retrieval of images from within an image archive</strong> </li>
<li><strong>· resource sharing across different departments or companies, allowing a greater library of images available to all </strong></li>
<li><strong>· Metadata inclusion within the files themselves. Enabling a higher level of findability when the files are used online within websites</strong> </li>
</ul>
<p>&#160;</p>
<p>To ensure that this occurs, guidelines should be followed by the image creators and those who manage the administration of these images. As tagging images can be highly subjective the guidelines drawn up here are designed to be quick and simple to create within the Photoshop File info panel.There are four main fields that need descriptive information to ensure images hold metadata that will provide SEO benefit and enable the files to be found easily.The fields are;</p>
<ul>
<li><strong>· OBJECT</strong> – What the image is of. Is it a person, animal, logo, building or machinery? </li>
<li><strong>· LOCATION</strong> – Where the photograph was taken, this is an entity type that helps searching for specific images around a subject area by specifying geographic place. For images such as graphics, this descriptor will not be necessary. </li>
<li><strong>· DATE</strong> – The date on which the image was created. </li>
<li><strong>· REASON</strong> – The purpose for the image being created and what the image illustrates (seen in the description field below). This is another entity type. </li>
<li><strong>· KEYWORDS</strong> – This enables searching for the image within an archive and externally </li>
</ul>
<p>&#160;</p>
<p><a href="http://userpathways.com/2008/06/clip-image0024.jpg"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="343" alt="Rhubarb image" src="http://userpathways.com/2008/06/clip-image0024-thumb.jpg" width="556" border="0" /></a></p>
<p>&#160;</p>
<p>The image above has been taken for use in a magazine and online. As it is a generic image of food there is also a good chance that it could be searched for. Once the image has been downloaded from the camera it is here where the initial information needs to be added via an application, preferably Photoshop.Using the <strong>File Info</strong> command a box will appear like the example shown below. Within the first option, Description, all the metadata can be added that will aid SEO and will be maintained when taken into other applications such as <a href="http://www.fotoware.com/">Fotoware</a>. The first option in the menu (description) uses the metadata to populate other areas, such as IPTC info areas further down the option list.</p>
<p>&#160;</p>
<h3><a name="_Toc190251660"></a></h3>
<p><strong></strong></p>
<p><a href="http://userpathways.com/2008/06/clip-image002.jpg"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="304" alt="Photoshop file info interface" src="http://userpathways.com/2008/06/clip-image002-thumb.jpg" width="404" border="0" /></a></p>
<p>&#160;</p>
<p>&#160;</p>
<h4>1. Document title field</h4>
<p><a href="http://userpathways.com/2008/06/clip-image004.jpg"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="34" alt="document title field" src="http://userpathways.com/2008/06/clip-image004-thumb.jpg" width="244" border="0" /></a></p>
<p>This is effectively the <strong>OBJECT</strong> attribute mentioned earlier. It must be a concise description of the image contents in as few words as is possible. This will also form the JPG file name and for this reason has important SEO implications. In this example the image is called <strong>rhubarb_diced.jpg</strong>. The author’s information can also be added under this field.</p>
<p>&#160;</p>
<h4>2. Description field</h4>
<p><a href="http://userpathways.com/2008/06/clip-image005.jpg"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="56" alt="description field" src="http://userpathways.com/2008/06/clip-image005-thumb.jpg" width="448" border="0" /></a></p>
<p>This is the area that holds information about the <strong>LOCATION</strong> and <strong>REASON</strong> for the image’s existence. It also holds information regarding the <strong>DATE</strong>. The description should be targeted and concise. The description field should not be used as a further way to inform the art editors on the picture’s usage. This should be done in a separate document as all date within file info refers to metadata and will remain with the image after it has left the production desk.</p>
<p>&#160;</p>
<h4>3. Keywords field</h4>
<p><a href="http://userpathways.com/2008/06/clip-image007.jpg"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="73" alt="keywords field" src="http://userpathways.com/2008/06/clip-image007-thumb.jpg" width="244" border="0" /></a></p>
<p>For search engine optimisation and search through the Fotoware’s online interface &#8211; FotoWeb. These <strong>keywords</strong> are really important as they define the ease in which a user can find the appropriate image.</p>
<p>&#160;</p>
<p><a href="http://userpathways.com/2008/06/clip-image009.jpg"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="321" alt="fotoweb interface" src="http://userpathways.com/2008/06/clip-image009-thumb.jpg" width="427" border="0" /></a></p>
<p>&#160;</p>
<p>The image above shows a user searching for images that have been tagged ‘Langley Vale Farm’ and Fotoweb has returned 640 results. To narrow the search the categories list on the left hand side enables a user to drill down into results that have been put into relevant sections.</p>
<p>&#160;</p>
<p><a href="http://userpathways.com/2008/06/clip-image012.jpg"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="324" alt="fotoweb interface" src="http://userpathways.com/2008/06/clip-image012-thumb.jpg" width="430" border="0" /></a></p>
<p>&#160;</p>
<p>Clicking on ‘Land’ enables the user to see the 18 images that have the keywords associated to them. Clicking on a thumbnail allows the user to preview the image and also to examine the metadata. Here we can see that the term ‘Langley Vale’ has revealed the image of the farm on the Langley Vale estate.</p>
<p>&#160;</p>
<p><a href="http://userpathways.com/2008/06/clip-image016.jpg"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="328" alt="fotoweb detail page" src="http://userpathways.com/2008/06/clip-image016-thumb.jpg" width="436" border="0" /></a></p>
<p>&#160;</p>
<h4>4. Copyright field</h4>
<p>It is important that the correct copyright information is displayed and Photoshop can help ratify if a copyright license agreement is in place. The © logo will appear next to the file name of the Photoshop file. The file info panel will allow the creator or the picture editor to establish what copyright information is in place.</p>
<p>&#160;</p>
<p><a href="http://userpathways.com/2008/06/clip-image018.jpg"><img style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="297" alt="image of copyright pic in Photoshop" src="http://userpathways.com/2008/06/clip-image018-thumb.jpg" width="428" border="0" /></a></p>
<p>&#160;</p>
<h3><a name="_Toc190251665"></a></h3>
<p>Where possible, images should be tagged following the <em>what</em> (<strong>OBJECT</strong>), <em>when</em> (<strong>DATE</strong>), <em>where</em> (<strong>LOCATION</strong>) and <em>why</em> (<strong>REASON</strong>) of the image. Where images have rights management issues keywords and copyright information will help give a minimum standard to the tagging of images.If this data is within the JPEG of an image then there is a much higher chance of the images appearing in a search engine results page (SERP). Tagging images this way now, also helps in maintaining a standardised approach to tagging of images that will ensure placement in SERPs in the future as crawlers become more adept at reading metadata from different file types.</p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=Optimising+images+to+ensure+findability+http://cftpk.th8.us" title="Post to Twitter"><img class="nothumb" src="http://userpathways.com/wp-content/plugins/tweet-this/icons/tt-twitter.png" alt="Post to Twitter" /></a> <a class="tt" href="http://twitter.com/home/?status=Optimising+images+to+ensure+findability+http://cftpk.th8.us" title="Post to Twitter">Tweet This Post</a></p>]]></content:encoded>
			<wfw:commentRss>http://userpathways.com/2008/06/optimising-images-to-ensure-findability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
