<?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>Spellbound Blog &#187; controlled vocabularies</title>
	<atom:link href="http://www.spellboundblog.com/category/controlled-vocabularies/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.spellboundblog.com</link>
	<description>Archives, Digital Humanities, Cultural Heritage, Technology</description>
	<lastBuildDate>Mon, 06 Feb 2012 14:49:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>LIFE Photo Archive Digitized and Put Online by Google</title>
		<link>http://www.spellboundblog.com/2008/11/22/life-photo-archive-digitized-and-put-online-by-google/</link>
		<comments>http://www.spellboundblog.com/2008/11/22/life-photo-archive-digitized-and-put-online-by-google/#comments</comments>
		<pubDate>Sat, 22 Nov 2008 07:00:12 +0000</pubDate>
		<dc:creator>Jeanne</dc:creator>
				<category><![CDATA[controlled vocabularies]]></category>
		<category><![CDATA[digitization]]></category>
		<category><![CDATA[funding]]></category>
		<category><![CDATA[metadata]]></category>
		<category><![CDATA[photography]]></category>
		<category><![CDATA[search]]></category>

		<guid isPermaLink="false">http://www.spellboundblog.com/2008/11/22/life-photo-archive-digitized-and-put-online-by-google/</guid>
		<description><![CDATA[In news that would make any fan of old photographs drool, the Official Google Blog has announced that the LIFE Photo Archive is now available on Google Image Search.  The LIFE Photo Archive&#8217;s home page is neatly organized to encourage you to browse for images by decade, famous people and topics. There really is something [...]<p>This post is from from: <a href="http://www.spellboundblog.com">Spellbound Blog</a>.<br/><br/><a href="http://www.spellboundblog.com/2008/11/22/life-photo-archive-digitized-and-put-online-by-google/">LIFE Photo Archive Digitized and Put Online by Google</a></p>
]]></description>
			<content:encoded><![CDATA[<p><a href="http://images.google.com/hosted/life/l?imgurl=4be14877a8ea4f88" title="TimeInc: Martha Graham, photo by Gjon Mili, 1941"><img src="http://www.spellboundblog.com/wp-content/uploads/2008/11/martha-graham.jpg" alt="Martha Graham" width="230" align="right" height="292" /></a>In news that would make any fan of old photographs drool, the <a href="http://googleblog.blogspot.com/" title="Official Google Blog">Official Google Blog</a> has announced that the <a href="http://googleblog.blogspot.com/2008/11/life-photo-archive-available-on-google.html" title="LIFE Photo Archive available on Google Image Search">LIFE Photo Archive is now available on Google Image Search</a>.  The <a href="http://images.google.com/hosted/life" title="LIFE Photo Archive">LIFE Photo Archive&#8217;s home page</a> is neatly organized to encourage you to browse for images by decade, famous people and topics.</p>
<p>There really is something for everyone here. I picked this striking image of <a href="http://en.wikipedia.org/wiki/Martha_Graham" title="Wikipedia: Martha Graham">Martha Graham</a> because I love modern dance, but there are also images of war, fashion, sports, landscapes, architecture and tons more. The images currently posted stretch from the 1750s through 2003 and include many that have never before been published.</p>
<p>It is also worth noting that not everything in this collection is a photograph. I found illustrated pages from books like the <a href="http://images.google.com/hosted/life/l?imgurl=3e8435ecdfee184b" title="Queen Summer">Queen Summer by Walter Crane</a>. I also found illustrations like this one of <a href="http://images.google.com/hosted/life/l?imgurl=f218f88474dca5ee" title="Temple of Artemis: Ephesus, Turkey">the ancient temple of Artemis in Ephesus, Turkey</a>.</p>
<p>From the text in Google&#8217;s blog post, it sounds as if Google is doing the digitizing &#8211; while LIFE Inc (or their parent company <a href="http://www.timeinc.com" title="Time Inc">Time Inc</a>) will profit from the sale of prints. The current posted photos represent 20% of all the photos. Ultimately the photo archive is expected to be about 10 million images and stretch to the present day.</p>
<p><a href="http://life.qoop.com/images/13051022" title="TimeInc: Trees in Snow"><img src="http://www.spellboundblog.com/wp-content/uploads/2008/11/tree-snow.jpg" alt="TimeInc: St. Moritz, Switzerland, February 1947" align="left" /></a>TimeInc has partnered with <a href="http://www.qoop.com/" title="QOOP">QOOP</a> to sell framed fine art photographs via links directly from each of the LIFE photo pages within Google. Take a look at the page dedicated to selling you a  <a href="http://life.qoop.com/images/13051022" title="Framed LIFE photo: St. Moritz, Switzerland in 1947">framed art print of St. Moritz, Switzerland in 1947</a>.</p>
<p>I had not heard of QOOP before, but they seem to have a number of <a href="https://my.qoop.com/design/partner_page.php" title="QOOP Partner Options">options available for those who want to be their partner</a>. QOOP also wanted me to join their &#8216;Social Commerce Revolution&#8217;. In order to join the revolution I had to create an account (it is free and easy it pointed out). To create my account I had to give them my email address, password and birth date. Not so bad. On the next screen they required that I enter my mailing address and phone number. I don&#8217;t really want to give them this information &#8211; but I am curious about this revolution I have been promised. And when I was done &#8211; a whole lot of nothing happened. I think that I am supposed to use QOOP to create and market products. Is it an affiliate program? Is it an artsier <a href="http://www.cafepress.com" title="CafePress">CafePress</a>? Do I need to contribute my own images or can I use those of others? I am still not sure.</p>
<p>I do like their integration with the LIFE images, but I think that there is clearly more work to be done before they are going to foster a &#8216;Social Commerce Revolution&#8217; anytime soon.</p>
<p><a href="http://www.timeinc.com/pressroom/detail.php?id=releases/11182008.php" title="TimeInc Press Release">Time Inc&#8217;s press release</a> includes the following details:</p>
<blockquote><p>The LIFE Photo Archive featured on Google will be among the largest professional photography collections on the Web and one of the largest scanning projects ever undertaken. Millions of images have been scanned and made available on Google Image Search today with all 10 million images to be available in the coming months.</p>
<p>“For 70 years, LIFE has been about one thing, and that’s the power of photography to tell a story,” says Andy Blau, LIFE’s President. “LIFE will now reach a broader audience and engage them online with the incredible depth and breadth of the LIFE Photo Archive from serious world events, to Hollywood celebrities to whimsical photographs.” Time Inc. EVP, John Squires adds: “We’re delighted Google recognized the rich value of our photo archive and worked with us to bring it to millions of consumers. Consistent with the launch of the TIME Archive, PEOPLE Archive and the SI Vault, this initiative continues our efforts to build valuable new revenue opportunities from our rich heritage.”</p>
<p>All keywords are translated into 16 different   languages<strong>. </strong>LIFE’s Photo Archive will be scanned and available on Google Image Search free for personal and research purposes. Copyright and ownership of all images will remain with Time Inc.</p></blockquote>
<p>Google uses a special notation to support search across the LIFE collection &#8211; all you do is include source:life as one of your search terms within the Google Image search box. Each photo has a rich set of metadata including a description and the keywords mentioned in the press release above.</p>
<p>When you click on one of the keywords (which are actually called &#8216;Labels&#8217; in the Google interface) it submits a search within the LIFE collection &#8211; but does NOT restrict that search to only the keywords. Rather, it seems to search across all the text associated with each image. For example &#8211; the label &#8216;Feathers&#8217; on assorted images links to this URL: <a href="http://images.google.com/images?&amp;hl=en&amp;q=Feathers+source:life" title="LIFE Photo Archive search for Feathers">http://images.google.com/images?q=Feathers+source:life</a>. This search returns many images, including one of <a href="http://images.google.com/hosted/life/l?imgurl=835d55936404eae4" title="Debutante Marilyn Lowe wearing a dress made from feathers">Debutante Marilyn Lowe wearing a dress made from feathers</a> which is not in fact assigned the label &#8216;Feathers&#8217;, but obviously does include the word feathers in the description.</p>
<p>For those accustomed to hotlinked tag-like terms only retrieving content that also is assigned that term (see <a href="http://flickr.com/commons/tags/snow" title="Flickr Commons Tag Snow">all the images in the Flickr Commons tagged with &#8216;snow&#8217;</a>), this might be a bit confusing. Also in contrast with the <a href="http://flickr.com/commons" title="Flickr Commons">Flickr Commons</a>, Google does not offer the opportunity for users to assign additional labels/keywords to the images. If you have signed on with a Google account, you <em>can </em>assign images within the LIFE collection a star rating. I don&#8217;t see how this is used right now, but I expect that over time they will leverage these ratings to sort the Google hosted image search results.</p>
<p>Since I spend a lot of time these days organizing controlled vocabularies, seeing the keywords assigned to these images makes me wish I could see Time Inc&#8217;s full and organized set of terms. My favorite spotted so far? <a href="http://images.google.com/images?q=Lines+Of+People+source:life" title="LIFE Photo Archive of Lines of People">Lines of People</a> &#8211; as typified by this photograph of <a href="http://images.google.com/hosted/life/l?imgurl=e2699913c595da58" title="Models wearing checked outfits">Models wearing checked outfits</a> from 1958.</p>
<p>It will be interesting to see what other partnerships crop up in the next year to digitize other major collections. I am also very curious to know if people actually buy framed fine art prints at the current cost of $79.99 for an 8&#8243;x12&#8243; inch print in a 13&#8243;x16&#8243; frame. Who knows if Time Inc will be forthcoming with their degree of success on this front &#8211; but it will likely be an good test case for other major collections looking to recoup some of the cost of their digitization efforts and find a new revenue stream.</p>
<p><em>Image Credit: The copyright of both of the images shown above belong to Time Inc. Please click through to view details about each image, including the photographer&#8217;s name and the option to purchase your own print of the image. </em></p>
<p>This post is from from: <a href="http://www.spellboundblog.com">Spellbound Blog</a>.<br/><br/><a href="http://www.spellboundblog.com/2008/11/22/life-photo-archive-digitized-and-put-online-by-google/">LIFE Photo Archive Digitized and Put Online by Google</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.spellboundblog.com/2008/11/22/life-photo-archive-digitized-and-put-online-by-google/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Anyone going to IA Summit 2008?</title>
		<link>http://www.spellboundblog.com/2008/04/10/anyone-going-to-ia-summit-2008/</link>
		<comments>http://www.spellboundblog.com/2008/04/10/anyone-going-to-ia-summit-2008/#comments</comments>
		<pubDate>Thu, 10 Apr 2008 04:35:47 +0000</pubDate>
		<dc:creator>Jeanne</dc:creator>
				<category><![CDATA[controlled vocabularies]]></category>
		<category><![CDATA[interface design]]></category>

		<guid isPermaLink="false">http://www.spellboundblog.com/2008/04/10/anyone-going-to-ia-summit-2008/</guid>
		<description><![CDATA[I figured it couldn&#8217;t hurt to let folks know I am in Miami for the IA Summit. Anyone else from this corner of the world headed this way? If so, either drop a comment here or ping me over in IA Summit&#8217;s CrowdVine. This post is from from: Spellbound Blog.Anyone going to IA Summit 2008?<p>This post is from from: <a href="http://www.spellboundblog.com">Spellbound Blog</a>.<br/><br/><a href="http://www.spellboundblog.com/2008/04/10/anyone-going-to-ia-summit-2008/">Anyone going to IA Summit 2008?</a></p>
]]></description>
			<content:encoded><![CDATA[<p>I figured it couldn&#8217;t hurt to let folks know I am in Miami for the <a href="http://www.iasummit.org/2008/" title="IA Summit 2008">IA Summit</a>. Anyone else from this corner of the world headed this way? If so, either drop a comment here or ping me over in <a href="http://iasummit08.crowdvine.com/profiles/13744" title="IA Summit: Jeanne on CrowdVine">IA Summit&#8217;s CrowdVine</a>.</p>
<p>This post is from from: <a href="http://www.spellboundblog.com">Spellbound Blog</a>.<br/><br/><a href="http://www.spellboundblog.com/2008/04/10/anyone-going-to-ia-summit-2008/">Anyone going to IA Summit 2008?</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.spellboundblog.com/2008/04/10/anyone-going-to-ia-summit-2008/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>SAA2007: Content Aggregation, Shareable Metadata and Access (Session 607)</title>
		<link>http://www.spellboundblog.com/2007/11/09/saa2007-content-aggregation-shareable-metadata-and-access-session-607/</link>
		<comments>http://www.spellboundblog.com/2007/11/09/saa2007-content-aggregation-shareable-metadata-and-access-session-607/#comments</comments>
		<pubDate>Fri, 09 Nov 2007 04:15:33 +0000</pubDate>
		<dc:creator>Jeanne</dc:creator>
				<category><![CDATA[access]]></category>
		<category><![CDATA[context]]></category>
		<category><![CDATA[controlled vocabularies]]></category>
		<category><![CDATA[EAD]]></category>
		<category><![CDATA[metadata]]></category>
		<category><![CDATA[search]]></category>

		<guid isPermaLink="false">http://www.spellboundblog.com/2007/11/09/saa2007-content-aggregation-shareable-metadata-and-access-session-607/</guid>
		<description><![CDATA[Focusing on the challenges of sharing metadata to support content aggregation and access, SAA2007 Session 607&#8242;s official title was The Dynamics in the Aggregate: Shareable Metadata and Next-Generation Access Systems. Bill Landis, the Head of Arrangement, Description, &#38; Metadata Coordinator at Yale University Library&#8217;s Manuscripts and Archives division, began the session by stressing that while [...]<p>This post is from from: <a href="http://www.spellboundblog.com">Spellbound Blog</a>.<br/><br/><a href="http://www.spellboundblog.com/2007/11/09/saa2007-content-aggregation-shareable-metadata-and-access-session-607/">SAA2007: Content Aggregation, Shareable Metadata and Access (Session 607)</a></p>
]]></description>
			<content:encoded><![CDATA[<p><a href="http://flickr.com/photos/prettydaisies/869133597/in/photostream" title="Photo take by Andrea Mercado: Card Catalog, Digital Catalog"><img src="http://www.spellboundblog.com/wp-content/uploads/2007/11/869133597_4593d91df7_m.jpg" title="Photo taken by Andrea Mercado: Card Catalog, Digital Catalog" alt="Photo taken by Andrea Mercado: Card Catalog, Digital Catalog" align="left" hspace="10" /></a>Focusing on the challenges of sharing metadata to support content aggregation and access, SAA2007 Session 607&#8242;s official title was <a href="http://www.ibiblio.org/saa2007/index.php/Session:_The_Dynamics_in_the_Aggregate:_Shareable_Metadata_and_Next-Generation_Access_Systems_%28Session_607%29" title="The Dynamics in the Aggregate: Shareable Metadata and Next-Generation Access Systems">The Dynamics in the Aggregate: Shareable Metadata and Next-Generation Access Systems</a>. <a href="http://www.archivists.org/prof-education/instructor-bios/landis.asp" title="Bill Landis">Bill Landis</a>, the Head of Arrangement, Description, &amp; Metadata Coordinator at <a href="http://www.library.yale.edu/mssa/" title="Yale University Library: Manuscripts and Archives">Yale University Library&#8217;s Manuscripts and Archives</a> division, began the session by stressing that while it is hard to predict the future it seems obvious that there will be an increase in the aggregation of content. Google is one type of aggregator. Many institutions are using the standards of the <a href="http://www.openarchives.org/" title="Open Archives Initiative">Open Archives Initiative</a> (OAI) to both publish and to harvest data. This session considered shareable metadata and how it can support or hinder content aggregation and access. A pointer was give to the <a href="http://webservices.itcs.umich.edu/mediawiki/oaibp/" title="Best Practices for OAI Data Provider Implementations and Shareable Metadata">Best Practices for OAI Data Provider Implementations and Shareable Metadata</a> joint initiative of the <a href="http://www.diglib.org/" title="Digital Library Federation">Digital Library Federation</a> and the <a href="http://nsdl.org/" title="National Science Digital Library">National Science Digital Library</a>.</p>
<p><strong>Introduction to Shareable Metadata and Interoperability</strong></p>
<p>The first speaker, <a href="https://netfiles.uiuc.edu/sshreeve/www/index.html" title="Sarah Shreeves">Sarah Shreeves</a>, started the panel off with her presentation titled <a href="http://hdl.handle.net/2142/2263" title="The Dynamics of Sharing: Introduction to Shareable Metadata and Interoperability">The Dynamics of Sharing: Introduction to Shareable Metadata and Interoperability</a> (follow the link to view the full set of slides). Sarah is not an archivist, but she has extensive experience with metadata aggregation.</p>
<p>She began with the assumption that &#8220;we&#8221; (libraries/archives/museums/cultural organizations) cannot afford to think about our collections only in the context of our local community. There is no way to know where your metadata is going to end up &#8211; either grouped with other things or pulled out of your collection into single atomized items.</p>
<p>Why share content? It benefits our users, supports one-stop searching, brings together distributed collections and supports <a href="http://en.wikipedia.org/wiki/Mashup_(web_application_hybrid)" title="Wikipedia: Mashups">mashups</a> . Sharing helps us and increases our exposure. We have to do this &#8211; we cannot assume that our users will come in through the front door. <a href="http://www.oclc.org/research/staff/dempsey.htm" title="Lorcan Dempsey">Lorcan Dempsey</a> uses the phrase <a href="http://orweblog.oclc.org/archives/000688.html" title="Lorcan Dempsey's Weblog: In The Flow">In The Flow</a> to mean how to get your content &#8220;out&#8221; into the world where users will find it.</p>
<p>Keys to Shareability or Interoperability:</p>
<ul>
<li>You need the technical side (<a href="http://www.loc.gov/z3950/agency/" title="Z39.50">Z39.50</a>, <a href="http://www.openarchives.org/pmh/" title="OAI-PMH">OAI PMH</a>, <a href="http://en.wikipedia.org/wiki/RSS_(file_format)" title="Wikipedia:">RSS</a> &#8230;etc)</li>
<li>Organization commitment of resources (people, training, time, priority)</li>
<li>Standards.. lots and lots of standards</li>
</ul>
<p>There are two main ways to share metadata. The first is known as <a href="http://en.wikipedia.org/wiki/Federated_search" title="Wikipedia: Federated Search">federated search</a>. In this model a user searches from a single central location. That query is sent to distributed database and the answers are sent back for the central query source to assemble the results. <a href="http://www.loc.gov/z3950/agency/" title="Z39.50">Z39.50</a> and Search/Retrieval via URL ( <a href="http://www.loc.gov/standards/sru/" title="LOC: SRU">SRU</a>) are examples of technology used to perform federated searches.</p>
<p>The second way of sharing metadata is known as the metadata aggregation model. In this scenario, metadata is pulled from many places into a single location. This is what search engines, <a href="http://en.wikipedia.org/wiki/Union_catalog" title="Wikipedia: Union Catalog">union catalogs</a>, <a href="http://www.openarchives.org/pmh/" title="OAI-PMH">OAI PMH</a>, <a href="http://en.wikipedia.org/wiki/RSS_(file_format)" title="Wikipedia:">RSS</a> and <a href="http://en.wikipedia.org/wiki/Atom" title="Wikipedia: Atom">Atom</a> do. It provides an opportunity to massage and normalize the data. Once users find what they are looking for &#8211; they are often redirected to the original source of the item.</p>
<p>A major challenge of the metadata aggregation model is &#8220;the ability to perform a search over diverse sets of metadata records and obtain meaningful results&#8221; Priscilla Caplan (in <a href="http://worldcat.org/isbn/0838908470" title="Metadata Fundamentals for All Librarians">Metadata Fundamentals for All Librarians</a>). This is hard because we are not used to what metadata looks like outside our local context. Sarah then showed lots of different examples so the audience could see how different the metadata is.</p>
<p>Metadata is not monolithic. It can be a view projected from a single information object. It is possible to create multiple views appropriate for different uses. Each view will affect the granularity of description, choice of vocabularies, and choice of formats.</p>
<p>You can customize the format of your metadata depending on the context of how the metadata will be consumed. This might sound scary, hard and overwhelming &#8211; but Sarah is confident that we can do this in smart ways. She believes that we should be able to lobby for the features we need to support different views.</p>
<p>Sarah&#8217;s list of attributes of &#8216;shareable metadata&#8217;:</p>
<ul>
<li>is quality metadata</li>
<li>promotes search interoperability</li>
<li>is human understandable outside of its local context</li>
<li>must be useful outside its local context &#8211; an aggregator can actually build services based on the data in the records provided &#8211; example was geographic data that can be used to put the items on a map</li>
<li>preferably is machine processable &#8211; Subject clustering &#8211; machine created &#8211; but still needs lots of human intervention to make it work</li>
<li>provides enough contextual information &#8211; the Theodore Roosevelt collection didn&#8217;t have a Roosevelt subject term because the title of the collection was assumed to be enough. She also mentioned a map that didn&#8217;t include the fact that it was a map in it&#8217;s metadata</li>
<li>is consistent across a collection &#8211; ie, same date field, same controlled vocabulary.. this is within a single collection</li>
<li>is coherent</li>
<li>is true to its content but also its audience &#8211; different views for different perspectives</li>
<li>conforms to standards &#8211; descriptive, technical, etc</li>
</ul>
<p>There <strong><em>are</em></strong> some safe assumptions you can make. Users often get to your data through shared records &#8211; not through your front door. Users either don&#8217;t know about your collection or won&#8217;t remember. Shared records can lead users to local environments where the full context is available. Users are often entering through deep links that may bypass the introductory information that provides the larger context for a collection.</p>
<p><strong>Implementing Shareable Metadata Practices</strong></p>
<p><a href="http://www.dlib.indiana.edu/~jenlrile/" title="Jenn Riley">Jenn Riley</a>, of the <a href="http://inquiringlibrarian.blogspot.com/" title="Inquiring Librarian Blog">Inquiring Librarian Blog</a>, gave the 2nd presentation:  <a href="http://www.dlib.indiana.edu/~jenlrile/presentations/saa2007/jennSAA2007.ppt" title="Implementing Shareable Metadata Practices in a Diverse University Envrionment (PPT)">Implementing Shareable Metadata Practices in a Diverse University Environment</a>. Jenn has a grand vision of what we are trying to achieve with all these efforts to share metadata. We needs lots of different ways to discover the data.. lots of environments.</p>
<p>We need machine-readable descriptive metadata, definitions of properties of shareable metadata in various communities (this is the focus of this session), and protocols and systems that use them for sharing that make it automatic. We also need online delivery of content too, but that is a big challenge and out of scope for this session.</p>
<p>Archives and digital libraries face different challenges in implementing standard practices related to shareable metadata. Archives are unique, making the notion of a single workflow model not possible. They are not a &#8216;homogeneous body&#8217;. Archives need to figure out how to support the expanding view of the mission to meet the needs of online users and make more services available. They need to find resources to provide appropriate description as well as technical implementation &#8211; and need time and money and skills in order to do this. On the other hand, digital library practice assumes content is digitized&#8211; that there will be &#8216;stuff&#8217; at the end. Metadata-only workflows are not common. Digital libraries usually assume item-level description, but this is often not the case, and concepts of provenance and original order are largely foreign.</p>
<p>Communities need to agree on key definitions to bridge the gulf between digital libraries and archives. Digital libraries need to understand that Encoded Archival Description (<a href="http://www.loc.gov/ead/" title="EAD">EAD</a>) is not a metadata format, EAD is a markup language.</p>
<p>The good news is that aggregations are not out to replace archives specific discovery systems. We don&#8217;t have to give up the local robust environment, we can and need to do both.</p>
<p>Key shareable metadata principles for archives:</p>
<ul>
<li>Context: need enough context so the user can figure out if the record is useful for them. At the same time &#8211; too much repeated info can cause issues too.</li>
<li>Content: what is the appropriate granularity for shared records from archives &#8212; this choice needs to be done per usage and per audience.</li>
</ul>
<p>Possible strategies include the creation of collection-level records only, creation of an aggregator that understands multi-level descriptions, the design of multi-level descriptions carefully for future item/file-level view, linking to digital objects from the lowest level of description in the finding aid and description at the item level.</p>
<p>Jenn then discussed the experiences at <a href="http://www.dlib.indiana.edu/" title="Indiana University's Digital Library Program">Indiana University&#8217;s Digital Library Program</a> :</p>
<ul>
<li>They have a <a href="http://www.dlib.indiana.edu/collections/findingaids/" title="IU: Finding Aids">new EAD finding aid website</a></li>
<li>the new system is more faithful to encoding with less &#8216;helpful&#8217; fixed presentation</li>
<li>mutual learning process about archival descriptive practices</li>
<li>many decisions made about when encoding should be changed when systems should be changed</li>
<li>results of this process: RE-ENGINEERING! New template, report card, better previewing capability &#8212; new template for EAD that supports new data we didn&#8217;t have before&#8230; report card built on schema-tron and encoder can preview how their encoding is really working and preview what the final product finding aid will look like</li>
<li>some EAD files link to digital objects</li>
<li>soon there will be item-level OAI records (Dublin Core and MODS) for digitized items linked from finding aids</li>
<li>central Digital Library repository that allows EAD as the *master* metadata format</li>
<li>new workflow that permits links from any level of a multi-level description in EAD</li>
</ul>
<p>The more you put stuff online &#8211; the more you attract the sort of attention that gets you more money to put more stuff online. Jenn suggests lobbying of software vendors for a better support of EAD.. don&#8217;t settle for Dublin core. We need to discuss with our user communities about the need for an archives-specific aggregators and consider the multi-level description.</p>
<p>Libraries and archives are learning from one another. The item centric view can be too narrow &#8211; but it can help with re-engineering. More structure in finding aids can be a good thing. Archives can show libraries why expertise in descriptive practice is still necessary &#8212; maybe those who are running out of things to catalog on the library side can spend some time describing over on the archives side?</p>
<p><strong>Archival Frameworks for Shareable Metadata</strong></p>
<p>Kelcy Shepherd, Digital Interfaces Librarian at the <a href="http://umass.edu/umhome/index.php" title="University of Massachusetts Amherst">University of Massachusetts Amherst</a> , gave the final presentation of the session: &#8220;Archival Standards and Tools: A Framework for Shareable Metadata&#8221;.</p>
<p>The first framework Kelcy addressed was <a href="http://www.archivists.org/catalog/pubDetail.asp?objectID=1279" title="Describing Archives: A Content Standard (DACS)">Describing Archives: A Content Standard</a> (DACS). What about DACS is applicable to sharing metadata? It is compatible for use with controlled vocabularies. It can make sure that our access points will work well with access points from other metadata communities. Since DACS is output agnostic, you can create the data and then use that data to generate different views or formats. A single set of DACS based data can produce printed finding aids, EAD finding aids, MARC 21 or MODS records.</p>
<p>In order to produce each of these different views from a single original format, you must a crosswalk. A crosswalk maps individual elements from one data format to corresponding elements of another. Unfortunately, crosswalks come with their own challenges:</p>
<ul>
<li>granularity</li>
<li>missing elements</li>
<li>single element on one side that would need to be split into multiple elements on the other side</li>
</ul>
<p>You need expertise in both standards addressed by a each crosswalk in order to do this well.</p>
<p>Next Kelcy discussed <a href="http://www.archivists.org/saagroups/ead/" title="Encoded Archival Description">Encoded Archival Description</a> (EAD). EAD is a data structure standard, machine readable format for encoding archival descriptions. It allows archivists to share the data across institutions. If you want to re-purpose a finding aids metadata, the data needs to be in a machine readable format. EAD gives you this. You can convert an EAD encoded finding aid into a <a href="http://www.loc.gov/standards/mods/" title="Metadata Object Description Schema">Metadata Object Description Schema</a> (MODS) document using an <a href="http://en.wikipedia.org/wiki/XSL_Transformations" title="XSLT">XSLT</a> stylesheet and a crosswalk. The stylesheet may take a lot of work (especially for use across many finding aids), but there is a big payoff. Once the work is done a single stylesheet can be used across many many finding aids.</p>
<p>The <a href="http://www.archiviststoolkit.org/" title="Archivists' Toolkit">Archivists&#8217; Toolkit</a> was cited as an example of a tool that can let you output multiple formats from a single set of data. It can produce EAD, MARC, MODS and Dublin Core records.</p>
<p>Tools can support efforts &#8211; but it all comes back to quality archival description. The best tool in the world will never make bad content into good content. If data is inconsistent &#8211; you have to manually go back and clean it up. I particularly liked Kelcy&#8217;s point about ensuring that your data doesn&#8217;t need the screen labels you to make sense. If you don&#8217;t consider this, when you export that data into a new format or view the data can loose it&#8217;s meaning.</p>
<p>Her concluding point was that if you don&#8217;t have the tech skills or support, work on your content.. use DACS&#8230; get your data in order and it will pay off later.</p>
<p><strong>Questions and Answers</strong></p>
<p><em>Question</em>: How does this work when you are trying to share your metadata with communities that use different controlled vocabularies &#8211; thinking about the single EAD that generates MODS and MARC .etc etc&#8230;</p>
<p><em>Answer</em>: Aggregators often they don&#8217;t use subject headings. This is nearly impossible to do in OAI &#8211; people use lots of different controlled vocabularies.. and sometimes no controlled vocabulary at all. There are experiments being done with subject clustering. Algorithms are used to cluster like things together &#8211; but it still requires human intervention to make sure the clusters make sense.</p>
<p>On the other hand &#8211; if you are using a standard vocabulary, there is work being done to map from one standard to another. An example of this is the OCLC <a href="http://www.oclc.org/research/projects/mswitch/default.htm" title="OCLC: Metadata Switch Project">Metadata switch project</a> .</p>
<p><em>Question</em> : What about social taggging?</p>
<p><em>Jenn</em> : We are in no position to turn down metadata.</p>
<p><em>Sarah</em>: <a href="http://www.dspace.org/" title="DSpace">DSpace</a> has a concept of community. There is a way to let a community organically build their own controlled vocabulary as they go &#8211; new contributions are provided choices of terms that have been used before.</p>
<p>Bill talked about the article about Michaelson where they gave the same finding aids to 40 archivists to use LCSH for picking subject headings. The result was 0 consistency! Every single archivist picked different subject headings.</p>
<p><em>Jordan</em>: <a href="http://tags.library.upenn.edu/help/" title="PennTags - Help">PennTags</a> is an example of an effort to combine social tagging with traditional classification. It shows tagging not as competition but as another way to get user generated descriptive information. It is an example of a way to &#8216;get into the flow&#8217;.</p>
<p><em>Sarah:</em> Google will now use OAI PMH as a site map for indexing, but it throws away the metadata.</p>
<p><em>Jenn:</em> Dlib &#8211; representing digital collections on wikipedia article.</p>
<p><em>Bill:</em> PennTags is acting as an aggregation system to pull siloed information together.</p>
<p><em>Question</em>: In some cases EAD data is flattened down for all items so that each item has all the context data and only one field is different on each? Is this an indication that the mapping have been better?</p>
<p><em>Answer</em>: It is a problem &#8211; can be a problem&#8230;ultimately it is all about use and audience.</p>
<p><strong>My Thoughts</strong></p>
<p>I came away from this session with my head whirling with ideas. I was so pleased to hear people talk about concrete examples. We need more examples of challenges and real world benefits to further efforts to aggregate, publish and share archival content and it&#8217;s metadata. None of this is easy, but each project will give us new lessons and add to the growing set of best practices.</p>
<p>I truly believe that the sooner we tackle these thorny problems, the sooner we will start seeing the impact in improved access to archival records. The sooner we deal with it, the less we will be adding data that will have to be fixed later.</p>
<p>For anyone who has been following my blog &#8211; you will already know about my <a href="http://www.spellboundblog.com/2007/05/13/archivesz-visualizing-archival-collections/" title="Spellboundblog: ArchivesZ">ArchivesZ</a> project from last spring. One of the big struggles we had was figuring out how to make the subject term metadata &#8216;useful&#8217; for aggregation and visualization. Another example of the challenges and benefits to shareable metadata is the <a href="http://www.spellboundblog.com/2007/09/22/saa2007-publishers%e2%80%99-bindings-online-digitization-collaboration-standardization-and-community-building-session-707/" title="SAA2007: PBO Presentation">SAA presentation about Publisher&#8217;s Bindings Online</a> .</p>
<p>I had one last sentence in my notes from this session &#8211; an idea for a <a href="http://developers.facebook.com/" title="Facebook Developers">Facebook application</a> that would let you feature your favorite archival image or record. This would be an amazing example of getting archival records &#8216;in the flow&#8217; and showing up in surprising new places where no-one is &#8216;looking&#8217; for records. Hey &#8211; maybe I should prod the <a href="http://www.footnote.com" title="Footnote.com">Footnote </a>people with this idea. It might be right up their alley!</p>
<p><em>As is the case with all my session summaries from SAA2007, please accept my apologies in advance for any cases in which I misquote, overly simplify or miss points altogether in the post above. These sessions move fast and my main goal is to capture the core of the ideas presented and exchanged. Feel free to contact me about corrections to my summary either via comments on this post or via my <a href="http://www.spellboundblog.com/contact/" title="Contact Form">contact form</a>.</em></p>
<p>This post is from from: <a href="http://www.spellboundblog.com">Spellbound Blog</a>.<br/><br/><a href="http://www.spellboundblog.com/2007/11/09/saa2007-content-aggregation-shareable-metadata-and-access-session-607/">SAA2007: Content Aggregation, Shareable Metadata and Access (Session 607)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.spellboundblog.com/2007/11/09/saa2007-content-aggregation-shareable-metadata-and-access-session-607/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>SAA2007: Publishers’ Bindings Online &#8211; Digitization, Collaboration, Standardization and Community Building (Session 707)</title>
		<link>http://www.spellboundblog.com/2007/09/22/saa2007-publishers%e2%80%99-bindings-online-digitization-collaboration-standardization-and-community-building-session-707/</link>
		<comments>http://www.spellboundblog.com/2007/09/22/saa2007-publishers%e2%80%99-bindings-online-digitization-collaboration-standardization-and-community-building-session-707/#comments</comments>
		<pubDate>Sun, 23 Sep 2007 03:33:35 +0000</pubDate>
		<dc:creator>Jeanne</dc:creator>
				<category><![CDATA[access]]></category>
		<category><![CDATA[controlled vocabularies]]></category>
		<category><![CDATA[digitization]]></category>
		<category><![CDATA[funding]]></category>
		<category><![CDATA[metadata]]></category>
		<category><![CDATA[SAA2007]]></category>
		<category><![CDATA[search]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[virtual collaboration]]></category>

		<guid isPermaLink="false">http://www.spellboundblog.com/2007/09/22/saa2007-publishers%e2%80%99-bindings-online-digitization-collaboration-standardization-and-community-building-session-707/</guid>
		<description><![CDATA[Session 707 of SAA2007 in Chicago discussed many aspects of the project that created Publishers&#8217; Bindings Online (PBO). The full title of this session was The Anatomy of a Collaborative Digital Project and Lessons Learned in the Realms of Access, Outreach, and Creative Success: A Multi-Disciplinary Look at Publishers’ Bindings Online, 1815-1930: The Art of [...]<p>This post is from from: <a href="http://www.spellboundblog.com">Spellbound Blog</a>.<br/><br/><a href="http://www.spellboundblog.com/2007/09/22/saa2007-publishers%e2%80%99-bindings-online-digitization-collaboration-standardization-and-community-building-session-707/">SAA2007: Publishers’ Bindings Online &#8211; Digitization, Collaboration, Standardization and Community Building (Session 707)</a></p>
]]></description>
			<content:encoded><![CDATA[<p><a href="http://bindings.lib.ua.edu/" title="Publishers' Bindings Online"><img src="http://www.spellboundblog.com/wp-content/uploads/2007/09/pbo.JPG" title="PBO image" alt="PBO image" align="left" height="153" width="153" /></a>Session 707 of SAA2007 in Chicago discussed many aspects of the project that created <a href="http://bindings.lib.ua.edu/" title="Publishers' Bindings Online">Publishers&#8217; Bindings Online</a> (PBO). The full title of this session was <a href="http://www.ibiblio.org/saa2007/index.php/Session:_The_Anatomy_of_a_Collaborative_Digital_Project_and_Lessons_Learned_in_the_Realms_of_Access%2C_Outreach%2C_and_Creative_Success" title="The Anatomy of a Collaborative Digital Project and Lessons Learned in the Realms of Access, Outreach, and Creative Success: A Multi-Disciplinary Look at Publishers’ Bindings Online, 1815-1930: The Art of Books">The Anatomy of a Collaborative Digital Project and Lessons Learned in the Realms of Access, Outreach, and Creative Success: A Multi-Disciplinary Look at Publishers’ Bindings Online, 1815-1930: The Art of Books</a>. The presenters have kindly posted the <a href="http://bindings.lib.ua.edu/saa_pres_083007_FINAL.pdf" title="SAA 2007 PBO presentation slides">full slide deck from their panel</a> online. In this post I attempt to capture the main points of the presentation and Q&amp;A discussion of PBO.</p>
<p><strong>Who Spoke?</strong></p>
<p><a href="http://www.archivists.org/prof-education/instructor-bios/Lacher-Feldman.asp" title="Jessica Lacher-Feldman">Jessica Lacher-Feldman</a> (session chair) &#8211; <a href="http://www.ua.edu/" title="University of Alabama">University of Alabama</a>, PBO project manager</p>
<p><a href="http://www.lib.ncsu.edu/staff/aeruders/" title="Amy Rudersdorf">Amy Rudersdorf</a> &#8211; now at <a href="http://www.ncsu.edu/" title="North Carolina State University">North Carolina State University</a>, Digital production coordinator, <a href="http://www.lib.ncsu.edu/specialcollections/" title="NCSU Special Collections Research Center">NCSU special Collections</a>, but was at <a href="http://www.wisc.edu/" title="University of Wisconsin, Madison">University of Wisconsin, Madison</a> during PBO project</p>
<p>Kristy Dixon &#8211; <a href="http://www.ua.edu/" title="University of Alabama">University of Alabama</a> , PBO staff</p>
<p><strong>PBO Project Overview</strong></p>
<p>PBO was made possible by a 3 year <a href="http://www.imls.gov" title="Institute of Museum and Library Services (IMLS)">Institute of Museum and Library Services</a> (IMLS) grant. Originally awarded in 2003, the grant was extended once (and I think they mentioned additional funding being applied for). The primary grant funded the digitization of 10,000 images from up to 5000 book bindings. Ultimately 10,570 images were added to PBO and made searchable by metadata. The bindings selected included books from 1815-1930, primarily US titles and mostly in English.</p>
<p>Their guiding vision was of &#8220;giving something to the world that is both needed and useful&#8221; (and really beautiful). And they succeeded! PBO is a lot more than 10,000+ digitized book bindings. The project strived to make the information available in many different ways, including via:</p>
<ul>
<li>a web-based database</li>
<li>online exhibits &amp; galleries,</li>
<li><a href="http://en.wikipedia.org/wiki/Video_podcast" title="Wikipedia: Vodcats or Video Podcasts">vodcasts</a> and <a href="http://en.wikipedia.org/wiki/Podcasting" title="Wikipedia: Podcast">podcasts</a></li>
<li>web-based tutorials</li>
<li>virtual and real exhibits</li>
<li>presentations &amp; class lectures</li>
<li>opportunities to adapt the project to other disciplines &#8211; history, book arts, librarianship, literature.. K-12 and more</li>
</ul>
<p><strong>Technology and Processes</strong></p>
<p>The division of labor for PBO was split between the <a href="http://www.ua.edu/" title="University of Alabama">University of Alabama</a> and the <a href="http://www.wisc.edu/" title="University of Wisconsin, Madison">University of Wisconsin, Madison</a>.</p>
<p>Many extensions to the OCLC <a href="http://opensitesearch.sourceforge.net/docs/helpzone/main.html" title="SiteSearch">SiteSearch</a> based database were made by the <a href="http://uwdcc.library.wisc.edu/" title="University of Wisconsin Digital Collections Center">UWDCC</a> (UW Digital Collections Center) digital production center at the <a href="http://www.wisc.edu/" title="University of Wisconsin, Madison">University of Wisconsin, Madison</a> .</p>
<p>They went through an overview of the participants and staff &#8211; who did what.. what skills were needed and what was brought by the two institutions to the collaboration. They acknowledged their fabulous advisory group including Sue Allen &#8211; &#8220;the expert on publisher&#8217;s bindings&#8221;. Individuals from outside their teams contribute based on their special interest and knowledge about a specific individual (this contribution is still ongoing).</p>
<p>Working in collaboration forced them to wrestle with many challenges including:</p>
<ul>
<li>staff in two locations &#8211; most of whom had never met</li>
<li>&#8220;long distance relationships are hard&#8221;</li>
<li>they had to work hard to ensure that all were &#8216;equally-valued participants&#8217;</li>
<li>standards &#8211; you need ground rules from the outset</li>
</ul>
<p><strong>Collaboration &amp; Description</strong></p>
<p>&#8220;Every pair of eyes are different&#8221;.  PBO tapped into the resource of the &#8216;young fertile minds&#8217; to power the project out of the local MLS programs at both institutions. Even with a detailed description form &#8211; there was confusion over subject headings and overlap &#8211; especially when those selecting subject headings were grad students who might not know the official terms for things. For example, the list of terms might include <a href="http://en.wikipedia.org/wiki/Ouroboros" title="Wikipedia:">Ouroboros</a> &#8211; but the students might not know this  it is the term for a snake eating it&#8217;s own tail.</p>
<p>Ultimately they had to do quality control at a single location. They spent a LOT of time on this.</p>
<p>Their top tips for cultivating continuity for virtual project teams:</p>
<ul>
<li>write into your grants money for travel (they stressed that your grant includes funds to support people meeting each other)</li>
<li>continuous communication is critical</li>
<li>&#8216;shared working group website&#8217; available online</li>
<li>email, conference calls and instant messaging (IM) for communication</li>
<li>regular reporting to each other</li>
<li>being project manager means that you have to be on top of everything &#8211; you need to be the glue</li>
<li>focus on the deliverables &#8211; use planning tools and timelines</li>
</ul>
<p>They discovered that IM was key to developing trust between the two institutions.</p>
<p><strong>Metadata &#8211; the core of the project</strong></p>
<p>The key to their metadata approach was to consider a book less as a &#8216;bibliographic object&#8217; and more as an &#8216;art object&#8217;.</p>
<p>They called books in PBO &#8216;objects&#8217; but still kept the bibliographic metadata. They used <a href="http://en.wikipedia.org/wiki/Dublin_Core" title="Wikipedia: Dublin Core">Dublin Core</a> by pulling the <a href="http://www.loc.gov/marc/" title="MARC">MARC</a> data into the Dublin Core structure. As part of this they took all the subjects from the bibliographic info and moved it to the Dublin Core description and labeled it &#8216;book topic&#8217;. Then they used the &#8216;Subjects&#8217; portion of the Dublin Core record to describe the binding and talk about what the images are OF. This is where the subject terms from the controlled vocabulary were added.</p>
<p>These are the steps of their metadata workflow process:</p>
<ul>
<li>selection from collections of note &#8211; faculty, consultants and library staff did this step</li>
<li>description &#8211; used a paper form, described the books on paper and joined that description to what was in the MARC record &#8211; done by the grad students and library staff</li>
<li>metadata entry &#8211; entry of data through an online form &#8211; done by students (overseen by library staff) actually ended up being cheaper to manually enter the MARC data (rather than automated extraction)</li>
<li>quality control &#8211; content, grammar, spelling &#8211; done by library staff (took a lot more time than anyone expected)</li>
<li>no live update between their working Filemaker Pro database and the final SiteSearch database</li>
<li>record ownership &#8211; indicated in the identifier field (with a special code in the identifier) AND in the Submitter field</li>
</ul>
<p>A lot of description went into this project.</p>
<p>They needed to develop a controlled vocabulary for the project. To do this they first worked with content specialists to develop a list. They used <a href="http://en.wikipedia.org/wiki/Library_of_Congress_Subject_Headings" title="Wikipedia: Library of Congress Subject Headings">Library of Congress Subject Headings</a> (LCSH) terms where they could, as well as <a href="http://www.getty.edu/research/conducting_research/vocabularies/aat/" title="Getty Art and Architecture Thesaurus">Getty Art and Architecture Thesaurus</a>. Then they added some local terms. The controlled vocabulary list evolved with the project and is the foundation of all teaching, search and more.</p>
<p>The speaker showed an example of the controlled vocabulary &#8211; the terms really are a window into the past. Users can <a href="http://bindings.lib.ua.edu/vocabulary.htm" title="PBO: Browse Controlled Vocabulary">browse the controlled vocabulary</a> through the front end.</p>
<p>On the description paper form they had a list of &#8216;binding themes&#8217; for those doing the description to pick from. A lot of work was done to get the huge list of themes onto a single page. Ultimately they had to provide some fill in the blank extension fields. For example, rather than believing they had listed every useful trade or profession, there was a section on the list labeled: Profession/Trade &#8211; _______________ with the expectation that those describing a binding might need to fill in the blank.</p>
<p><strong>Digitization and The Database</strong></p>
<p>Generally two scans were taken from each book, but sometimes as many as five. What did they scan? Front cover, spine, back cover and end papers.</p>
<p>There were two different image reformatting standards at the two institutions &#8211; 300 <a href="http://en.wikipedia.org/wiki/Dots_per_inch" title="Wikipedia: Dots Per Inch (DPI)">DPI</a> vs 600 DPI. Both used a black background when scanning. All books were presented in as in condition &#8211; some have front/back covers missing. After the scanning they began with master TIFs and then transformed them to JPGs in three sizes in 72 DPI.</p>
<p>The presentation showed screen shots of:</p>
<ul>
<li>simple search</li>
<li>brief view record in search results &#8212; which includes subjects</li>
<li>full record view &#8211; including display of all images associated with the book object record</li>
<li>gallery view &#8211; thumbnail, title and indication if there are one or more images related to the title</li>
<li>guided search (advanced search)</li>
<li>clickable subject headings</li>
</ul>
<p>All the images in PBO are freely available for download.</p>
<p>With an eye to digital preservation, all the original uncompressed TIF images are archived in triplicate to digital archive tape and stored in three different locations. The metadata is stored with images in both text and SGML format (which is what SiteSearch works with). The full process documents are available on the project site.</p>
<p><strong>Future Growth</strong></p>
<p>The PBO team is talking to <a href="http://www.lsu.edu/" title="Louisiana State University">Louisiana State University</a> (LSU) to figure out how PBO can grow. LSU would need to work and live with the way PBO works and learn their processes. They are talking to other institutions &#8211; if you are interested in adding content to PBO, please contact them.</p>
<p>The Richard Minsky Collection has been purchased and is being added to the project. This is a rich collection that was gathered to create a catalog. PBO has the catalog and all of Minsky&#8217;s research that goes with the collection. The goal is to feed as much of this rich data into PBO as possible. They are working with individual scholars and collectors to find other avenues for growth.</p>
<p><strong>Value Added Components</strong></p>
<p>One of the focuses of PBO has been to look beyond the digital images themselves to creating value added components for their user community.</p>
<p>A <a href="http://bindings.lib.ua.edu/tutorials/tutorialmain.html" title="PBO: Tutorials">tutorial</a> for users is provided, including information about how to email a record. A comprehensive <a href="http://bindings.lib.ua.edu/bib.html" title="PBO Bibliography">bibliography</a> has been created and is used by scholars. The page prompts users to submit feedback so the bibliography is a live document.</p>
<p>Over <a href="http://bindings.lib.ua.edu/gallery2.html" title="PBO Galleries">30 galleries</a> have been created &#8211; organizing access to essays and additional info by topic. Types of galleries include:</p>
<ul>
<li>Galleries on Bindings and Book binding techniques &#8211; these are not really related to individual book objects &#8211; but give more information, for example <a href="http://bindings.lib.ua.edu/gallery/silvergold.html" title="PBO: Gallery on Silver &amp; Gold: The Art of Metal Stamping">Silver &amp; Gold: The Art of Metal Stamping</a></li>
<li>Galleries on Collections &#8211; for example the <a href="http://bindings.lib.ua.edu/gallery/wade.html" title="PBO: Collection Gallery for Wade Hall Collection of Southern History and Culture">Wade Hall Collection of Southern History and Culture</a></li>
<li><a href="http://bindings.lib.ua.edu/gallery_art.html" title="PBO: Artistic Galleries">Galleries on Artistic Styles and Movements</a> &#8211; a narrative approach provides information on the historical roots of the movements and show how the bindings fit into the movements</li>
<li><a href="http://bindings.lib.ua.edu/gallery_historical.html" title="PBO: Historical Galleries">Galleries on History</a> -  they have 11 of these galleries,including major historical events, literature and culture of the time</li>
<li><a href="http://bindings.lib.ua.edu/gallery_literary.html" title="PBO: Literary Galleries">Galleries on Literature</a></li>
</ul>
<p>Links to trusted information outside of PBO&#8217;s site are shown whenever possible. For example &#8211; links to the full text of books are provided via <a href="http://www.gutenberg.org/catalog/" title="Project Gutenberg">Project Gutenberg</a>. Throughout the site&#8217;s text link to sources such as the <a href="http://www.loc.gov" title="Library of Congress">Library of Congress</a>, .gov sites, <a href="http://www.pbs.org/" title="PBS">PBS</a> and so forth can be found.</p>
<p>Canned searches are provided to make it easy for users to explore content. An example of this is the <a href="http://bindings.lib.ua.edu/gallery/silvergold.html" title="PBO: Gallery on Silver &amp; Gold: The Art of Metal Stamping">Silver &amp; Gold: The Art of Metal Stamping</a> search that will find every binding with either silver or gold stamping. This is in contrast with making users figure out the right syntax to submit the search criteria themselves.</p>
<p>The <a href="http://bindings.lib.ua.edu/teaching.html" title="PBO: Teaching Tools">Teaching Tools</a> portion of the site provides sample <a href="http://bindings.lib.ua.edu/teaching.html#lesson" title="PBO: Lesson Plans">lesson plans</a> on all sorts of topics. They worked with some high school history teachers via focus groups and got feedback about what they needed and wanted. The <a href="http://http://bindings.lib.ua.edu/gallery/industrial/industrial_lesson.pdf" title="PBO: Industrial Revolution lesson plan">Industrial Revolution lesson plan</a> was created based on that feedback.</p>
<p>The <a href="http://bindings.lib.ua.edu/research.html" title="PBO: Research tools">research tools</a>  that were created as a result of the PBO project and are made available online are:</p>
<ul>
<li><a href="http://bindings.lib.ua.edu/glossary.html" title="PBO: Glossary">glossary</a> &#8211; 456 terms defined using ten major authorities</li>
<li>bibliography of <a href="http://bindings.lib.ua.edu/bib.html" title="PBO: Print Resources">print</a> &amp; <a href="http://bindings.lib.ua.edu/bib2.html" title="PBO: Online Resources">web</a> resources</li>
<li><a href="http://bindings.lib.ua.edu/vocabulary.htm" title="PBO: controlled vocabulary for subject headings">controlled vocabulary for subject headings</a></li>
<li><a href="http://bindings.lib.ua.edu/publishers_map.html" title="PBO: publisher's map">publishers map</a> &#8211; an interactive map that includes 2123 publishers so far</li>
<li>tutorials on various subjects</li>
</ul>
<p><a href="http://bindings.lib.ua.edu/designers.html" title="PBO: Publishers’ Bindings &amp; Their Designers">Signed or Designer bindings</a> is a new resource to which scholars continue to contribute new information.</p>
<p>Through collaboration with teaching faculty they developed the presentation such as <a href="http://bindings.lib.ua.edu/gallery/west.html" title="Indians, the Frontier, and the West in American Bookbindings">Indians, the Frontier, and the West in American Bookbindings</a>. This presentation will eventually be podcast on the PBO site. It talks about how these books inspired people to move west and inspired kids to read.</p>
<p>Another podcast is on the way addressing the representation of Uncle Tom&#8217;s Cabin. It will discuss how the book was it marketed to different groups &#8211; Yiddish, German&#8230; etc. There already exists a <a href="http://bindings.lib.ua.edu/gallery/uncletom.html" title="PBO: gallery and essay on Uncle Tom's Cabin">gallery and essay on Uncle Tom&#8217;s Cabin</a> .</p>
<p><strong>Conclusions</strong></p>
<p>The team has been very pleased by the tangible scholarly impact of PBO. They have seen extensive collaboration with the university community, new research, and promotion of the use of special collections materials in the classroom using digital resources. They point to PBO as showing a path to preserve these increasingly fragile books by moving out of the general stacks and into special collections &#8211; with a result of increased access to the book and decreased handling.</p>
<p>The presenters avowed that PBO could never have been created by their team alone &#8211; working with consultants and advisers was the key to their success. They needed input from experts and others to help PBO grow and keep it sustainable. This interaction makes the  project strong  &#8211; it has it&#8217;s own legs and won&#8217;t cease to exist when the money disappears.</p>
<p>Publicity and outreach got attention on the PBO project from the very beginning. They made documenting their experiences and making recommendations about how to market digital projects part of the original plan in their grant proposals. These documents were part of their deliverables. They even published a white paper about PBO and outreach.</p>
<p>PBO uses <a href="http://www.google.com/analytics/" title="Google Analytics">Google Analytics</a> so they can see where their users are coming from. Also it makes cool talking points for your reports and fun things to tell the Dean!</p>
<p>I think the best conclusion to my summary of the presentation portion of this session is the list of points on the final slide titled &#8220;Beyond the grant: Room to Grow&#8221;:</p>
<ul>
<li>Potential future contribution from other repositories in the US and abroad…</li>
<li>Potential future collaboration with teaching faculty at UA and beyond</li>
<li>With additional collections, the database and the project will only grow stronger</li>
<li>Potential as a web portal, clearing house, or consortium</li>
<li>Additional potential funding opportunities, scholarship, and ways to highlight collections, resources, knowledge, and abilities</li>
</ul>
<p><strong>Questions and Answers</strong></p>
<p><em>Keep in mind throughout this section that I am summarizing and paraphrasing the questions and their answers. Please do not take any statements as full and complete quotes. In cases where I missed too much of the question or answer I generally skipped including it in the list below. If you are anxious to know exactly what was said, you would need to <a href="http://secure.cartsvr.net/catalogs/catalog.asp?prodid=4985701&amp;showprevnext=1" title="Buy Recording of Session 707">buy</a> and listen to the conference recordings for this session.</em></p>
<p><em>Question</em>: Who maintains the website and who makes decisions about how things are going to get updated?<br />
<em>Answer</em>: UA maintains the static web pages and UW maintains the database. The project manager has been in charge.. made prototypes of new design and sent it around for feedback. They have standards for colors in their handbooks.</p>
<p><em>Question</em>: If the grant funding dried up right now would the project be sustainable?<br />
<em>Answer</em>: There is support from the institutions&#8230; for example, it is just one project of many at UW.</p>
<p><em>Question</em>: How did you get such good scans of the book spines?<br />
<em>Answer</em> : At UW they used blocks or boxes to prop up the books and laid black foam core on top on flatbed scanners. At UA &#8211; they used black paper covered blocks in combination with overhead scanners.</p>
<p><em>Question</em>: How did you get the full cover scans?<br />
<em>Answer</em>: They very carefully lay the cover flat &#8211; so the pages sticking are sticking up.</p>
<p><em>Question</em>: Who customized <a href="http://opensitesearch.sourceforge.net/docs/helpzone/main.html" title="SiteSearch">SiteSearch</a>  &#8211; OCLC or UW?<br />
<em>Answer</em>: UW did the work &#8211; they had one and a half dedicated IT staff to do the customizations.</p>
<p><em>Question</em> : Have you had to negotiate copyright issues for bindings from the late end of the time range of the project<br />
<em>Answer</em>: No.</p>
<p><em>Question</em> : Are you aware of others doing similar projects? Have you been approached and or are looking for others who want to contribute?<br />
<em>Answer</em>: Yes. Right now they are working with <a href="http://www.lsu.edu/" title="LSU">LSU</a>  and are not actively seeking out new participants. There are plans to grow the project eventually.</p>
<p><em>Question</em>: Did you think about the fact that you were creating your own online publication?<br />
<em>Answer</em>: They didn&#8217;t realize it ahead of time &#8211; they didn&#8217;t realize how powerful the database was going to be to fuel their ability to build further on the work.</p>
<p><em>Question</em>: Can you search for &#8216;young people&#8217;s covers&#8217; &#8211; is there metadata for what age groups might enjoy specific books?<br />
<em>Answer</em>: It depends on if it was part of the descriptive information, but you can search on &#8216;boys&#8217; or &#8216;girls&#8217; or &#8216;juvenile&#8217; and gain useful results.</p>
<p><em>Question</em>: Can you talk about the work behind the MARC to Dublin Core migration?<br />
<em>Answer</em>: In some ways it was easier than they thought it would be &#8211; so many of the fields transfer directly from MARC to Dublin Core.. it was the revelation about the book as art object that made them realize the work they needed to do. Building the controlled vocabularies was where the heavy lifting occurred. It involved going through giant spread sheets with subject terms in alphabetical order looking for typos and working toward consistency (ie, use plurals). The spreadsheet didn&#8217;t show how many items used each term &#8211; it was hard to know how many changes would be needed.</p>
<p><em>Question</em>: Do you get hits from the standard online catalog into PBO?<br />
<em>Answer</em>: This is not happening now. They would love to build a better connection between the <a href="http://en.wikipedia.org/wiki/OPAC" title="Wikipedia: OPAC">OPAC</a> and PBO in both institutions.</p>
<p><em>Question</em>: How did you make decisions when there were disagreements?<br />
<em>Answer</em>: &#8220;I don&#8217;t remember any more.. it was all so beautiful&#8230;&#8221; &lt;<em>laughter</em> &gt; . There were no big issues about standards. There were more issues about the grant and things like how many images or books they were supposed to scan. In some cases it was easy because they were in charge of very different project areas &#8211; each team had &#8220;their own little fiefdom&#8221;.</p>
<p><em>Question</em>: Do you think you might sell images to generate revenue?<br />
<em>Answer</em>: They have considered it. The have made a calendar and a poster, but gave them away. They also have used images for making holiday cards. They don&#8217;t see selling images as a main goal right now.</p>
<p><em>Question</em>: Have you considered pursuing online collaborative methods for work with the scholars and collectors?<br />
<em>Answer</em>: No, but they think that would be useful to explore.</p>
<p><strong>My Thoughts</strong></p>
<p>I loved the energy and connection displayed by the presenters. It was fun to see a team of people who clearly were so proud of their work and pleased by its reception. I was personally intrigued by the highlighted challenge of coming up with (and painstakingly validating) their <a href="http://bindings.lib.ua.edu/vocabulary.htm" title="PBO: controlled vocabulary">controlled vocabulary for subjects</a>. I firmly believe that the topic of subject terms and their standardization across repositories will only grow in importance. For those interested in some of what is being done on this front &#8211; take a look at both the UK based <a href="http://hilt.cdlr.strath.ac.uk/" title="HILT">High Level Thesaurus</a> (HILT) and the <a href="http://www.w3.org/2004/02/skos/" title="Simple Knowledge Organisation Systems Core">Simple Knowledge Organisation Systems Core</a> (SKOS) project. I suspect many will be intrigued by the SKOS use case titled <a href="http://www.w3.org/2006/07/SWD/wiki/EucManuscriptsDetailed" title="An integrated view to medieval illuminated manuscripts">An integrated view to medieval illuminated manuscripts</a>.</p>
<p>Even given the mammoth effort required to create a shared controlled vocabulary, it is clear that the benefits they have reaped from this effort are still being discovered. The speakers mentioned on multiple occasions how pleased (and surprised) they were to realize how powerful their database of metadata has proven to be. All the amazing value added features build on this &#8216;heavy lifting&#8217;.</p>
<p>While it will be rare for such item level attention to be given to most archival documents, PBO sets the bar high for what can be done via collaboration across institutions. Their dedication to sharing their lessons learned is a fine example of what all big projects who are forging new frontiers could be doing. Finally &#8211; it is the weight of all the value added elements (galleries, tutorials, lesson plans.. and the list goes on) that have raised what could have been just a set of classified images in a database to being an active community with a growing draw for many types of users from around the world.</p>
<p><em>As is the case with all my session summaries from SAA2007, please accept my apologies in advance for any cases in which I misquote, overly simplify or miss points altogether in the post above. These sessions move fast and my main goal is to capture the core of the ideas presented and exchanged. Feel free to contact me about corrections to my summary either via comments on this post or via my <a href="http://www.spellboundblog.com/contact/" title="SpellboundBlog Contact Form">contact form</a>.</em></p>
<p>This post is from from: <a href="http://www.spellboundblog.com">Spellbound Blog</a>.<br/><br/><a href="http://www.spellboundblog.com/2007/09/22/saa2007-publishers%e2%80%99-bindings-online-digitization-collaboration-standardization-and-community-building-session-707/">SAA2007: Publishers’ Bindings Online &#8211; Digitization, Collaboration, Standardization and Community Building (Session 707)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.spellboundblog.com/2007/09/22/saa2007-publishers%e2%80%99-bindings-online-digitization-collaboration-standardization-and-community-building-session-707/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

