<?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>North Carolina Digital Collections Collaboratory &#187; Flickr</title>
	<atom:link href="http://digital.lib.ecu.edu/collaboratory/index.php?feed=rss2&#038;cat=25" rel="self" type="application/rss+xml" />
	<link>http://digital.lib.ecu.edu/collaboratory</link>
	<description>Bringing North Carolina Digital Collections Together</description>
	<lastBuildDate>Wed, 26 Jan 2011 20:56:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Preserving Forsyth&#8217;s Past: creating local digital collections</title>
		<link>http://digital.lib.ecu.edu/collaboratory/?p=404</link>
		<comments>http://digital.lib.ecu.edu/collaboratory/?p=404#comments</comments>
		<pubDate>Thu, 10 Jun 2010 17:45:00 +0000</pubDate>
		<dc:creator>Audra</dc:creator>
				<category><![CDATA[Flickr]]></category>
		<category><![CDATA[Wake Forest]]></category>
		<category><![CDATA[digitization]]></category>
		<category><![CDATA[grants]]></category>

		<guid isPermaLink="false">http://digital.lib.ecu.edu/collaboratory/?p=404</guid>
		<description><![CDATA[In June 2009, Wake Forest University&#8217;s Z. Smith Reynolds Library and Forsyth County Public Library were awarded an LSTA Library Outreach Services grant by the State Library of North Carolina for a project entitled &#8220;Preserving Forsyth&#8217;s Past.&#8221; Originally intended as an expansion of the popular Digital Forsyth project that would help smaller institutions in the [...]]]></description>
			<content:encoded><![CDATA[<p>In June 2009, Wake Forest University&#8217;s Z. Smith Reynolds Library and Forsyth County Public Library were awarded an LSTA Library Outreach Services grant by the State Library of North Carolina for a project entitled &#8220;Preserving Forsyth&#8217;s Past.&#8221; Originally intended as an expansion of the popular <a href="http://www.digitalforsyth.org/" target="_blank">Digital Forsyth</a> project that would help smaller institutions in the county digitize their historic photographs, the project morphed into a new animal altogether. Instead of another collaborative digitization project, Preserving Forsyth&#8217;s Past would be an outreach effort to make accessible digitization equipment and provide preservation training for community organizations and the general public.</p>
<p>The grant allowed WFU and FCPL to purchase equipment for five digitization centers at library locations throughout Forsyth County (Z. Smith Reynolds Library and four FCPL locations: Central Library, Walkertown Branch Library, Lewisville Branch Library, and the Malloy/Jordan East Winston Heritage Center). In addition, it provided funding for guest speakers to do preservation and digitization instruction in a day-long workshop format. The first of the five workshops was a pilot, followed by another session reserved for members of local community organizations (postcard announcements were sent to everyone from the Afro-American Genealogical and Historical Society to the local railroad history appreciation society). Subsequent sessions were open to the general public. <span id="more-404"></span></p>
<p>One thing we recognized after the sessions became open to the public was a strong interest in preservation and digitization. Community members brought in yearbooks, photo albums, family bibles, and other items as well as lots of questions about how to use the flatbed scanner, VHS to digital converter, audio cassette to digital converter, and slide scanner. Barry Davis, Digital Production Coordinator at ZSR, helped create online <a href="http://cloud.lib.wfu.edu/blog/tech/" target="_blank">guides to using the equipment</a> and will be posting online videos demonstrating both physical preservation and how to use the equipment. Local families, history societies, and organizations hold small but valuable records of our community&#8217;s past &#8212; and they want to preserve them.</p>
<p>After demonstrating the use of the digitization equipment, the public was informed that they could participate in Digital Forsyth by sharing their digital and digitized photos through the <a href="http://www.flickr.com/groups/digital_forsyth/" target="_blank">Digital Forsyth Flickr group</a> (also available through the Digital Forsyth <a href="http://www.digitalforsyth.org/community/" target="_blank">community page</a>). The group&#8217;s page notes that images may be harvested for use in Digital Forsyth. We ask participants to post other formats to YouTube, Internet Archive, and Scribd, since we do not provide storage space for these materials. These local digital collections, ideally, can be shared in multiple ways. Training for how to use the equipment will continue through the Forsyth County <a href="http://forsythcomputertraining.org/" target="_blank">Computer Training Bridge</a> at various locations around the county.</p>
<p>With the grant wrapping up at the end of this month, I have had time to reflect on how I think the project could have been improved. While organizations and the general public were thrilled with free seminars about hands-on preservation, organization, and digitization, we did not spend much time talking about what would be done with materials post-digitization. Concepts like metadata and digital storage are only briefly touched upon and could be emphasized in the future. In addition, there is still potential for the community to participate in a larger version of Digital Forsyth that collocates multiple digital formats to preserve the many layers of this area&#8217;s history and culture. In sum, it has been a joy to experience firsthand the effort to include personal collections and community-based archives in the discussion about digitization.</p>
]]></content:encoded>
			<wfw:commentRss>http://digital.lib.ecu.edu/collaboratory/?feed=rss2&amp;p=404</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>What Flickr portends, in the long-(tail)-run</title>
		<link>http://digital.lib.ecu.edu/collaboratory/?p=59</link>
		<comments>http://digital.lib.ecu.edu/collaboratory/?p=59#comments</comments>
		<pubDate>Wed, 11 Mar 2009 18:37:36 +0000</pubDate>
		<dc:creator>Mark</dc:creator>
				<category><![CDATA[ECU]]></category>
		<category><![CDATA[Flickr]]></category>
		<category><![CDATA[SAA]]></category>
		<category><![CDATA[digital preservation]]></category>
		<category><![CDATA[digitization]]></category>
		<category><![CDATA[metadata]]></category>
		<category><![CDATA[Hathi Trust]]></category>
		<category><![CDATA[Special Collections]]></category>

		<guid isPermaLink="false">http://digital.lib.ecu.edu/collaboratory/?p=59</guid>
		<description><![CDATA[I&#8217;ve been meaning to write about my experience with Flickr for some time, but in some ways it&#8217;s better that this is following Brian&#8217;s excellent post. My best guess, I&#8217;ll plainly state, is that in the wake of Google&#8217;s mass digitization of published works (books, magazines, journals), major research libraries will only be distinguishable by [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been meaning to write about my experience with Flickr for some time, but in some ways it&#8217;s better that this is following Brian&#8217;s excellent post. My best guess, I&#8217;ll plainly state, is that in the wake of Google&#8217;s mass digitization of published works (books, magazines, journals), major research libraries will only be distinguishable by three things:<br />
<span id="more-59"></span></p>
<ol>
<li>their architecture (physical)</li>
<li>their librarians (departments)</li>
<li>their collections (special -&gt; digital)</li>
</ol>
<p>The most flexible and adaptable of these differentiating factors, then, will most likely be our websites and digitized items (eventually, perhaps, our “linked data”). Certainly the physical architecture of the libraries will change most slowly, but with an average website “face-lift” occurring &#8212; let&#8217;s say &#8212; every three years, presently it may actually be the case that the average time frame of personnel shift amongst libraries/departments is approximately equal to any major attention lavished on the website and/or the addition/migration of major digitized collections. But soon, surely, it will be indisputable that it&#8217;s our digital collections alone that will be our most adaptable differentiating factor.</p>
<p>As such, it will equally be the most powerful method to level the variances between our libraries (think “open source software”) and, paradoxically, also the most powerful method to differentiate our libraries (think local developments on top of “open source software”). Furthermore, though our digitized surrogates will certainly retain the provenance of their real-world counterparts by means of metadata, my contention is that in the eventual wake of the mass digitization of special collections, major research libraries will only be distinguishable by &#8212; not three &#8212; but just two things:</p>
<ol>
<li>their architecture</li>
<li>their librarians</li>
</ol>
<p>And so, as our most unique resources become de-referenceable, these acts will slowly but eventually erase all differences in our collections (barring, of course, or perhaps only being slowed by, forced authentication and registration of online “researchers”) and return libraries to a pre-website state.</p>
<p>Rather than being feared, however, this should be our ultimate goal. Though universities will certainly retain their differences and specialties, the special collections of the libraries (those available online) will become the collections of all (of course, libraries will still need to maintain these collections, but it&#8217;s likely that they&#8217;ll perform this as a shared and proportionally balanced duty).</p>
<p>I should clarify, though: being returned to a “pre-website state” will not mean that a library will suddenly cease to exist online. Rather, the library&#8217;s online existence will no longer be controlled and contained, at least not in the same manner (and the site, as we know it now, might simply not need to exist).   And this, finally, brings me back to Flickr, a small but timely example of the changes ahead.</p>
<p>But first, I should say, I had little to no experience with Flickr when setting out to include a sample of ECU&#8217;s digital collections  (<a href="http://www.flickr.com/photos/ecu_digital_collections">http://www.flickr.com/photos/ecu_digital_collections</a>). I mention this at the onset to highlight Flickr&#8217;s ease of use and, also, the potential reasoning behind my false steps along the way, especially since I ended up working through the necessary steps in, literally, a backward fashion.</p>
<p>What follows is a bullet-list summary of my experience in the process so far (and please feel free to ask me about any particulars).</p>
<p><strong>Basic steps:</strong></p>
<ul>
<li>Requested a free, non-commericial API from Flickr (<a href="http://www.flickr.com/services/api/">http://www.flickr.com/services/api/</a>)</li>
<li>Selected public domain/copyright free items to share</li>
<li>Batched and resized images to save space (wanted to be under the free account&#8217;s 100 MB/month cap)</li>
<li>Wrote an XSLT stylsheet to remove just a few pieces of data from our METS record
<ol>
<li>Title</li>
<li>Description</li>
<li>Date</li>
<li>Persistent URL</li>
</ol>
</li>
<li>Added just one or two tags to each image based on &#8220;format&#8221; and &#8220;virtual collection&#8221; (opted not to add our subjects as tags or to display them at all)</li>
<li>Used a text editor to take the output and put into a Python file, generally making sure that I wrapped strings in triple quotes</li>
<li>Finally, I used &#8220;<a href="http://stuvel.eu/projects/flickrapi">Beej&#8217;s Python Flickr API kit</a>&#8221; for the mass upload and user authentication</li>
</ul>
<p><strong>Next steps:</strong></p>
<ul>
<li>Update my old images with &#8220;<a href="http://www.flickr.com/groups/api/discuss/72157594497877875/">machine tags</a>&#8220;, as I neglected this in my first round</li>
<li>Add a new set (the free account lets you have up to three)</li>
<li>Get the Pro account</li>
<li>Use the API to funnel the comments and tags from Flickr to our site, thereby linking user-supplied data from this <a href="http://www.flickr.com/photos/ecu_digital_collections/3289183842/">Flickr image</a> to that <a href="http://digital.lib.ecu.edu/5053">same image</a> in our digital repository, which doesn&#8217;t yet have that comment or tag.</li>
<li>Join <a href="http://www.flickr.com/commons/">The Commons on Flickr</a> if approved</li>
</ul>
<p><strong>And things to consider if you set up a Flickr account:</strong></p>
<ul>
<li>Don&#8217;t select a birthday that would make you under 18, or else you&#8217;ll need to use a credit card to verify parental consent (as if that alone won&#8217;t make everyone underage grow up quite quickly)</li>
<li>If you&#8217;re using a free account, remember that though you&#8217;re able to upload 100MB a month, only your 200 most recent images will be displayed</li>
</ul>
<p><strong>Some interesting Library/Flickr articles to read:</strong></p>
<ul>
<li><a href="http://www.nytimes.com/2009/01/19/technology/internet/19link.html">Historical Photos in Web Archives Gain Vivid New Lives</a> by Noam Cohen</li>
<li><a href="http://journal.code4lib.org/articles/74">Developing an Academic Image Collection with Flickr</a> by Jeremy McWilliams</li>
</ul>
<p><strong>And finally:</strong></p>
<p>As our collections continue to disperse in the digital age, and as our collections begin to arrive in a predominately digital format, it&#8217;s my hope that we&#8217;ll be able to receive donations that can be shared online without restrictions.</p>
<p>At the same time, SAA and archivists in general will need to vigilantly campaign against the potential misappropriation of our collections.  Though commercial partners and vendors might not offer to digitize our special collections for free, they will certainly come knocking on the doors soon enough, explaining that they can host our vast collections; but in this respect I hope that we do not yield.  If we do, we&#8217;ll surely trap not only our libraries, but also our users; and, being a trap, the situation won&#8217;t come equipped with something as user-friendly as the Flicrk API to permit the free passport of our collections and users.  Certainly, then, there&#8217;s no reason that we shouldn&#8217;t already be imagining the equivalent of the <a href="http://www.hathitrust.org/">Hathi Trust</a> for our special collection materials.</p>
]]></content:encoded>
			<wfw:commentRss>http://digital.lib.ecu.edu/collaboratory/?feed=rss2&amp;p=59</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>
