<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: A study of scanning habits</title>
	<atom:link href="http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html/feed" rel="self" type="application/rss+xml" />
	<link>http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html</link>
	<description>a library weblog by Steve Lawson</description>
	<lastBuildDate>Wed, 26 Oct 2011 17:57:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Alain Pierrot</title>
		<link>http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html/comment-page-1#comment-3626</link>
		<dc:creator>Alain Pierrot</dc:creator>
		<pubDate>Mon, 20 Aug 2007 14:40:40 +0000</pubDate>
		<guid isPermaLink="false">http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html#comment-3626</guid>
		<description>&lt;blockquote&gt;“David, what about “the medium is the message?” As I say, I expect we will have massive amounts of usable e-books some day, maybe even soon, but the experience of reading a paper book and that of reading an e-book won’t necessarily be equivalent.”&lt;/blockquote&gt;
While I fully agree with that, I am less convinced by the discussion about &quot;container&quot; and &quot;story&quot;:
Jean-Michel Salaün, &lt;a href=&quot;http://blogues.ebsi.umontreal.ca/jms/index.php/2007/08/14/298-la-trahison-de-google-book&quot; rel=&quot;nofollow&quot;&gt;commenting (in French)&lt;/a&gt; about Paul Duguid&#039;s article reminds us that documents could (should?) be considered as having &lt;strong&gt;three&lt;/strong&gt; dimensions:
&lt;blockquote&gt;“* Anthropologique : Forme (Document = Support + Inscription)
    * Intellectuelle : Texte (Document = Code + représentation)
    * Sociale : Médium (Document = Mémoire + transaction)”&lt;/blockquote&gt;
(my translation)
Anthopological : Form (Document = Format + Inscription)
Intellectual : Text (Document = Code + representation)
Social : Medium (Document = Memory + transaction)

In order to render the original (book) document, the digitization process should consider the three different aspects, which goes — most of the time — further than the mere distinction between &quot;container&quot; and &quot;story&quot;.</description>
		<content:encoded><![CDATA[<blockquote><p>“David, what about “the medium is the message?” As I say, I expect we will have massive amounts of usable e-books some day, maybe even soon, but the experience of reading a paper book and that of reading an e-book won’t necessarily be equivalent.”</p></blockquote>
<p>While I fully agree with that, I am less convinced by the discussion about &#8220;container&#8221; and &#8220;story&#8221;:<br />
Jean-Michel Salaün, <a href="http://blogues.ebsi.umontreal.ca/jms/index.php/2007/08/14/298-la-trahison-de-google-book" rel="nofollow">commenting (in French)</a> about Paul Duguid&#8217;s article reminds us that documents could (should?) be considered as having <strong>three</strong> dimensions:</p>
<blockquote><p>“* Anthropologique : Forme (Document = Support + Inscription)<br />
    * Intellectuelle : Texte (Document = Code + représentation)<br />
    * Sociale : Médium (Document = Mémoire + transaction)”</p></blockquote>
<p>(my translation)<br />
Anthopological : Form (Document = Format + Inscription)<br />
Intellectual : Text (Document = Code + representation)<br />
Social : Medium (Document = Memory + transaction)</p>
<p>In order to render the original (book) document, the digitization process should consider the three different aspects, which goes — most of the time — further than the mere distinction between &#8220;container&#8221; and &#8220;story&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Book, music, communication, content, social</title>
		<link>http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html/comment-page-1#comment-3606</link>
		<dc:creator>Book, music, communication, content, social</dc:creator>
		<pubDate>Fri, 17 Aug 2007 22:13:55 +0000</pubDate>
		<guid isPermaLink="false">http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html#comment-3606</guid>
		<description>[...] Also&#8230;, A study of scanning habit  : a couple of [...]</description>
		<content:encoded><![CDATA[<p>[...] Also&#8230;, A study of scanning habit  : a couple of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bowerbird</title>
		<link>http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html/comment-page-1#comment-3604</link>
		<dc:creator>bowerbird</dc:creator>
		<pubDate>Fri, 17 Aug 2007 20:46:42 +0000</pubDate>
		<guid isPermaLink="false">http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html#comment-3604</guid>
		<description>i am the person dorothea lambasted in her blog entry of 4 years ago. (and i&#039;m amazed that she&#039;s still pointing to that hatchet-job she did.) at any rate, i still maintain that digitization is _not_ a difficult process.

the fact that google can&#039;t seem to get it right doesn&#039;t mean it&#039;s _hard_.

duguid (whose earlier article i admired) was very slipshod with this one.

he points to blurry scans.  and they&#039;re entirely unforgiveable, of course. but does anyone here really think it&#039;s _difficult_ to get nonblurry scans?

likewise, duguid discovers google has lost track of the volume numbers. but does anyone believe that noting volume numbers is inherently hard?

or take the fact that google confused the list of illustrations in &quot;shandy&quot; as a table of contents.  was this because it&#039;s _hard_ to tell &#039;em apart?  no, it&#039;s because there was no table of contents, so it found the closest thing.

***

why is google making such stupid mistakes?  probably because they hire people at minimum wage for a job that requires very close concentration. and -- even more importantly -- because their quality control _sucks_...

but to pretend this job is _difficult_ is laughable, in the extreme.

***

dorothea&#039;s post is quoted here:
&gt;   We have to sweat over math, art, indexes, tables, links, 
&gt;   complex layouts, production workflows, metadata, 
&gt;   non-Roman alphabets, digital preservation issues, 
&gt;   and all that fun stuff.

math = graphics (or latex, if you&#039;re nasty).
art = graphics.
indexes = indexes, hotlinked please.
tables = tables.
links = links.
complex layouts = oh, poor dear, yes, that layout _is_ complex.  sheesh!
production workflows = gobbledygook.
metadata = shmetadata.
non-roman alphabets = unicode.
digital preservation issues = mirror stuff to new formats constantly.
all that fun stuff = make up your mind; is it hard or is it fun?

none of this is hard.  i repeat, _none_ of it.

the vast majority of books can be digitized in a straightforward manner.

dorothea would have you think that i believe this because i&#039;m &quot;stupid or clueless&quot; and have no experience digitizing books. but she declined to identify me, so you couldn&#039;t check up on her little hatchet-job.

-bowerbird</description>
		<content:encoded><![CDATA[<p>i am the person dorothea lambasted in her blog entry of 4 years ago. (and i&#8217;m amazed that she&#8217;s still pointing to that hatchet-job she did.) at any rate, i still maintain that digitization is _not_ a difficult process.</p>
<p>the fact that google can&#8217;t seem to get it right doesn&#8217;t mean it&#8217;s _hard_.</p>
<p>duguid (whose earlier article i admired) was very slipshod with this one.</p>
<p>he points to blurry scans.  and they&#8217;re entirely unforgiveable, of course. but does anyone here really think it&#8217;s _difficult_ to get nonblurry scans?</p>
<p>likewise, duguid discovers google has lost track of the volume numbers. but does anyone believe that noting volume numbers is inherently hard?</p>
<p>or take the fact that google confused the list of illustrations in &#8220;shandy&#8221; as a table of contents.  was this because it&#8217;s _hard_ to tell &#8216;em apart?  no, it&#8217;s because there was no table of contents, so it found the closest thing.</p>
<p>***</p>
<p>why is google making such stupid mistakes?  probably because they hire people at minimum wage for a job that requires very close concentration. and &#8212; even more importantly &#8212; because their quality control _sucks_&#8230;</p>
<p>but to pretend this job is _difficult_ is laughable, in the extreme.</p>
<p>***</p>
<p>dorothea&#8217;s post is quoted here:<br />
&gt;   We have to sweat over math, art, indexes, tables, links,<br />
&gt;   complex layouts, production workflows, metadata,<br />
&gt;   non-Roman alphabets, digital preservation issues,<br />
&gt;   and all that fun stuff.</p>
<p>math = graphics (or latex, if you&#8217;re nasty).<br />
art = graphics.<br />
indexes = indexes, hotlinked please.<br />
tables = tables.<br />
links = links.<br />
complex layouts = oh, poor dear, yes, that layout _is_ complex.  sheesh!<br />
production workflows = gobbledygook.<br />
metadata = shmetadata.<br />
non-roman alphabets = unicode.<br />
digital preservation issues = mirror stuff to new formats constantly.<br />
all that fun stuff = make up your mind; is it hard or is it fun?</p>
<p>none of this is hard.  i repeat, _none_ of it.</p>
<p>the vast majority of books can be digitized in a straightforward manner.</p>
<p>dorothea would have you think that i believe this because i&#8217;m &#8220;stupid or clueless&#8221; and have no experience digitizing books. but she declined to identify me, so you couldn&#8217;t check up on her little hatchet-job.</p>
<p>-bowerbird</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html/comment-page-1#comment-3600</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Fri, 17 Aug 2007 18:57:19 +0000</pubDate>
		<guid isPermaLink="false">http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html#comment-3600</guid>
		<description>Yay, I agree with David!  It &lt;i&gt;is&lt;/i&gt; the &quot;story&quot; that matters and it can come in all sorts of containers. 

And, often, we do speak loosely of a book as the content.

If we want to FRBR-ize the discussion then in my stricter definition it is nonsensical to talk about a book as any FRBR entity.  A book as container would be part of the thing being described as a manifestation (well, not really, but I&#039;ll leave this philosophical issue aside) and certainly part of the item (if it is a book) being described.

In the loose sense of speaking, we could say that a book is the item.  But in this case, and actually especially (hmm?), in this case the book is only the container.  The work (the story) has already been cataloged at the work/expression level.

Yes! In fact, in FRBR there isn&#039;t a single thing about the story that is part of the item.  It is only individual carrier info--bar code, provenance, condition of the item, etc.  Manifestation is pretty much the same.

E.g., see the RDA-FRBR mappings:
http://www.collectionscanada.ca/jsc/docs/5rda-frbrmapping.pdf

So, David, if you were only talking about the story all along then, on one hand I apologize for butting in.  But on the other, I could not tell exactly what you meant because of the collapse of a distinction that I felt important (in many cases; again, not all).

David, I fully agree with you (and Iris and others) that, except in the ways Walt suggests matter, container should not matter.  

Recorded story is recorded story, and reading is reading.  

Certainly there are things that can be teased apart between reading a quality print item versus reading from a screen, and reading some kinds of materials &lt;i&gt;may&lt;/i&gt; be better than others....  I guess I just feel these differences reside at a finer grain, perhaps, and thus won&#039;t need to be trotted out as often.

Anyway, thanks for the conversation all; in all the various places we have spread it.</description>
		<content:encoded><![CDATA[<p>Yay, I agree with David!  It <i>is</i> the &#8220;story&#8221; that matters and it can come in all sorts of containers. </p>
<p>And, often, we do speak loosely of a book as the content.</p>
<p>If we want to FRBR-ize the discussion then in my stricter definition it is nonsensical to talk about a book as any FRBR entity.  A book as container would be part of the thing being described as a manifestation (well, not really, but I&#8217;ll leave this philosophical issue aside) and certainly part of the item (if it is a book) being described.</p>
<p>In the loose sense of speaking, we could say that a book is the item.  But in this case, and actually especially (hmm?), in this case the book is only the container.  The work (the story) has already been cataloged at the work/expression level.</p>
<p>Yes! In fact, in FRBR there isn&#8217;t a single thing about the story that is part of the item.  It is only individual carrier info&#8211;bar code, provenance, condition of the item, etc.  Manifestation is pretty much the same.</p>
<p>E.g., see the RDA-FRBR mappings:<br />
<a href="http://www.collectionscanada.ca/jsc/docs/5rda-frbrmapping.pdf" rel="nofollow">http://www.collectionscanada.ca/jsc/docs/5rda-frbrmapping.pdf</a></p>
<p>So, David, if you were only talking about the story all along then, on one hand I apologize for butting in.  But on the other, I could not tell exactly what you meant because of the collapse of a distinction that I felt important (in many cases; again, not all).</p>
<p>David, I fully agree with you (and Iris and others) that, except in the ways Walt suggests matter, container should not matter.  </p>
<p>Recorded story is recorded story, and reading is reading.  </p>
<p>Certainly there are things that can be teased apart between reading a quality print item versus reading from a screen, and reading some kinds of materials <i>may</i> be better than others&#8230;.  I guess I just feel these differences reside at a finer grain, perhaps, and thus won&#8217;t need to be trotted out as often.</p>
<p>Anyway, thanks for the conversation all; in all the various places we have spread it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Iris</title>
		<link>http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html/comment-page-1#comment-3597</link>
		<dc:creator>Iris</dc:creator>
		<pubDate>Fri, 17 Aug 2007 16:27:05 +0000</pubDate>
		<guid isPermaLink="false">http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html#comment-3597</guid>
		<description>Heh. &quot;Reading&quot; being more than holding a book... that needs to be explained to all the people who say kids don&#039;t spend any time &quot;reading&quot; these days because they&#039;re too busy texting and IMing. :)

Sorry to go off topic a little... I now return you to your regularly scheduled discussion.</description>
		<content:encoded><![CDATA[<p>Heh. &#8220;Reading&#8221; being more than holding a book&#8230; that needs to be explained to all the people who say kids don&#8217;t spend any time &#8220;reading&#8221; these days because they&#8217;re too busy texting and IMing. :)</p>
<p>Sorry to go off topic a little&#8230; I now return you to your regularly scheduled discussion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david lee king</title>
		<link>http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html/comment-page-1#comment-3596</link>
		<dc:creator>david lee king</dc:creator>
		<pubDate>Fri, 17 Aug 2007 15:39:03 +0000</pubDate>
		<guid isPermaLink="false">http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html#comment-3596</guid>
		<description>No Walt, I think you&#039;re correct. &quot;Denigrate&quot; is much too strong of a word... and I don&#039;t actually &quot;denigrate&quot; paper books. In fact, I have a whole stack of them to read right now!

I think what I&#039;m trying to get at is this: I see some public libraries build whole websites and huge programs around paper books, and actually get sorta mad when presented with the possibility that people at some future point in time might not equate paper and books (or texts).

I even see librarians that don&#039;t understand that the concept of &quot;reading&quot; means much more than holding a paper book in one&#039;s hands.

So I&#039;m just trying to explain that I think there&#039;s a huge difference between where you are reading the words (on a page, on a screen, etc) and the words themselves.

I think &quot;denigrate&quot; came from a comment or post Steve made, and I commented on that and used his comment on my words as a starting point... and this is probably where conversations in comment boxes start to break down. Kind of like how USENET conversations got lopsided pretty fast :-)</description>
		<content:encoded><![CDATA[<p>No Walt, I think you&#8217;re correct. &#8220;Denigrate&#8221; is much too strong of a word&#8230; and I don&#8217;t actually &#8220;denigrate&#8221; paper books. In fact, I have a whole stack of them to read right now!</p>
<p>I think what I&#8217;m trying to get at is this: I see some public libraries build whole websites and huge programs around paper books, and actually get sorta mad when presented with the possibility that people at some future point in time might not equate paper and books (or texts).</p>
<p>I even see librarians that don&#8217;t understand that the concept of &#8220;reading&#8221; means much more than holding a paper book in one&#8217;s hands.</p>
<p>So I&#8217;m just trying to explain that I think there&#8217;s a huge difference between where you are reading the words (on a page, on a screen, etc) and the words themselves.</p>
<p>I think &#8220;denigrate&#8221; came from a comment or post Steve made, and I commented on that and used his comment on my words as a starting point&#8230; and this is probably where conversations in comment boxes start to break down. Kind of like how USENET conversations got lopsided pretty fast :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: walt crawford</title>
		<link>http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html/comment-page-1#comment-3595</link>
		<dc:creator>walt crawford</dc:creator>
		<pubDate>Fri, 17 Aug 2007 15:23:22 +0000</pubDate>
		<guid isPermaLink="false">http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html#comment-3595</guid>
		<description>You know, I just skipped over something in this fascinating multiblog conversation--probably because I only read it on the screen.

To wit, &quot;I don’t denigrate books. I denigrate the container,&quot;

I&#039;ll avoid the issue of the definition of &quot;book&quot; (which, I submit, is ambiguous, but there are much better minds in this collective and I&#039;m learning from the various perspectives) and just wonder why there&#039;s any point in &quot;denigrating the container.&quot;

I mean, unless (David) you really are saying &quot;digital is always better,&quot; then why denigrate? If a different container works better for some people for some uses, fine--point out the virtues of that container. But unless there&#039;s something actually defective about a bound collection of printed pages as a way to read long linear text--and the, um, overwhelming popularity of the Rocket Ebook and various others (including Sony&#039;s device) seem to suggest that most people aren&#039;t anxiously looking for a replacement--then denigrating physical books just seems silly.

I suppose this comment belongs on DLK&#039;s blog...but the emphasis on those two sentences in this post broke through my poor on-screen retention. Thanks.</description>
		<content:encoded><![CDATA[<p>You know, I just skipped over something in this fascinating multiblog conversation&#8211;probably because I only read it on the screen.</p>
<p>To wit, &#8220;I don’t denigrate books. I denigrate the container,&#8221;</p>
<p>I&#8217;ll avoid the issue of the definition of &#8220;book&#8221; (which, I submit, is ambiguous, but there are much better minds in this collective and I&#8217;m learning from the various perspectives) and just wonder why there&#8217;s any point in &#8220;denigrating the container.&#8221;</p>
<p>I mean, unless (David) you really are saying &#8220;digital is always better,&#8221; then why denigrate? If a different container works better for some people for some uses, fine&#8211;point out the virtues of that container. But unless there&#8217;s something actually defective about a bound collection of printed pages as a way to read long linear text&#8211;and the, um, overwhelming popularity of the Rocket Ebook and various others (including Sony&#8217;s device) seem to suggest that most people aren&#8217;t anxiously looking for a replacement&#8211;then denigrating physical books just seems silly.</p>
<p>I suppose this comment belongs on DLK&#8217;s blog&#8230;but the emphasis on those two sentences in this post broke through my poor on-screen retention. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Lawson</title>
		<link>http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html/comment-page-1#comment-3594</link>
		<dc:creator>Steve Lawson</dc:creator>
		<pubDate>Fri, 17 Aug 2007 13:24:32 +0000</pubDate>
		<guid isPermaLink="false">http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html#comment-3594</guid>
		<description>David, I think the word that academics tend to use in that context is &quot;text.&quot; 

FRBR-ized librarians might prefer to say that David is talking about a &quot;work&quot; or &quot;expression&quot; while Mark is talking about the &quot;manifestation&quot; or &quot;item.&quot; (I&#039;m not a FRBR expert, though. The distinction between &quot;work&quot; and &quot;expression&quot; seems very slippery to me.)</description>
		<content:encoded><![CDATA[<p>David, I think the word that academics tend to use in that context is &#8220;text.&#8221; </p>
<p>FRBR-ized librarians might prefer to say that David is talking about a &#8220;work&#8221; or &#8220;expression&#8221; while Mark is talking about the &#8220;manifestation&#8221; or &#8220;item.&#8221; (I&#8217;m not a FRBR expert, though. The distinction between &#8220;work&#8221; and &#8220;expression&#8221; seems very slippery to me.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david lee king</title>
		<link>http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html/comment-page-1#comment-3593</link>
		<dc:creator>david lee king</dc:creator>
		<pubDate>Fri, 17 Aug 2007 13:15:35 +0000</pubDate>
		<guid isPermaLink="false">http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html#comment-3593</guid>
		<description>Another way to think about it... a story. Used to be spoken only (oral tradition before people started writing things down), then the story appeared in drawings, then the story appeared on clay tablets, then on scrolls, and now, finally, on books. No, wait... also on blogs, in PDF, in many different emerging forms of e-book... 

But it&#039;s all the same story.</description>
		<content:encoded><![CDATA[<p>Another way to think about it&#8230; a story. Used to be spoken only (oral tradition before people started writing things down), then the story appeared in drawings, then the story appeared on clay tablets, then on scrolls, and now, finally, on books. No, wait&#8230; also on blogs, in PDF, in many different emerging forms of e-book&#8230; </p>
<p>But it&#8217;s all the same story.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david lee king</title>
		<link>http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html/comment-page-1#comment-3592</link>
		<dc:creator>david lee king</dc:creator>
		<pubDate>Fri, 17 Aug 2007 13:11:29 +0000</pubDate>
		<guid isPermaLink="false">http://stevelawson.name/seealso/archives/2007/08/a_study_of_scanning_habits.html#comment-3592</guid>
		<description>Gee whiz, Mark... ok. You&#039;re correct. Instead of &quot;book&quot; in my comment above, please insert: novel, novella, large work of gathered poetry, large multi-chapter work of non-fiction, etc.

Does that clarify my comment any?</description>
		<content:encoded><![CDATA[<p>Gee whiz, Mark&#8230; ok. You&#8217;re correct. Instead of &#8220;book&#8221; in my comment above, please insert: novel, novella, large work of gathered poetry, large multi-chapter work of non-fiction, etc.</p>
<p>Does that clarify my comment any?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

