<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Manx on His Deeds Are Dust</title>
    <link>https://hisdeedsaredust.com/tags/manx/</link>
    <description>Recent content in Manx on His Deeds Are Dust</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <copyright>Paul Flo Williams</copyright>
    <lastBuildDate>Tue, 27 Dec 2022 13:40:04 +0000</lastBuildDate><atom:link href="https://hisdeedsaredust.com/tags/manx/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Manx da capo</title>
      <link>https://hisdeedsaredust.com/posts/2022/manx-dc/</link>
      <pubDate>Tue, 27 Dec 2022 13:40:04 +0000</pubDate>
      
      <guid>https://hisdeedsaredust.com/posts/2022/manx-dc/</guid>
      <description>&lt;p&gt;Over lockdown, I was revisiting some old projects and taking the opportunity to see if they would benefit from a fresh pair of eyes
and new learning over the last decade.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://vt100.net/manx/&#34;&gt;Manx&lt;/a&gt; was one such; a catalogue of old computer manuals that I created 20 years ago and worked on until
2009, at which point some major changes in my life meant I could no longer sustain the effort to maintain what had always been a
single person task. Although I&amp;rsquo;d had plans to allow multiple editors to add content, the tooling was always the least exciting part
of the project and only two of us had ever maintained it.&lt;/p&gt;
&lt;p&gt;The Perl source for the application and the database had been dumped and distributed, and I mostly forgot about it. It was
rewritten in PHP by someone else and placed online.&lt;/p&gt;
&lt;p&gt;Over a decade on and, I had started work on a new, large art-history database (a catalogue raisonné for the artist &lt;a href=&#34;//acmichael.org&#34;&gt;A. C.
Michael&lt;/a&gt;)
and had learned a lot about improved database queries, application structure, testing and templating of web applications as well as,
crucially, backend tooling. So I took a look at upgrading Manx, to satisfy my own curiosity.&lt;/p&gt;
&lt;p&gt;This is still a work in progress and I&amp;rsquo;ll be writing more about this over the coming months. The significant changes so far, not all
user-visible, are:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Citations have been added, so that publications mentioned by related documents or catalogues are explicitly marked. This should
answer questions about why a given document is in the catalogue at all.&lt;/li&gt;
&lt;li&gt;Some documents incorporate others. For example, print sets are frequently assemblies of lower level parts. These are now
explicit in the database.&lt;/li&gt;
&lt;li&gt;Pages are generated using a template engine. Apart from the benefit of separating functionality from presentation, the discipline
of retrieving all the relevant information from the database before &amp;ldquo;pouring&amp;rdquo; it into a template for display allows the
information to also be made available in other forms. I can now use the same backend for powering the command line tools I use for
updating the database by sending JSON extracts as well as HTML.&lt;/li&gt;
&lt;li&gt;The back-end spidering software now provides a much faster way of updating websites that contain scanned documents.&lt;/li&gt;
&lt;li&gt;Different versions of documents can now be grouped in the database to provide a clearer view of supersessions.&lt;/li&gt;
&lt;li&gt;The number of documents in the database has climbed by 13000 to over 35000, with another 7000 references to online scans.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;I have spoken to the person who took on the job of maintenance of the database many years ago. I haven&amp;rsquo;t yet worked out how we can
collaborate with the new features but it is not completely off my radar.&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>
