1
0
Fork 0
mirror of https://github.com/futurepress/epub.js.git synced 2025-10-04 15:09:16 +02:00

upped version

This commit is contained in:
Fred Chasen 2013-04-01 13:39:39 -07:00
parent 0e68ec6c9e
commit 674e56c330
65 changed files with 17685 additions and 0 deletions

View file

@ -0,0 +1,2 @@
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<container xmlns="urn:oasis:names:tc:opendocument:xmlns:container" version="1.0"><rootfiles><rootfile full-path="OEBPS/content.opf" media-type="application/oebps-package+xml"/></rootfiles></container>

Binary file not shown.

BIN
TDO/OEBPS/DejaVuSerif.otf Normal file

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

385
TDO/OEBPS/bi01.html Normal file

File diff suppressed because one or more lines are too long

4
TDO/OEBPS/bk01-toc.html Normal file

File diff suppressed because one or more lines are too long

1621
TDO/OEBPS/ch01.html Normal file

File diff suppressed because it is too large Load diff

1785
TDO/OEBPS/ch02.html Normal file

File diff suppressed because it is too large Load diff

1494
TDO/OEBPS/ch03.html Normal file

File diff suppressed because it is too large Load diff

1617
TDO/OEBPS/ch04.html Normal file

File diff suppressed because it is too large Load diff

1391
TDO/OEBPS/ch05.html Normal file

File diff suppressed because it is too large Load diff

1318
TDO/OEBPS/ch06.html Normal file

File diff suppressed because it is too large Load diff

1299
TDO/OEBPS/ch07.html Normal file

File diff suppressed because it is too large Load diff

1492
TDO/OEBPS/ch08.html Normal file

File diff suppressed because it is too large Load diff

1262
TDO/OEBPS/ch09.html Normal file

File diff suppressed because it is too large Load diff

1101
TDO/OEBPS/ch10.html Normal file

File diff suppressed because it is too large Load diff

25
TDO/OEBPS/co01.html Normal file
View file

@ -0,0 +1,25 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>Colophon</title><link rel="stylesheet" type="text/css" href="core.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"/><meta name="keywords" content="organizing, information, resources, metadata, resource description"/><link rel="up" href="index.html" title="The Discipline of Organizing"/><link rel="prev" href="ix01.html" title="Index"/><link rel="next" href="copyright.html" title=""/></head><body><div class="colophon" title="Colophon" epub:type="colophon" id="Colophon"><h2 class="title">Colophon</h2><p>The cover is <em class="citetitle">An Intentional Arrangement</em>
by <span class="personname"><span class="firstname">Jen</span> <span class="surname">Wang</span></span>. The cover font is HTF Knockout.
(A concept involving progressive organization of wooden alphabet blocks was rejected as suggesting a childrens book.)</p><p>The authors and editors managed their textual content on DropBox using various versions of Microsoft Word.
Those Word documents were transformed into DocBook representations using scripts and hand editing.
The DocBook files were then encoded with extensive semantic tagging and hypertext relationships,
including references and transclusion of content from the chapters into the glossary.
The editors used oXygen, XML Spy and XMetaL word processors on OS X and Windows platforms.
Customized XSLT scripts transformed the DocBook files into XHTML 5 which then served as the basis for
further transformations using CSS and/or XSLT to produce the printed, PDF, XHTML, ePub or Mobi format document
that you are reading now.</p><p>The printed edition of <em class="citetitle">The Discipline of Organizing</em>
was built with <a class="ulink" href="http://atlas.labs.oreilly.com" target="_top">Altas</a> from OReilly Media.
The content of the printed book uses OpenType DejaVu fonts.
We started with the source files
(<a class="ulink" href="http://dejavu-fonts.org/wiki/Main_Page" target="_top"><code class="uri">http://dejavu-fonts.org/wiki/Main_Page</code></a>)
to generate custom OTF versions.
The text font is DejaVuSerif;
the heading font is DejaVuSans.
The monospaced font used for code samples and literal text is DejaVuMono.
The condensed font used in the index is DejaVuSerifCondensed;
some labels use DejaVuSansCondensed.
A small number of characters require a Unicode font to represent them;
the Unicode font used for print and PDF versions of this book is Adobe Song Standard.
Emphasis is presented in italic and bold faces of the corresponding font families.</p><p>The electronic book editions (ePub 2 and ePub 3) were built using customized XSLT scripts created by Bob Stayton,
<a class="ulink" href="http://www.sagehill.net/" target="_top">Sagehill Enterprises</a>.</p></div></body></html>

191
TDO/OEBPS/content.opf Normal file
View file

@ -0,0 +1,191 @@
<?xml version='1.0' encoding='UTF-8'?>
<package xmlns="http://www.idpf.org/2007/opf" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" prefix="ibooks: http://vocabulary.itunes.apple.com/rdf/ibooks/vocabulary-extensions-1.0/" version="3.0" xml:lang="en" unique-identifier="pub-identifier">
<metadata>
<dc:identifier id="pub-identifier">Z666.5.D57 2013</dc:identifier>
<meta id="meta-identifier" property="dcterms:identifier">Z666.5.D57 2013</meta>
<dc:title id="pub-title">The Discipline of Organizing</dc:title>
<meta property="dcterms:title" id="meta-title">The Discipline of Organizing</meta>
<dc:language id="pub-language">en</dc:language>
<meta property="dcterms:language" id="meta-language">en</meta>
<meta property="dcterms:modified">2013-02-20T15:09:16Z</meta>
<!--The preceding date value is actually local time (not UTC) in UTC format because there is no function in XSLT 1.0 to generate a correct UTC time-->
<meta property="dcterms:description">Abstract: We organize things, we organize information, we organize information about things, and we organize information about information. But even though “organizing” is a fundamental and ubiquitous challenge, when we compare these activities their contrasts are more apparent than their commonalities. We propose to unify many perspectives about organizing with the concept of an Organizing System, defined as an intentionally arranged collection of resources and the interactions they support. Every Organizing System involves a collection of resources, a choice of properties or principles used to describe and arrange resources, and ways of supporting interactions with resources. By comparing and contrasting how these activities take place in different contexts and domains, we can identify patterns of organizing. We can create a discipline of organizing in a disciplined way.</meta>
<dc:description>Abstract: We organize things, we organize information, we organize information about things, and we organize information about information. But even though “organizing” is a fundamental and ubiquitous challenge, when we compare these activities their contrasts are more apparent than their commonalities. We propose to unify many perspectives about organizing with the concept of an Organizing System, defined as an intentionally arranged collection of resources and the interactions they support. Every Organizing System involves a collection of resources, a choice of properties or principles used to describe and arrange resources, and ways of supporting interactions with resources. By comparing and contrasting how these activities take place in different contexts and domains, we can identify patterns of organizing. We can create a discipline of organizing in a disciplined way.</dc:description>
<meta property="dcterms:coverage">2013</meta>
<dc:coverage>2013</dc:coverage>
<meta property="dcterms:relation">http://www.docbook.org/xml/4.5/docbookx.dtd</meta>
<dc:relation>http://www.docbook.org/xml/4.5/docbookx.dtd</dc:relation>
<meta property="dcterms:source">http://www.disciplineoforganizing.org</meta>
<dc:source>http://www.disciplineoforganizing.org</dc:source>
<meta property="dcterms:contributor">RobertJ.Glushko</meta>
<dc:contributor>RobertJ.Glushko</dc:contributor>
<meta id="meta-creator1" property="dcterms:creator">Robert J. Glushko</meta>
<dc:creator id="pub-creator1">Robert J. Glushko, Jess Hemerly, Murray Maloney, Kimra McPherson, Vivien Petras, Ryan Shaw, and Erik Wilde</dc:creator>
<meta id="meta-creator2" property="dcterms:creator">Jess Hemerly</meta>
<meta id="meta-creator3" property="dcterms:creator">Murray Maloney</meta>
<meta id="meta-creator4" property="dcterms:creator">Kimra McPherson</meta>
<meta id="meta-creator5" property="dcterms:creator">Vivien Petras</meta>
<meta id="meta-creator6" property="dcterms:creator">Ryan Shaw</meta>
<meta id="meta-creator7" property="dcterms:creator">Erik Wilde</meta>
<meta id="meta-creator1" property="dcterms:creator">Rachelle Annechino</meta>
<dc:creator id="pub-creator1">Rachelle Annechino, J.J.M. Ekaterin, Ryan Greenberg, Michael Manoochehri, Sean Marimpietri, Matthew Mayernik, Karen Joy Nomorosa, Hyunwoo Park, Alberto Pepe, Daniel D. Turner, and Longhao Wang</dc:creator>
<meta id="meta-creator2" property="dcterms:creator">J.J.M. Ekaterin</meta>
<meta id="meta-creator3" property="dcterms:creator">Ryan Greenberg</meta>
<meta id="meta-creator4" property="dcterms:creator">Michael Manoochehri</meta>
<meta id="meta-creator5" property="dcterms:creator">Sean Marimpietri</meta>
<meta id="meta-creator6" property="dcterms:creator">Matthew Mayernik</meta>
<meta id="meta-creator7" property="dcterms:creator">Karen Joy Nomorosa</meta>
<meta id="meta-creator8" property="dcterms:creator">Hyunwoo Park</meta>
<meta id="meta-creator9" property="dcterms:creator">Alberto Pepe</meta>
<meta id="meta-creator10" property="dcterms:creator">Daniel D. Turner</meta>
<meta id="meta-creator11" property="dcterms:creator">Longhao Wang</meta>
<meta property="dcterms:contributor">Acquisitions EditorMarguerite B.Avery</meta>
<dc:contributor>Acquisitions EditorMarguerite B.Avery</dc:contributor>
<meta property="dcterms:contributor">Copy and Markup EditorMurray Maloney</meta>
<dc:contributor>Copy and Markup EditorMurray Maloney</dc:contributor>
<meta property="dcterms:contributor">Cover DesignJenWang</meta>
<dc:contributor>Cover DesignJenWang</dc:contributor>
<meta property="dcterms:contributor">Interior DesignNellieMcKesson</meta>
<dc:contributor>Interior DesignNellieMcKesson</dc:contributor>
<meta property="dcterms:contributor">IllustratorDivyaAnand</meta>
<dc:contributor>IllustratorDivyaAnand</dc:contributor>
<meta property="dcterms:contributor">AjeetaDhole</meta>
<dc:contributor>AjeetaDhole</dc:contributor>
<meta property="dcterms:contributor">ChristinaPham</meta>
<dc:contributor>ChristinaPham</dc:contributor>
<meta property="dcterms:contributor">RaymonSutedjo-The</meta>
<dc:contributor>RaymonSutedjo-The</dc:contributor>
<meta property="dcterms:contributor">Bibliography EditorLisa Jervis</meta>
<dc:contributor>Bibliography EditorLisa Jervis</dc:contributor>
<meta property="dcterms:contributor">Bibliography EditorShohei Narron</meta>
<dc:contributor>Bibliography EditorShohei Narron</dc:contributor>
<meta property="dcterms:contributor">Bibliography EditorAnne Wootton</meta>
<dc:contributor>Bibliography EditorAnne Wootton</dc:contributor>
<meta property="dcterms:contributor">Glossary and Index EditorMurray Maloney</meta>
<dc:contributor>Glossary and Index EditorMurray Maloney</dc:contributor>
<meta property="dcterms:contributor">CSS Print ConsultantAdamWitwer</meta>
<dc:contributor>CSS Print ConsultantAdamWitwer</dc:contributor>
<meta property="dcterms:contributor">DocBook ConsultantBob StaytonSagehill Enterprises</meta>
<dc:contributor>DocBook ConsultantBob StaytonSagehill Enterprises</dc:contributor>
<meta property="dcterms:date">2013</meta>
<dc:date>2013</dc:date>
<meta property="dcterms:rights">Copyright © 2013 Robert J. Glushko</meta>
<dc:rights>Copyright © 2013 Robert J. Glushko</dc:rights>
<meta property="dcterms:rightsHolder">Robert J. Glushko</meta>
<meta property="dcterms:publisher">The MIT Press</meta>
<dc:publisher>The MIT Press</dc:publisher>
<meta property="dcterms:date">2013-04-20</meta>
<dc:date>2013-04-20</dc:date>
<meta property="dcterms:subject">1. Information organization.</meta>
<dc:subject>1. Information organization.</dc:subject>
<meta property="dcterms:subject">2. Information resources management.</meta>
<dc:subject>2. Information resources management.</dc:subject>
<meta property="dcterms:subject">3. Metadata.</meta>
<dc:subject>3. Metadata.</dc:subject>
<meta property="dcterms:subject">I. Glushko, Robert J., editor of compilation.</meta>
<dc:subject>I. Glushko, Robert J., editor of compilation.</dc:subject>
<meta property="dcterms:subject">organizing</meta>
<dc:subject>organizing</dc:subject>
<meta property="dcterms:subject">information</meta>
<dc:subject>information</dc:subject>
<meta property="dcterms:subject">resources</meta>
<dc:subject>resources</dc:subject>
<meta property="dcterms:subject">metadata</meta>
<dc:subject>metadata</dc:subject>
<meta property="dcterms:subject">resource description</meta>
<dc:subject>resource description</dc:subject>
<meta name="cover" content="cover-image"/>
<meta property="ibooks:specified-fonts">true</meta>
</metadata>
<manifest>
<item id="ncx" href="toc.ncx" media-type="application/x-dtbncx+xml"/>
<item id="epub.embedded.font.1" href="DejaVuSerif.otf" media-type="application/vnd.ms-opentype"/>
<item id="epub.embedded.font.2" href="DejaVuSans-Bold.otf" media-type="application/vnd.ms-opentype"/>
<item id="epub.embedded.font.3" href="UbuntuMono-Regular.otf" media-type="application/vnd.ms-opentype"/>
<item id="epub.embedded.font.4" href="UbuntuMono-Bold.otf" media-type="application/vnd.ms-opentype"/>
<item id="epub.embedded.font.5" href="UbuntuMono-BoldItalic.otf" media-type="application/vnd.ms-opentype"/>
<item id="epub.embedded.font.6" href="UbuntuMono-Italic.otf" media-type="application/vnd.ms-opentype"/>
<item id="htmltoc" properties="nav" media-type="application/xhtml+xml" href="bk01-toc.html"/>
<item media-type="text/css" id="html-css" href="core.css"/>
<item id="cover" href="cover.html" media-type="application/xhtml+xml"/>
<item id="cover-image" properties="cover-image" href="images/cover.png.jpg" media-type="image/jpeg"/>
<item id="id375964" href="index.html" media-type="application/xhtml+xml"/>
<item id="id413474" href="dedication.html" media-type="application/xhtml+xml"/>
<item id="id580108" href="pr02.html" media-type="application/xhtml+xml"/>
<item id="id580314" href="pr03.html" media-type="application/xhtml+xml"/>
<item id="id580413" href="ch01.html" media-type="application/xhtml+xml"/>
<item id="id589909" href="ch02.html" media-type="application/xhtml+xml"/>
<item id="id600782" href="ch03.html" media-type="application/xhtml+xml"/>
<item id="id611321" href="ch04.html" media-type="application/xhtml+xml"/>
<item id="id621664" href="ch05.html" media-type="application/xhtml+xml"/>
<item id="id633972" href="ch06.html" media-type="application/xhtml+xml"/>
<item id="id640965" href="ch07.html" media-type="application/xhtml+xml"/>
<item id="id651381" href="ch08.html" media-type="application/xhtml+xml"/>
<item id="id661464" href="ch09.html" media-type="application/xhtml+xml"/>
<item id="id669786" href="ch10.html" media-type="application/xhtml+xml"/>
<item id="id674730" href="pr04.html" media-type="application/xhtml+xml"/>
<item id="id675864" href="bi01.html" media-type="application/xhtml+xml"/>
<item id="id676106" href="go01.html" media-type="application/xhtml+xml"/>
<item id="id719283" href="ix01.html" media-type="application/xhtml+xml"/>
<item id="id700216" href="co01.html" media-type="application/xhtml+xml"/>
<item id="id700217" href="copyright.html" media-type="application/xhtml+xml"/>
<item id="id710840" href="figs/print/ch1.1-350dpi.png" media-type="image/png"/>
<item id="id1246987" href="figs/print/ucb-tdo-chapter1.3.2-color.png" media-type="image/png"/>
<item id="id1231479" href="figs/print/ch2.1-350dpi.jpg" media-type="image/jpeg"/>
<item id="id1229325" href="figs/print/ch3.1-350dpi.png" media-type="image/png"/>
<item id="id1255197" href="figs/print/Figure3-2-Replacement.png" media-type="image/png"/>
<item id="id1247062" href="figs/print/chapter-3-figure-3.2.2.png.jpg" media-type="image/jpeg"/>
<item id="id1259042" href="figs/print/ch3.4-350dpi.png" media-type="image/png"/>
<item id="id1254485" href="figs/print/ucb-tdo-chapter3.3.2-color.png" media-type="image/png"/>
<item id="id1130515" href="figs/print/ch3.6-350dpi.png" media-type="image/png"/>
<item id="id1233419" href="figs/print/Chapter4-4.2.2.4.png" media-type="image/png"/>
<item id="id1265976" href="figs/print/ch4.2-350dpi.png" media-type="image/png"/>
<item id="id1245466" href="figs/print/ch4.3-350dpi.png" media-type="image/png"/>
<item id="id1211022" href="figs/print/ch4.4-350dpi.png" media-type="image/png"/>
<item id="id1230373" href="figs/print/ch4.5-350dpi.png.jpg" media-type="image/jpeg"/>
<item id="id1231898" href="figs/print/ch5.1-350dpi.png" media-type="image/png"/>
<item id="id1265720" href="figs/print/ucb-tdo-chapter5.3.3-ontology-color.png" media-type="image/png"/>
<item id="id1249558" href="figs/print/ch5.3-350dpi.png" media-type="image/png"/>
<item id="id1247144" href="figs/print/ucb-tdo-chapter7.2.1.2-color.png" media-type="image/png"/>
<item id="id1247145" href="figs/print/ucb-tdo-chapter7.4.1a-color.png" media-type="image/png"/>
<item id="id1211113" href="figs/print/ucb-tdo-chapter7.4.1b-color.png" media-type="image/png"/>
<item id="id1229994" href="figs/print/ucb-tdo-chapter7.4.1c-color.png" media-type="image/png"/>
<item id="id1265977" href="figs/print/ch7.7-350dpi.png" media-type="image/png"/>
<item id="id1131476" href="figs/print/ch8.1-350dpi.png" media-type="image/png"/>
<item id="id1232457" href="figs/print/ch8.2-350dpi.png" media-type="image/png"/>
<item id="id1249037" href="figs/print/ch8.3-350dpi.png" media-type="image/png"/>
<item id="id1249022" href="figs/print/ch8.4-350dpi.png" media-type="image/png"/>
<item id="id1047043" href="figs/print/ch8.5-350dpi.png" media-type="image/png"/>
<item id="id1250477" href="figs/print/ch8.6-350dpi.png" media-type="image/png"/>
<item id="id1232104" href="figs/print/ch8.7-350dpi.png" media-type="image/png"/>
<item id="id1250476" href="figs/print/ch9-1.png" media-type="image/png"/>
</manifest>
<spine toc="ncx">
<itemref idref="cover" linear="yes"/>
<itemref idref="id375964"/>
<itemref idref="id413474"/>
<itemref idref="id580108"/>
<itemref idref="id580314"/>
<itemref idref="id580413"/>
<itemref idref="id589909"/>
<itemref idref="id600782"/>
<itemref idref="id611321"/>
<itemref idref="id621664"/>
<itemref idref="id633972"/>
<itemref idref="id640965"/>
<itemref idref="id651381"/>
<itemref idref="id661464"/>
<itemref idref="id669786"/>
<itemref idref="id674730"/>
<itemref idref="id675864"/>
<itemref idref="id676106"/>
<itemref idref="id719283"/>
<itemref idref="id700216"/>
<itemref idref="id700217"/>
</spine>
<guide>
<reference href="cover.html" type="cover" title="Cover"/>
<reference href="bk01-toc.html" type="toc" title="Table of Contents"/>
<reference href="index.html" type="text"/>
</guide>
</package>

14
TDO/OEBPS/copyright.html Normal file
View file

@ -0,0 +1,14 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title/><link rel="stylesheet" type="text/css" href="core.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"/><meta name="keywords" content="organizing, information, resources, metadata, resource description"/><link rel="up" href="index.html" title="The Discipline of Organizing"/><link rel="prev" href="co01.html" title="Colophon"/></head><body><div class="colophon" epub:type="colophon" id="copyright_page_orm"><h2 class="title"/><div><h1 class="title">The Discipline of Organizing</h1></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Robert</span> <span class="othername">J.</span> <span class="surname">Glushko</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Jess</span> <span class="surname">Hemerly</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Murray</span> <span class="surname">Maloney</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Kimra</span> <span class="surname">McPherson</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Vivien</span> <span class="surname">Petras</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Ryan</span> <span class="surname">Shaw</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Erik</span> <span class="surname">Wilde</span></h3></div></div></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Rachelle</span> <span class="surname">Annechino</span></h3></div><div class="author"><h3 class="author"><span class="firstname">J.J.M.</span> <span class="surname">Ekaterin</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Ryan</span> <span class="surname">Greenberg</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Michael</span> <span class="surname">Manoochehri</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Sean</span> <span class="surname">Marimpietri</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Matthew</span> <span class="surname">Mayernik</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Karen</span> <span class="othername">Joy</span> <span class="surname">Nomorosa</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Hyunwoo</span> <span class="surname">Park</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Alberto</span> <span class="surname">Pepe</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Daniel</span> <span class="othername">D.</span> <span class="surname">Turner</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Longhao</span> <span class="surname">Wang</span></h3></div></div></div><div class="editor"><h4>Editor</h4><h3 class="editor"><span class="firstname">Robert</span> <span class="othername">J.</span> <span class="surname">Glushko</span></h3></div><div><div class="revhistory"><table style="border: 1; width: 100%; "><tr><td style="text-align: left; vertical-align: top; " colspan="2"><strong>Revision History</strong></td></tr><tr class="revision"><td class="revdate">April 2013</td><td class="revremark">First release</td></tr></table></div></div><div><p class="copyright">Copyright © 2013 Robert J. Glushko</p></div><div><div class="legalnotice" title="Legal Notice"><a id="id414659"/><div class="literallayout"><p>Library of Congress Cataloging-in-Publication Data<br/>
<br/>
The discipline of organizing / edited by Robert J. Glushko.<br/>
 p. cm<br/>
Includes bibliographical references, glossary and index.<br/>
<span>ISBN 978-0-262-51850-5 (hardcover : alk. paper)</span><br/>
<span>ISBN 978-0-262-25793-0 (retail ebook)</span><br/>
1. Information organization. 2. Information resources management. 3. Metadata. <br/>
I. Glushko, Robert J., editor of compilation.<br/>
Z666.5.D57 2013<br/>
025—dc23                                                                                     2012038046<br/>
        <br/>
        </p></div><p>10 9 8 7 6 5 4 3 2 1</p></div></div><div><div class="legalnotice" title="Legal Notice"><a id="id579774"/><p/></div></div><div class="publisher"><span class="publishername">The MIT Press<br/></span><div class="address"><p><span class="street">55 Hayward Street</span></p><p><span class="city">Cambridge</span>, <span class="state">Massachusetts</span> </p><p><span class="country">U.S.A</span></p></div></div><div class="timestamp"><p>2013-02-20T15:09:16Z</p></div><p/></div></body></html>

1120
TDO/OEBPS/core.css Normal file

File diff suppressed because it is too large Load diff

2
TDO/OEBPS/cover.html Normal file
View file

@ -0,0 +1,2 @@
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<html xmlns="http://www.w3.org/1999/xhtml"><head><title>Cover</title><style type="text/css"> img { max-width: 100%; }</style></head><body><div id="cover-image"><img src="images/cover.png.jpg" alt="Abstract"/></div></body></html>

36
TDO/OEBPS/dedication.html Normal file
View file

@ -0,0 +1,36 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>Dedication</title><link rel="stylesheet" type="text/css" href="core.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"/><meta name="keywords" content="organizing, information, resources, metadata, resource description"/><link rel="up" href="index.html" title="The Discipline of Organizing"/><link rel="prev" href="index.html" title="The Discipline of Organizing"/><link rel="next" href="pr02.html" title="Foreword"/></head><body><section class="preface" title="Dedication" epub:type="preface" id="id413474"><div class="titlepage"><div><div><h2 class="title">Dedication</h2></div></div></div><p>
<a id="id579854" class="indexterm"/>
<a id="id579864" class="indexterm"/>
<a id="id579870" class="indexterm"/>
<a id="id579876" class="indexterm"/>
<a id="id579883" class="indexterm"/>
</p><p>To Aristotle, Plato, Linnaeus, Condorcet, Wittgenstein...</p><p>
<a id="id579894" class="indexterm"/>
<a id="id579902" class="indexterm"/>
<a id="id579908" class="indexterm"/>
<a id="id579915" class="indexterm"/>
</p><p>Panizzi, Cutter, Ragananthan, Svenonius... </p><p>
<a id="id579928" class="indexterm"/>
<a id="id579934" class="indexterm"/>
<a id="id579940" class="indexterm"/>
<a id="id579947" class="indexterm"/>
</p><p>Gibson, Norman, Rosch, Barsalou... </p><p>
<a id="id579960" class="indexterm"/>
<a id="id579966" class="indexterm"/>
<a id="id579972" class="indexterm"/>
</p><p>Adam Smith, Coase, Williamson... </p><p>
<a id="id579985" class="indexterm"/>
<a id="id579992" class="indexterm"/>
<a id="id579998" class="indexterm"/>
<a id="id580004" class="indexterm"/>
</p><p>Simon, Salton, Miller, Dumais...</p><p>
<a id="id580017" class="indexterm"/>
<a id="id580024" class="indexterm"/>
<a id="id580030" class="indexterm"/>
<a id="id580036" class="indexterm"/>
</p><p>Bush, Engelbart, Nelson, Berners-Lee... </p><p>
<a id="id580049" class="indexterm"/>
</p><p>...and the countless others whose diverse perspectives</p><p>
<a id="id580065" class="indexterm"/>
</p><p>we have synthesized in the discipline of organizing.</p></section></body></html>

Binary file not shown.

After

Width:  |  Height:  |  Size: 87 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 72 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 59 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 116 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 143 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 93 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 28 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 31 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 142 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 80 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 32 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 31 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 70 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 49 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 42 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 63 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 64 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 64 KiB

BIN
TDO/OEBPS/figs/print/ch9-1.png Executable file

Binary file not shown.

After

Width:  |  Height:  |  Size: 163 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 55 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 213 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 177 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 169 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 229 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 91 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 95 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 69 KiB

1171
TDO/OEBPS/go01.html Normal file

File diff suppressed because it is too large Load diff

Binary file not shown.

After

Width:  |  Height:  |  Size: 49 KiB

2
TDO/OEBPS/index.html Normal file
View file

@ -0,0 +1,2 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>The Discipline of Organizing</title><link rel="stylesheet" type="text/css" href="core.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"/><meta name="description" content="Abstract We organize things, we organize information, we organize information about things, and we organize information about information. But even though “organizing” is a fundamental and ubiquitous challenge, when we compare these activities their contrasts are more apparent than their commonalities. We propose to unify many perspectives about organizing with the concept of an Organizing System, defined as an intentionally arranged collection of resources and the interactions they support. Every Organizing System involves a collection of resources, a choice of properties or principles used to describe and arrange resources, and ways of supporting interactions with resources. By comparing and contrasting how these activities take place in different contexts and domains, we can identify patterns of organizing. We can create a discipline of organizing in a disciplined way."/><meta name="keywords" content="organizing, information, resources, metadata, resource description"/><link rel="next" href="dedication.html" title="Dedication"/></head><body><div class="book" title="The Discipline of Organizing" id="id375964"><div class="titlepage"><div><div><h1 class="title">The Discipline of Organizing</h1></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Robert</span> <span class="othername">J.</span> <span class="surname">Glushko</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Jess</span> <span class="surname">Hemerly</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Murray</span> <span class="surname">Maloney</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Kimra</span> <span class="surname">McPherson</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Vivien</span> <span class="surname">Petras</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Ryan</span> <span class="surname">Shaw</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Erik</span> <span class="surname">Wilde</span></h3></div></div></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Rachelle</span> <span class="surname">Annechino</span></h3></div><div class="author"><h3 class="author"><span class="firstname">J.J.M.</span> <span class="surname">Ekaterin</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Ryan</span> <span class="surname">Greenberg</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Michael</span> <span class="surname">Manoochehri</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Sean</span> <span class="surname">Marimpietri</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Matthew</span> <span class="surname">Mayernik</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Karen</span> <span class="othername">Joy</span> <span class="surname">Nomorosa</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Hyunwoo</span> <span class="surname">Park</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Alberto</span> <span class="surname">Pepe</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Daniel</span> <span class="othername">D.</span> <span class="surname">Turner</span></h3></div><div class="author"><h3 class="author"><span class="firstname">Longhao</span> <span class="surname">Wang</span></h3></div></div></div><div class="publishername">Published by <span class="publishername">The MIT Press<br/></span></div></div></div></div></body></html>

29
TDO/OEBPS/ix01.html Normal file

File diff suppressed because one or more lines are too long

114
TDO/OEBPS/pr02.html Normal file
View file

@ -0,0 +1,114 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>Foreword</title><link rel="stylesheet" type="text/css" href="core.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"/><meta name="keywords" content="organizing, information, resources, metadata, resource description"/><link rel="up" href="index.html" title="The Discipline of Organizing"/><link rel="prev" href="dedication.html" title="Dedication"/><link rel="next" href="pr03.html" title="Preface"/></head><body><section class="preface" title="Foreword" epub:type="preface" id="Foreword"><div class="titlepage"><div><div><h2 class="title">Foreword</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Jonathan</span> <span class="surname">Grudin</span></h3></div></div></div></div></div><p>This wonderful book arrives at the right time. It is more than a textbook<span class="symbol"></span>it defines and
creates the field for which it is a text. Befitting a book that lays out a discipline of
organization that spans print and digital media, this volume is carefully organized, with a
focus on future print and digital editions.</p><p><em class="citetitle">The Discipline of Organizing</em> has a broad scope. Even more valuable
is its depth, the result of years of examining and thinking through related concepts<span class="symbol"></span>often
overlapping but not identical<span class="symbol"></span>from the fields of library science, information science,
business, and computer science. The rare combination of breadth and depth empowers readers
by providing a new perspective and framework for organizing subsequent experiences. The
organization is comprehensive and systematic, but it is not simple. A lot of concepts must
be assimilated. Yet thanks to the authors thoroughness, you can proceed confident that
investing the time to master novel concepts will pay off, that a coherent structure is being
assembled, without inconsistencies or confusions. Into this framework you can fit your own
examples, alongside the many provided by the authors. You can identify extensions and form
new associations, building on a strong foundation.</p><p>The authors ask us to step back and adopt a general, multidisciplinary perspective. This
is unusual for a textbook. For good reason, the world is marked by increasing
specialization, the division of labor on which complex civilization depends. First we master
a discipline; then we are encouraged to be multidisciplinary, interdisciplinary, and
transdisciplinary<span class="symbol"></span>to balance our specialized pursuits. But scholars thrive within single
disciplines, and even in fields created as multidisciplinary efforts, such as the
neurosciences or cognitive science, most researchers soon become highly specialized. So why
should a student of information undertake to master this broad perspective?</p><p>By growing from insignificance to centrality in the century-old field of information
management in a few decades, digital technology has forced a disciplinary merger. Library
science, information science, computer science or informatics, and information systems have
developed different terminologies and sets of abstractions. Rather than asking each camp to
learn the others languages, the authors ask each of us to engage with a new terminology and
set of abstractions.</p><p>The analogy of the artificial language Esperanto may come to mind, but we are in a better
position. Esperanto is only useful if you are in a community of Esperantists. The
abstractions in this book will be useful if others share them, but any reader will benefit
by understanding the correspondences across the approaches to information organization that
we encounter today. Unlike Esperanto, which is just another language, the concepts in this
book reveal linkages and dependencies that we would not otherwise appreciate. The book
provides a deep foundation for understanding changes that affect our lives and will do so
more in the years ahead, a foundation that you will carry even if much of the time you
converse in the language of one or another professional tribe.</p><p>Why do I say the timing is perfect, that this effort is worthwhile today? Havent people
gotten by without it until now? The answer has two parts. One, which is important even if
you have heard it before, is that this is a time of extraordinary change in our uses of
information. The other is that people have not always <span class="quote"><span class="quote">gotten by</span></span> very well; years have been
wasted and careers damaged by not understanding the principles in this book. The likelihood
of such wreckage is growing, as the waves of change are larger and come at us faster. On the
positive side, the waves offer tremendous opportunity for accomplishment. The coming era of
monster waves may be risky if we surf with a narrow focus, but thrilling for those whose
view extends up and down the shoreline. I believe that if you read this book, you will see
this point and be glad you read it. Let me know.</p><p><a id="id580278" class="indexterm"/>We are used to hearing about <span>Moores law</span> and related legislation, but familiarity lowers
our guard.  Human beings do not reason well about exponential growth, our experience is
linear, not exponential. What we overlook is that exponential growth can proceed for a long
time under the radar<span class="symbol"></span>one grain of rice, two grains, four grains, etc., not adding up to
much, but when it reaches the point of having an impact, the impact comes so fast that we
are unprepared for it. Decades passed before accessible digital technology could support
high-quality photography, but when the time came, film photography disappeared so quickly
that most major companies went bankrupt. Digital audio and video were a long time coming,
then panicked and shuttered major industries. The expanding capacity and diminishing cost of
information storage alter the balances described in this book. Bandwidth, increasing more
slowly, is also reaching disruptive levels. This book provides the best tools available for
understanding the disruptions of today and tomorrow in information management.</p><p>This perspective is invaluable now. It would have been useful earlier, but it was not
considered imperative for the disciplines of library science, information science,
informatics, and information systems. Historically they prospered despite interacting less
than one might have expected. Library and information science, rooted in the humanities,
focused technology efforts primarily on administrators and specialized users. Delivering
services to the public was secondary. In contrast, academic computer science and
human-computer interaction focused on widespread applications.</p><p>This book consciously connects fields that have focused on aspects of information
organization and management such as archiving, records management, and curation, to
information retrieval and related aspects of informatics. It explores how related issues
play out in different contexts. The authors are admirably positive. They do not drag us
through the myriad disasters that resulted when library and information science did not
understand the potential contributions of digital technology and the equally unfortunate
disasters that resulted when technologists ignored a century of work on information
organization.</p><p>However, I will sound a cautionary note about what might go wrong if you do not understand
the principles laid out in this book. First, for computer scientists and engineers: Major
system-building efforts foundered due to a lack of insight into the principles of
information organization. I will describe an early one, whose protagonists, good or bad,
right or wrong, are all equal now.</p><p>Although not a computer scientist or computer engineer,
<span class="personname"><span class="firstname">Vannevar</span> <span class="surname">Bush</span></span> had as much
influence on the field as anyone through his work on shaping government support for research
after the Second World War and through his 1945 <span class="italic">The Atlantic</span>
essay “<span class="citetitle">As We May Think</span>”.
Discussed in <a class="xref" href="ch02.html" title="Chapter 2. Activities in Organizing Systems">Chapter 2</a>, this essay describes a hypothetical machine
called the Memex that would enable information retrieval through a complex <span class="quote"><span class="quote">associative
memory</span></span> that supports links much like those found in the World Wide Web today. Although
Bushs design was based on microfilm and optical scanning rather than silicon, his vision
has inspired countless researchers to this day.</p><p>Less well known are Bushs classified efforts from the 1930s through early 1950s to build
machines for the military and information agencies with Memex capabilities. Meticulously
detailed by historian Colin Burke in the book <em class="citetitle">Information and
Secrecy: Vannevar Bush, Ultra, and the other Memex</em>, these projects consumed
massive funding, occupied many brilliant MIT scientists for years, and produced nothing
useful. A working machine was finally produced, but Bush never consulted with library
science scholars who understood information organization from decades of work and made naïve
assumptions about how information could be organized for retrieval<span class="symbol"></span>the extraordinarily
expensive machine was not usable in the real world.</p><p>Computer scientists interested in information should adopt a broad perspective, and this
book is a place to begin. Several fields of computer science garner attention today, such as
machine learning, data mining, information visualization, and design. Those centered on
information, which is most directly affected by Moores law, are likely to have the greatest
impact. </p><p>The library and information science side of the bridge also have seen disarray and
disaster. Pride in a century of disciplinary development led to inertia. Once exponential
silicon-based change could not be avoided, there was not enough time to react. Major library
schools closed. Today there are schools of information and a range of <span class="quote"><span class="quote">library and
information science</span></span> schools, some more forward-looking than others. Curriculum change has
been relatively ad hoc, shaped by local personnel and context. Consider Information to be a
large new volcanic cone pushing up in the midst of other peaks. No consistent approach has
emerged to navigate the range. This book provides bridges where before there were slippery
trails.</p><p>What can you do by virtue of reading and studying this book? Most importantly, perhaps,
you can avoid confusion<span class="symbol"></span>when reading something or talking with someone from a different
discipline, when asked a question in a job interview or by a colleague with a different
background. Knowing that differences in terminology and abstractions are possible, you can
ask questions and home quickly in on understanding. I have written elsewhere that through my
career, such confusions frequently arose when I interacted with people in diverse
disciplines, such as management information systems, software engineering, human factors,
and so on. Because there was no book like this to clarify, it took me years to comprehend
the source of many communication problems.</p><p>Beyond that, this book provides a foundation and framework for organizing and thinking
about your experiences. This is a textbook, pointing to areas for research, providing ways
of looking at new developments, and revealing to the perceptive reader yet unexplored
territory in the spaces between disciplines.
This is a book to read and put on the bookshelf<span class="symbol"></span>or
in a folder in your digital reader<span class="symbol"></span>to reread in a few years time.</p><p><span class="personname"><span class="firstname">Jonathan</span> <span class="surname">Grudin</span></span>, 17 December 2012</p></section></body></html>

11
TDO/OEBPS/pr03.html Normal file
View file

@ -0,0 +1,11 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>Preface</title><link rel="stylesheet" type="text/css" href="core.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"/><meta name="keywords" content="organizing, information, resources, metadata, resource description"/><link rel="up" href="index.html" title="The Discipline of Organizing"/><link rel="prev" href="pr02.html" title="Foreword"/><link rel="next" href="ch01.html" title="Chapter 1. Foundations for Organizing Systems"/></head><body><section class="preface" title="Preface" epub:type="preface" id="Preface"><div class="titlepage"><div><div><h2 class="title">Preface</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Robert</span> <span class="othername">J.</span> <span class="surname">Glushko</span></h3></div></div></div></div></div><p>In our daily lives organizing is a common personal and group activity that we often do without thinking much about it. Organizing is also a fundamental issue in library and information science, computer science, systems analysis, informatics, law, economics, and business. But even though researchers and practitioners in these disciplines think about organizing all the time, they have only limited agreement in how they approach problems of organizing and in what they seek as their solutions.</p><p>This book analyzes these different contexts and disciplines to propose a discipline of organizing that applies to all of them. Whether you are organizing physical resources like printed books or museum paintings, or digital resources like web pages, MP3s, or computational services implemented in software, you are creating an <span class="bold"><strong>Organizing System<span class="symbol"></span>an intentionally arranged collection of resources and the interactions they support.</strong></span></p><p>
The transdisciplinary concept of Organizing System lets us see that resource selection, organizing, interaction design, and maintenance take place in every one of them. We can also identify many design principles and methods that apply broadly when we describe resources, create resource categories, and classify resources by assigning them to categories. A vocabulary for discussing common organizing challenges and issues that might be otherwise obscured by narrow disciplinary perspectives helps us understand existing organizing systems better while also suggesting how to invent new ones by making different design choices.
</p><h2><a id="id580472"/>Motivation</h2><p>This book began as the lecture notes from a graduate course on <span class="italic">Information Organization and Retrieval</span> I have taught since 2005 at the University of California, Berkeley. My goal was to teach these traditionally distinct subjects in a more integrated way. The former is the focus of library and information science, while the latter is core to computer science and informatics, and their conventional textbooks and topics are widely divergent. But while these academic disciplines are divided, in the “real world” information organization and retrieval are increasingly intermixed and converging.</p><p>
With the World Wide Web and ubiquitous digital information, along with effectively unlimited processing, storage and communication capability driven by Moores Law, millions of people create and browse websites, blog, tag, tweet, and upload and download content of all media types without thinking “Im organizing now” or “Im retrieving now.” When people use their smart phones to search the web or run applications, location information transmitted from their phone is used to filter and reorganize the information they retrieve. Arranging results to make them fit the users location is a kind of computational curation, but because it takes place quickly and automatically we hardly notice it. Likewise, almost every application that once seemed predominantly about information retrieval is now increasingly combined with activities and functions that most would consider to be information organization. </p><p>We needed a book that could bridge<span class="symbol"></span>or better yet, synthesize<span class="symbol"></span>the two disciplines of library science and computer science. We believe that their intellectual intersection is the study of organizing, and in particular, the analysis and design of Organizing Systems.</p><h2><a id="id580460"/>Collaboration</h2><p>A book motivated by the prospect of multidisciplinary synthesis implies a multidisciplinary collaboration to create it. The principal authors of this book are mostly professors or former professors at different universities whose backgrounds include computer science and software engineering, library science, digital humanities, and cognitive science. Many of the other authors are former graduate students currently working in major web firms, web start-ups, consulting organizations, academic and government research labs, and law firms. This diverse set of authors with different backgrounds and aspirations gives this book a broad and contemporary perspective that would be impossible for a single author to achieve.</p><h2><a id="id580562"/>Customization</h2><p>Multidisciplinary collaboration poses its own challenge. A book that brings together multiple disciplines contains many specialized topics and domain-specific examples that might overwhelm the shared concepts. Our solution is to write a “lean” core text and to move disciplinary and domain-specific content into “tagged” endnotes. This allows the book to emphasize the concepts that bridge the different organizing disciplines while enabling it to satisfy the additional topical needs of different academic programs. There are six types of endnotes, listed here in order of their frequency in the text:</p><div class="itemizedlist"><ul class="itemizedlist"><li class="listitem"><p><span class="italic">Citation</span> <span class="symbol"></span> additional detail not tied to a particular discipline.</p></li><li class="listitem"><p><span class="italic">LIS</span> <span class="symbol"></span> Library and Information Science; these arent the same, but this is a conventional disciplinary category.</p></li><li class="listitem"><p><span class="italic">Computing</span> <span class="symbol"></span> includes Computer Science, Software Engineering, and Web Architecture.</p></li><li class="listitem"><p><span class="italic">CogSci</span> <span class="symbol"></span> Cognitive Science, which includes Cognitive Psychology, Linguistics, and Philosophy.</p></li><li class="listitem"><p><span class="italic">Law.</span></p></li><li class="listitem"><p><span class="italic">Business.</span></p></li></ul></div><p>In the print version of this book readers can customize their experience by turning to
the endnotes section of each chapter. In the initial ebook versions, readers can follow
hypertext links to the associated endnotes. </p><h2><a id="id580533"/>ebooks</h2><p>We have thought since the beginning of this project that this book should not just be a conventional printed text. A printed book is an intellectual snapshot that is already dated in many respects the day it is published. In addition, the pedagogical goal of this book is made more difficult by the relentless pace of technology innovation in our information-intensive economy and culture. </p><p>The emergence of ebook publishing opens up innovative possibilities for this book. We are already working on a next-generation ebook application that can create a vastly more engaging and integrated reader experience with the tagged endnotes. Instead of requiring the reader to follow a hypertext link, our ebook application will present selectable icons that dynamically transclude the endnote text into the core text. Furthermore, we are making the set of endnote types completely extensible. In addition to the six types that occur in the book as first published, any instructor or institution will be able to create other endnote types to meet new requirements for customization.
</p><h2><a id="id580646"/>DisciplineOfOrganizing.org Website</h2><p>These additional endnotes will join a living repository of resources to enhance the use of the book among the instructors and students using it in university courses. “A living repository for collaboration” is not just a cliché here. We have been experimenting with this idea for over a year with a companion website, <a class="ulink" href="http://DisciplineOfOrganizing.org" target="_top"><code class="uri">http://DisciplineOfOrganizing.org</code></a>. </p><p>
The multi-disciplinary multi-campus collaboration needed to create this book has grown broader over time to include discussion and sharing of lecture notes, course assignments, and exam questions. In addition, student created-content such as course-related blog posts and commentary has also been shared between schools using the book. The site also contains a blog by the books authors and instructors. New versions of ebooks will be distributed through the site as they become available.
</p><p><span class="personname"><span class="firstname">Robert</span> <span class="othername">J.</span> <span class="surname">Glushko</span></span>, 31 December 2012</p></section></body></html>

194
TDO/OEBPS/pr04.html Normal file
View file

@ -0,0 +1,194 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xmlns:m="http://www.w3.org/1998/Math/MathML" xmlns:pls="http://www.w3.org/2005/01/pronunciation-lexicon" xmlns:ssml="http://www.w3.org/2001/10/synthesis" xmlns:svg="http://www.w3.org/2000/svg"><head><title>Acknowledgments</title><link rel="stylesheet" type="text/css" href="core.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"/><meta name="keywords" content="organizing, information, resources, metadata, resource description"/><link rel="up" href="index.html" title="The Discipline of Organizing"/><link rel="prev" href="ch10.html" title="Chapter 10. The Organizing System Roadmap"/><link rel="next" href="bi01.html" title="Bibliography"/></head><body><section class="preface" title="Acknowledgments" epub:type="preface" id="Acknowledgements"><div class="titlepage"><div><div><h2 class="title">Acknowledgments</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Robert</span> <span class="othername">J.</span> <span class="surname">Glushko</span></h3></div></div></div></div></div><p>Philosophers, scientists, designers, and many others have sought to make sense of how we
organize our physical and intellectual worlds for over two thousand years. We owe a great
general obligation to all of them, so we dedicated this book to them. However, it is more
important to acknowledge more specifically the people who made this <em class="citetitle">Discipline of Organizing</em>
book happen. I think it is befitting of a book about organizing to be organized in making
these acknowledgments, as follows in three categories:</p><h2><a id="id674845"/>The Motivators</h2><p><span class="personname"><span class="firstname">Annalee</span> <span class="surname">Saxenian</span></span>,
the Dean of the <span class="orgname">UC Berkeley School of Information</span>, challenged me in 2005
to teach the “Information Organization and Retrieval” course required of all entering
graduate students and provided me with a supportive environment in which to do it. The lecture notes
of my predecessors, Berkeley colleagues <span class="personname"><span class="firstname">Marti</span> <span class="surname">Hearst</span></span>,
<span class="personname"><span class="firstname">Ray</span> <span class="surname">Larson</span></span>, and
<span class="personname"><span class="firstname">Mark</span> <span class="surname">Davis</span></span>, provided
important intellectual scaffolding as I developed my own syllabus and lectures.</p><p>When I discovered the little red book by
<span class="personname"><span class="firstname">Elaine</span> <span class="surname">Svenonius</span></span>,
<em class="citetitle">The Intellectual Foundation of Information Organization</em>,
my mind opened up to library and information science. I
aspired to write a book that could build on and broaden those foundations to connect with my
own background in cognitive and computer science. A few months later when I met Elaine I was very pleased when she endorsed this ambitious effort.</p><p>I have been continually encouraged by faculty members and deans whenever I talked about
this project at Schools of Information or similar academic units. These include the U.S.
universities of Indiana, Kentucky, Michigan, and North Carolina, Canadian universities
of Toronto and Western Ontario, and European universities in Vienna and Berlin. In
particular, I would like to thank
<span class="personname"><span class="firstname">Colin</span> <span class="surname">Allen</span></span>,
<span class="personname"><span class="firstname">Ron</span> <span class="surname">Day</span></span>,
<span class="personname"><span class="firstname">Miles</span> <span class="surname">Efron</span></span>,
<span class="personname"><span class="firstname">Thomas</span> <span class="surname">Finholt</span></span>,
<span class="personname"><span class="firstname">Dan</span> <span class="surname">OHair</span></span>,
<span class="personname"><span class="firstname">Margaret</span> <span class="surname">Hedstrom</span></span>,
<span class="personname"><span class="firstname">Michael</span> <span class="surname">Jones</span></span>,
<span class="personname"><span class="firstname">John</span> <span class="surname">King</span></span>,
<span class="personname"><span class="firstname">Kathryn</span> <span class="surname">LaBarre</span></span>,
<span class="personname"><span class="firstname">Kelly</span> <span class="surname">Lyons</span></span>,
<span class="personname"><span class="firstname">Gary</span> <span class="surname">Marchionini</span></span>,
<span class="personname"><span class="firstname">Jerry</span> <span class="surname">McDonough</span></span>,
<span class="personname"><span class="firstname">Allen</span> <span class="surname">Renear</span></span>,
<span class="personname"><span class="firstname">Seamus</span> <span class="surname">Ross</span></span>,
<span class="personname"><span class="firstname">Victoria</span> <span class="surname">Rubin</span></span>,
<span class="personname"><span class="firstname">Michael</span> <span class="surname">Seadle</span></span>, and
<span class="personname"><span class="firstname">Linda</span> <span class="surname">Smith</span></span>.
I especially appreciate the encouragement that Deans Marchionini and Seadle
gave to
<span class="personname"><span class="firstname">Ryan</span> <span class="surname">Shaw</span></span> and
<span class="personname"><span class="firstname">Vivien</span> <span class="surname">Petras</span></span>,
two of the principal authors of this book. I apologize
to those of you that Ive forgotten to list here.</p><p><span class="personname"><span class="firstname">Margy</span> <span class="surname">Avery</span></span>
of <span class="orgname">The MIT Press</span> has pushed hard when she needed to and has been very receptive
when I needed her to be.</p><h2><a id="id675084"/>The Contributors</h2><p>It took me four years of teaching the IO &amp; IR course at Berkeley before I knew enough
(or too little) to think I could put together a book that might replace the diverse set of
textbooks that course was using. I did not realize at the time how much I was learning from
these teaching assistants, and I thank them for not making it obvious to me. Later on, after
the book project was underway, my teaching assistants were invaluable in pointing out
problems with the book, often proposing their solutions as well.</p><p>Almost exactly three years ago the project to write this book began in a graduate seminar
whose goals were to define the topical coverage and structure of the book, and then to write
chapters starting with my course lecture notes. Among the courageous students in that
seminar were many authors of the book being published here:
<span class="personname"><span class="firstname">Rachelle</span> <span class="surname">Annechino</span></span>,
<span class="personname"><span class="firstname">J.J.M.</span> <span class="surname">Ekaterin</span></span>,
<span class="personname"><span class="firstname">Ryan</span> <span class="surname">Greenberg</span></span>,
<span class="personname"><span class="firstname">Jess</span> <span class="surname">Hemerly</span></span>,
<span class="personname"><span class="firstname">Michael</span> <span class="surname">Manoochehri</span></span>,
<span class="personname"><span class="firstname">Sean</span> <span class="surname">Marimpietri</span></span>,
<span class="personname"><span class="firstname">Kimra</span> <span class="surname">McPherson</span></span>,
<span class="personname"><span class="firstname">Karen</span> <span class="surname">Nomorosa</span></span>,
<span class="personname"><span class="firstname">Hyunwoo</span> <span class="surname">Park</span></span>,
<span class="personname"><span class="firstname">Dan</span> <span class="surname">Turner</span></span>, and
<span class="personname"><span class="firstname">Longhao</span> <span class="surname">Wang</span></span>.
<span class="personname"><span class="firstname">Nick</span> <span class="surname">Doty</span></span>,
<span class="personname"><span class="firstname">Mohit</span> <span class="surname">Gupta</span></span>,
<span class="personname"><span class="firstname">Erin</span> <span class="surname">Knight</span></span>, and
<span class="personname"><span class="firstname">Joyce</span> <span class="surname">Tsai</span></span>
also contributed during this start-up period.</p><p>In Spring 2011
<span class="personname"><span class="firstname">Erik</span> <span class="surname">Wilde</span></span> and I conducted a seminar titled “Principles and Patterns of
Organizing Systems” to refine the key concepts of the evolving book. This seminar added
<span class="personname"><span class="firstname">Brendan</span> <span class="surname">Curran</span></span>,
<span class="personname"><span class="firstname">Krishna</span> <span class="surname">Janakiraman</span></span>,
<span class="personname"><span class="firstname">Julian</span> <span class="surname">Limon</span></span>,
<span class="personname"><span class="firstname">Rowyn</span> <span class="surname">McDonald</span></span>,
<span class="personname"><span class="firstname">Elisa</span> <span class="surname">Oreglia</span></span>,
<span class="personname"><span class="firstname">Monica</span> <span class="surname">Rosenberg</span></span>,
<span class="personname"><span class="firstname">Karen</span> <span class="surname">Rustad</span></span>,
<span class="personname"><span class="firstname">Bailey</span> <span class="surname">Smith</span></span>,
<span class="personname"><span class="firstname">Leslie</span> <span class="surname">Tom</span></span>, and
<span class="personname"><span class="firstname">Anne</span> <span class="surname">Wootton</span></span> to the growing set of
student contributors. Leslie gets credit for the books title.</p><p>In Spring 2012
<span class="personname"><span class="firstname">Andrea</span> <span class="surname">Angquist</span></span>,
<span class="personname"><span class="firstname">Jacob</span> <span class="surname">Portnoff</span></span>, and
<span class="personname"><span class="firstname">Brian</span> <span class="surname">Rea</span></span>, supervised capably by
<span class="personname"><span class="firstname">Anne</span> <span class="surname">Wootton</span></span>,
were essential editorial assistants in my end-to-end effort to rewrite the drafts
of Chapters 1-7 to improve their conceptual integration and continuity.</p><p>I used draft chapters of the book in my IO &amp; IR course three times, beginning in Fall
2010. The final version of the book in 2013 barely resembles those early drafts, which means
that many students suffered to improve the book. But they didnt suffer passively. Many
students submitted problems with the Twitter hashtag #tdofix, and submitted examples using
#tdoexample, which benefited the book greatly but which surely confused their regular
Twitter followers.</p><p>Many other Berkeley students did important work on the book.
<span class="personname"><span class="firstname">Jen</span> <span class="surname">Wang</span></span>
designed the cover;
<span class="personname"><span class="firstname">Divya</span> <span class="surname">Anand</span></span>,
<span class="personname"><span class="firstname">Ajeeta</span> <span class="surname">Dhole</span></span>,
<span class="personname"><span class="firstname">Christina</span> <span class="surname">Pham</span></span>, and
<span class="personname"><span class="firstname">Raymon</span> <span class="surname">Sutedjo-The</span></span> did the illustrations;
<span class="personname"><span class="firstname">Lisa</span> <span class="surname">Jervis</span></span>,
<span class="personname"><span class="firstname">Shohei</span> <span class="surname">Narron</span></span>, and
<span class="personname"><span class="firstname">Anne</span> <span class="surname">Wootton</span></span>
worked on the extensive bibliography. A group
of students whose work does not appear in the printed book but whose efforts will be
revealed in future ebooks include
<span class="personname"><span class="firstname">Luis</span> <span class="surname">Aguilar</span></span>,
<span class="personname"><span class="firstname">Fred</span> <span class="surname">Chasen</span></span>,
<span class="personname"><span class="firstname">Philip</span> <span class="surname">Foeckler</span></span>,
<span class="personname"><span class="firstname">Jake</span> <span class="surname">Hartnell</span></span>,
<span class="personname"><span class="firstname">Eliot</span> <span class="surname">Nahman</span></span>, and
<span class="personname"><span class="firstname">AJ</span> <span class="surname">Renold</span></span>. </p><p><span class="personname"><span class="firstname">Eliot</span> <span class="surname">Kimber</span></span>
showed me that it was possible to write a book that could be published
simultaneously in print and in ebooks. It hasnt turned out to be as simple as someone as
talented as Kimber can make it seem, but I am grateful to Eliot for convincing me that I
should try to do it. With help from
<span class="personname"><span class="firstname">Bob</span> <span class="surname">Stayton</span></span>,
<span class="personname"><span class="firstname">Adam</span> <span class="surname">Witmer</span></span>
(and <span class="orgname">OReilly Publishing</span>) we will get there.</p><p>I must also thank
<span class="personname"><span class="firstname">Christine</span> <span class="surname">Borgman</span></span>
of <span class="orgname">UCLA</span> for bringing a group of energetic and
thoughtful UCLA graduate students into the project. Two of them,
<span class="personname"><span class="firstname">Matt</span> <span class="surname">Mayernik</span></span> and
<span class="personname"><span class="firstname">Alberto</span> <span class="surname">Pepe</span></span>,
are contributing authors.
<span class="personname"><span class="firstname">Amelia</span> <span class="surname">Acker</span></span>,
<span class="personname"><span class="firstname">Jillian</span> <span class="surname">Wallis</span></span>, and
<span class="personname"><span class="firstname">Laura</span> <span class="surname">Wynholds</span></span> taught me a
great deal about libraries and archives, and I am certain they tried to teach me much more
than I was able to learn.</p><p>Many people read draft chapters and were thankfully unsparing in their criticism because
they wanted to make this book as good as it could be. Thank you
<span class="personname"><span class="firstname">Scott</span> <span class="surname">Abel</span></span>,
<span class="personname"><span class="firstname">Larry</span> <span class="surname">Barsalou</span></span>,
<span class="personname"><span class="firstname">Marcia</span> <span class="surname">Bates</span></span>,
<span class="personname"><span class="firstname">Christine</span> <span class="surname">Borgman</span></span>,
<span class="personname"><span class="firstname">Michael</span> <span class="surname">Cohen</span></span>,
<span class="personname"><span class="firstname">David</span> <span class="surname">Kirsh</span></span>,
<span class="personname"><span class="firstname">Jeff</span> <span class="surname">Elman</span></span>,
<span class="personname"><span class="firstname">Rob</span> <span class="surname">Goldstone</span></span>,
<span class="personname"><span class="firstname">Jonathan</span> <span class="surname">Grudin</span></span>,
<span class="personname"><span class="firstname">Ben</span> <span class="surname">Hill</span></span>,
<span class="personname"><span class="firstname">Mano</span> <span class="surname">Marks</span></span>,
<span class="personname"><span class="firstname">Patrick</span> <span class="surname">Schmitz</span></span>,
<span class="personname"><span class="firstname">Elaine</span> <span class="surname">Svenonius</span></span>,
<span class="personname"><span class="firstname">Jeff</span> <span class="surname">Zych</span></span>,
and everyone else whom I have carelessly forgotten.</p><p>Few books have been as battle tested before they went to print as this one. Let me thank
those who have been willing to teach from a book that did not entirely exist:
<span class="personname"><span class="firstname">Jane</span> <span class="surname">Greenberg</span></span>,
<span class="personname"><span class="firstname">Irith</span> <span class="surname">Hartman</span></span>,
<span class="personname"><span class="firstname">Lauren</span> <span class="surname">Plews</span></span>,
<span class="personname"><span class="firstname">Sarah</span> <span class="surname">Ramdeen</span></span>,
<span class="personname"><span class="firstname">Christian</span> <span class="surname">Sandvig</span></span>,
<span class="personname"><span class="firstname">Emily</span> <span class="surname">Seitz</span></span>,
<span class="personname"><span class="firstname">Isabelle</span> <span class="surname">Sperano</span></span>,
<span class="personname"><span class="firstname">Konstantin</span> <span class="surname">Tovstiadi</span></span>,
<span class="personname"><span class="firstname">Hong</span> <span class="surname">Zhang</span></span>, and
especially
<span class="personname"><span class="firstname">Vivien</span> <span class="surname">Petras</span></span> and
<span class="personname"><span class="firstname">Ryan</span> <span class="surname">Shaw</span></span> who went to battle with (and for) this book multiple times.</p><h2><a id="id675719"/>The Essentials</h2><p>The third and final category of acknowledgments is for people who were essential, without
whom this project would never have been finished.</p><p><span class="personname"><span class="firstname">Jess</span> <span class="surname">Hemerly</span></span> and
<span class="personname"><span class="firstname">Kimra</span> <span class="surname">McPherson</span></span>
joined the project in the “first crusade” of Spring 2010,
worked tirelessly through that summer to make chapter drafts course-worthy, and served as
teaching assistants in Fall 2010 when the book was first tested with students. They helped
me believe that there might be a book in there somewhere when it took a lot of faith to see
that.</p><p><span class="personname"><span class="firstname">Erik</span> <span class="surname">Wilde</span></span>
taught me much through our multi-year collaboration and dialectic when he was
on the Berkeley faculty from 2006-2011. Erik made me understand the elegance and great scope
of the word “resource,” which became the central concept in this book. His meticulously
annotated reviews of many chapters from a computer science perspective helped inspire the
idea of discipline-tagged endnotes.</p><p><span class="personname"><span class="firstname">Ryan</span> <span class="surname">Shaw</span></span> and
<span class="personname"><span class="firstname">Vivien</span> <span class="surname">Petras</span></span>,
both young professors at schools a long distance from
Berkeley, found courage in themselves and had confidence in the draft book coming out of
Berkeley in 2011<span class="symbol"></span>first to teach with it, and then to help write it, becoming the primary
reviewers of my chapters and the first authors of Chapters 8 and 9. </p><p><span class="personname"><span class="firstname">Murray</span> <span class="surname">Maloney</span></span> joined the project in April 2012 as copy editor, but we together soon
recognized that his nearly three decades of <abbr class="abbrev">SGML</abbr>, <abbr class="abbrev">XML</abbr>,
and publishing experience were too
valuable not to exploit further for the benefit of this book. Without Murrays work as the
markup and production editor, indexer and glossary-maker, there would be too much work left
to do and no one capable of doing it as well as Murray has. Somehow along the way he also
found time to make important intellectual contributions as a co-author to Chapters 5 and
8.</p><p>Finally, I want to thank
<span class="personname"><span class="firstname">Pam</span> <span class="surname">Samuelson</span></span>.
She has been far too patient with me as I talked
with her, to her, and at her for three years while this book was being written, who turned
many quarter-baked ideas into half-baked ones, and who turned many half-baked ones into
cornerstones of this book. Most importantly, she has helped me focus on this book and get it
finished when it would have been easy to give up on it. I promise not to take on another
book project anytime soon because Pam has suffered enough for this one.</p><p><span class="personname"><span class="firstname">Robert</span> <span class="othername">J.</span> <span class="surname">Glushko</span></span>, 31 December 2012</p></section></body></html>

2
TDO/OEBPS/toc.ncx Normal file

File diff suppressed because one or more lines are too long

1
TDO/mimetype Normal file
View file

@ -0,0 +1 @@
application/epub+zip

View file

@ -18,6 +18,8 @@
document.onreadystatechange = function () { document.onreadystatechange = function () {
if (document.readyState == "complete") { if (document.readyState == "complete") {
FP.VERSION = "0.1.6";
FP.filePath = "/fpjs/dist/"; FP.filePath = "/fpjs/dist/";
fileStorage.filePath = FP.filePath + "libs/"; fileStorage.filePath = FP.filePath + "libs/";