<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>The Reading Room</title>
    <link>https://pulpme.sh/~sample4</link>
    <description>Notes from the stacks, with citations</description>
    <language>en</language>
    <atom:link href="https://pulpme.sh/~sample4/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A day in the reading room</title>
      <link>https://pulpme.sh/~sample4/a-day-in-the-reading-room.html</link>
      <guid isPermaLink="true">https://pulpme.sh/~sample4/a-day-in-the-reading-room.html</guid>
      <pubDate>Sat, 04 Apr 2026 00:00:00 +0000</pubDate>
      <category>practice</category>
      <category>method</category>
      <description><![CDATA[
<p>Archives close at four. Every plan has to fit inside that.</p>

<h2 id="before-you-arrive">Before you arrive</h2>

<ul>
  <li>Order the boxes in advance, always; same-day retrieval is a myth in about<br />
half the places I have worked</li>
  <li>Read the finding aid on the train, not at the desk</li>
  <li>Charge everything, because the plug sockets are theoretical</li>
</ul>

<h2 id="the-first-hour">The first hour</h2>

<p>Do not read. <em>Survey</em>. Open every folder in the first box, note what is in it,<br />
close it, move on. You are building an index of the day.</p>

<h2 id="the-second-to-fourth-hours">The second to fourth hours</h2>

<p>Now read, in the order the survey suggested, which is almost never the order<br />
the boxes are in.</p>

<h2 id="photograph-everything-you-touch">Photograph everything you touch</h2>

<ol>
  <li>A shot of the folder label, first, every single time</li>
  <li>Then the item</li>
  <li>Then, if it is more than one page, a shot of your own hand holding up the<br />
page number</li>
</ol>

<p>Step one is the one people skip, and it is the one that makes the photos<br />
usable six months later. A folder of 400 undated images with no context is not<br />
research, it is a burden you handed to yourself.</p>

<h2 id="the-last-hour">The last hour</h2>

<p>Stop reading at three. Spend the last hour writing down what you found, in<br />
prose, while the boxes are still in front of you.</p>

<h2 id="the-note-i-write-at-the-end-of-every-day">The note I write at the end of every day</h2>

<p>Three lines: what I found, what I expected and did not find, and the one box I<br />
would open first if I came back tomorrow. That third line has paid for itself<br />
more often than the other two together.</p>
]]></description>
    </item>
    <item>
      <title>Digitisation is a decision</title>
      <link>https://pulpme.sh/~sample4/digitisation-is-a-decision.html</link>
      <guid isPermaLink="true">https://pulpme.sh/~sample4/digitisation-is-a-decision.html</guid>
      <pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate>
      <category>digitisation</category>
      <category>access</category>
      <description><![CDATA[
<p>Nothing is scanned by accident. Someone chose, and the choice is almost never<br />
recorded next to the result.</p>

<h2 id="what-drives-the-choice">What drives the choice</h2>

<ul>
  <li><strong>Demand</strong>: the collections people already ask for get scanned first, which<br />
makes them get asked for more</li>
  <li><strong>Condition</strong>: too fragile to handle is a reason to scan and a reason not to</li>
  <li><strong>Rights</strong>: clear copyright is a green light, uncertain copyright is a wall</li>
  <li><strong>Funding</strong>: a grant names a collection, and that collection gets scanned<br />
whether or not it was next</li>
</ul>

<h2 id="the-compounding-effect">The compounding effect</h2>

<p>A researcher searching from home sees the scanned tenth. They cite it. The<br />
citations become evidence of demand. The demand justifies the next round of<br />
scanning, on the same tenth.</p>

<p>This is not a conspiracy, it is a <em>ratchet</em>, and it runs on its own.</p>

<h2 id="what-a-good-project-publishes-alongside">What a good project publishes alongside</h2>

<ol>
  <li>The selection criteria, in writing</li>
  <li>What was excluded and why</li>
  <li>The capture specification, so a later project knows whether to rescan</li>
  <li>A stable identifier scheme, so the links survive the next migration</li>
</ol>

<p>That last one is where most projects fail. A URL like<br />
<code>https://archive.example/viewer?id=4471&amp;session=99</code> is not an identifier, it<br />
is a coincidence, and it will not resolve in five years.</p>

<h2 id="the-one-that-works">The one that works</h2>

<p>Persistent identifiers, resolved centrally. <a href="https://www.handle.net/" rel="nofollow">The Handle System</a><br />
and DOIs both do this, and both work because the resolution is someone’s job<br />
rather than a side effect of a web server’s routing table.</p>

<h2 id="what-i-want-in-every-viewer">What I want in every viewer</h2>

<p>A visible, copyable citation string. That is it. Half the linkrot in my<br />
bibliography exists because I copied what was in the address bar.</p>
]]></description>
    </item>
    <item>
      <title>Provenance and the broken chain</title>
      <link>https://pulpme.sh/~sample4/provenance-and-the-broken-chain.html</link>
      <guid isPermaLink="true">https://pulpme.sh/~sample4/provenance-and-the-broken-chain.html</guid>
      <pubDate>Sun, 22 Feb 2026 00:00:00 +0000</pubDate>
      <category>provenance</category>
      <category>ethics</category>
      <description><![CDATA[
<p>Provenance is the record of custody: who held a thing, when, and how it moved.<br />
A gap in that record is a fact about the record, not necessarily a fact about<br />
the thing.</p>

<h2 id="reading-a-gap">Reading a gap</h2>

<p>A chain that runs 1890, 1912, then jumps to 1958 has a gap that covers the<br />
years that matter most in European collections, and everyone in the field<br />
knows it. The <a href="https://www.state.gov/" rel="nofollow">Washington Principles</a> exist for<br />
precisely that shape of gap.</p>

<h2 id="what-the-gap-can-mean">What the gap can mean</h2>

<ol>
  <li>The dealer’s records burned, which happened constantly</li>
  <li>The owner was private and asked to stay private</li>
  <li>Nobody wrote it down, because until the 1990s nobody had to</li>
  <li>Something happened that someone did not want written down</li>
</ol>

<p>Only the fourth is the one people mean. The other three are more common.</p>

<h2 id="the-research-path">The research path</h2>

<ul>
  <li>Auction catalogues, which are often the only dated evidence</li>
  <li>Dealer stock books, where they survive</li>
  <li>Exhibition catalogues, which place an object in a room on a date</li>
  <li>Insurance schedules, the most reliable and the hardest to see</li>
</ul>

<h2 id="links-out-of-a-post-like-this">Links out of a post like this</h2>

<p>Every outbound link in this post carries <code>rel="nofollow"</code>, which is a small<br />
statement: I am pointing at this, not vouching for it. In a field where<br />
pointing at a dealer’s site is not an endorsement of the dealer, that<br />
distinction earns its keep.</p>

<p>An internal link is different. <a href="the-catalogue-is-not-the-collection.html">The catalogue is not the collection</a><br />
is mine, and pointing at it is vouching for it.</p>

<h2 id="the-honest-conclusion">The honest conclusion</h2>

<p>Most gaps are boring. The discipline is treating every one as a question until<br />
it is answered, without pretending a question is an accusation.</p>
]]></description>
    </item>
    <item>
      <title>The catalogue is not the collection</title>
      <link>https://pulpme.sh/~sample4/the-catalogue-is-not-the-collection.html</link>
      <guid isPermaLink="true">https://pulpme.sh/~sample4/the-catalogue-is-not-the-collection.html</guid>
      <pubDate>Fri, 30 Jan 2026 00:00:00 +0000</pubDate>
      <category>cataloguing</category>
      <category>opinion</category>
      <description><![CDATA[
<p>A catalogue record is a description of a thing, written once, by a person, in<br />
an afternoon, twenty years ago.</p>

<h2 id="what-gets-lost">What gets lost</h2>

<ul>
  <li>Anything the cataloguer did not think was the point</li>
  <li>Anything in a language they did not read</li>
  <li>Everything on the back of everything</li>
</ul>

<h2 id="why-the-search-fails">Why the search fails</h2>

<p>You search for a word. The record contains a description of the word. If the<br />
cataloguer wrote <em>correspondence</em> and you searched for <em>letters</em>, the<br />
collection is invisible to you and neither of you did anything wrong.</p>

<p>The fix is controlled vocabulary, which is why<br />
<a href="https://id.loc.gov/authorities/subjects.html" rel="nofollow">Library of Congress Subject Headings</a><br />
exist and why nobody enjoys them.</p>

<h2 id="searching-around-the-record">Searching around the record</h2>

<ol>
  <li>Find one item you know is in the collection</li>
  <li>Look at the subject headings on <em>its</em> record</li>
  <li>Search those headings, not your own words</li>
  <li>Repeat with whatever new headings turn up</li>
</ol>

<p>This is citation chaining pointed at metadata instead of bibliography.</p>

<h2 id="the-underscore-problem">The underscore problem</h2>

<p>Archive systems love identifiers like <code>MS_1904_series_b</code> and<br />
<code>coll_finding_aid_v2</code>. Written in running prose without code formatting, a<br />
naive emphasis rule eats the middle: MS_1904_series_b would come out with<br />
<em>1904</em> in italics if underscores delimited emphasis anywhere. They do not,<br />
only at word boundaries, which is why <em>this</em> is emphasis and that is not.</p>

<h2 id="what-to-do-about-it">What to do about it</h2>

<p>Write to the archivist. Every collection has one, most of them answer, and a<br />
five-line email saves a wasted day in a reading room three hundred miles away.</p>
]]></description>
    </item>
    <item>
      <title>Finding aids</title>
      <link>https://pulpme.sh/~sample4/finding-aids.html</link>
      <guid isPermaLink="true">https://pulpme.sh/~sample4/finding-aids.html</guid>
      <pubDate>Fri, 09 Jan 2026 00:00:00 +0000</pubDate>
      <category>archives</category>
      <category>method</category>
      <description><![CDATA[
<p>A finding aid is a map of a collection. Read it badly and you order the wrong<br />
box, wait a day, and read it again.</p>

<h2 id="the-four-sections">The four sections</h2>

<p>Every aid has the same skeleton, whatever the institution calls it. The<br />
<a href="https://dictionary.archivists.org/" rel="nofollow">Society of American Archivists glossary</a><br />
is the reference I keep open, and the<br />
<a href="https://www.ica.org/standards/" rel="nofollow">ISAD(G) standard</a> is the reason the sections<br />
are the same everywhere.</p>

<p>Note that the label there contains brackets of its own. A link label is<br />
matched by counting brackets, not by finding the first <code>]</code>, which is exactly<br />
what a title like ISAD(G) or [Sic] needs.</p>

<h2 id="scope-and-content">Scope and content</h2>

<p>The paragraph that tells you what is <em>actually</em> in the collection, as opposed<br />
to what the collection is named after. Read this twice.</p>

<h2 id="arrangement">Arrangement</h2>

<p>Series, subseries, boxes, folders. The unit you can request is usually the<br />
box, so the folder list is a preview, not a menu.</p>

<h2 id="restrictions">Restrictions</h2>

<p>The section people skip. It is where you learn that the interesting series is<br />
closed until 2041.</p>

<h2 id="citing-what-you-find">Citing what you find</h2>

<p>The house style at most reading rooms is collection, series, box, folder,<br />
institution. A citation marker like [1] in running prose is not a link and<br />
must never become one; it is a bracket, a digit and a bracket, and any<br />
renderer that turns it into an anchor has broken the citation.</p>

<p>For the full form see <a href="https://www.chicagomanualofstyle.org/" rel="nofollow">the Chicago manual’s archives<br />
chapter</a>, which is behind a paywall<br />
and worth exactly what your institution pays for it.</p>
]]></description>
    </item>
  </channel>
</rss>
