blog/archive/2019/05/05.rss

   1 <?xml version="1.0" encoding="ISO-8859-1"?>
   2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
   3         <channel>
   4                 <title>Petter Reinholdtsen - Entries from May 2019</title>
   5                 <description>Entries from May 2019</description>
   6                 <link>http://www.hungry.com/~pere/blog/</link>
   7
   8
   9         <item>
  10                 <title>Nikita version 0.4 released - free software archive API server</title>
  11                 <link>http://www.hungry.com/~pere/blog/Nikita_version_0_4_released___free_software_archive_API_server.html</link>
  12                 <guid isPermaLink="true">http://www.hungry.com/~pere/blog/Nikita_version_0_4_released___free_software_archive_API_server.html</guid>
  13                 <pubDate>Wed, 22 May 2019 11:30:00 +0200</pubDate>
  14                 <description>&lt;p&gt;This morning,  a new release of
  15 &lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core/&quot;&gt;Nikita
  16 Noark 5 core project&lt;/a&gt; was
  17 &lt;a href=&quot;https://lists.nuug.no/pipermail/nikita-noark/2019-May/000468.html&quot;&gt;announced
  18 on the project mailing list&lt;/a&gt;.  The Nikita free software solution is
  19 an implementation of the Norwegian archive standard Noark 5 used by
  20 government offices in Norway.  These were the changes in version 0.4
  21 since version 0.3, see the email link above for links to a demo site:&lt;/p&gt;
  22
  23 &lt;ul&gt;
  24
  25   &lt;li&gt;Roll out OData handling to all endpoints where applicable&lt;/li&gt;
  26   &lt;li&gt;Changed the relation key for &quot;ny-journalpost&quot; to the official one.&lt;/li&gt;
  27   &lt;li&gt;Better link generation on outgoing links.&lt;/li&gt;
  28   &lt;li&gt;Tidy up code and make code and approaches more consistent throughout
  29    the codebase&lt;/li&gt;
  30   &lt;li&gt;Update rels to be in compliance with updated version in the
  31    interface standard&lt;/li&gt;
  32   &lt;li&gt;Avoid printing links on empty objects as they can&#39;t have links&lt;/li&gt;
  33   &lt;li&gt;Small bug fixes and improvements&lt;/li&gt;
  34   &lt;li&gt;Start moving generation of outgoing links to @Service layer so access
  35    control can be used when generating links&lt;/li&gt;
  36   &lt;li&gt;Log exception that was being swallowed so it&#39;s traceable&lt;/li&gt;
  37   &lt;li&gt;Fix name mapping problem&lt;/li&gt;
  38   &lt;li&gt;Update templated printing so templated should only be printed if it
  39    is set true. Requires more work to roll out across entire
  40    application.&lt;/li&gt;
  41   &lt;li&gt;Remove Record-&gt;DocumentObject as per domain model of n5v4&lt;/li&gt;
  42   &lt;li&gt;Add ability to delete lists filtered with OData&lt;/li&gt;
  43   &lt;li&gt;Return NO_CONTENT (204) on delete as per interface standard&lt;/li&gt;
  44   &lt;li&gt;Introduce support for ConstraintViolationException exception&lt;/li&gt;
  45   &lt;li&gt;Make Service classes extend NoarkService&lt;/li&gt;
  46   &lt;li&gt;Make code base respect X-Forwarded-Host, X-Forwarded-Proto and
  47    X-Forwarded-Port&lt;/li&gt;
  48   &lt;li&gt;Update CorrespondencePart* code to be more in line with Single
  49    Responsibility Principle&lt;/li&gt;
  50   &lt;li&gt;Make package name follow directory structure&lt;/li&gt;
  51   &lt;li&gt;Make sure Document number starts at 1, not 0&lt;/li&gt;
  52   &lt;li&gt;Fix isues discovered by FindBugs&lt;/li&gt;
  53   &lt;li&gt;Update from Date to ZonedDateTime&lt;/li&gt;
  54   &lt;li&gt;Fix wrong tablename&lt;/li&gt;
  55   &lt;li&gt;Introduce Service layer tests&lt;/li&gt;
  56   &lt;li&gt;Improvements to CorrespondencePart&lt;/li&gt;
  57   &lt;li&gt;Continued work on Class / Classificationsystem&lt;/li&gt;
  58   &lt;li&gt;Fix feature where authors were stored as storageLocations&lt;/li&gt;
  59   &lt;li&gt;Update HQL builder for OData&lt;/li&gt;
  60   &lt;li&gt;Update OData search capability from webpage&lt;/li&gt;
  61
  62 &lt;/ul&gt;
  63
  64 &lt;p&gt;If free and open standardized archiving API sound interesting to
  65 you, please contact us on IRC
  66 (&lt;a href=&quot;irc://irc.freenode.net/%23nikita&quot;&gt;#nikita on
  67 irc.freenode.net&lt;/a&gt;) or email
  68 (&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;nikita-noark
  69 mailing list&lt;/a&gt;).&lt;/p&gt;
  70
  71 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
  72 activities, please send Bitcoin donations to my address
  73 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
  74 </description>
  75         </item>
  76
  77         <item>
  78                 <title>MIME type &quot;text/vnd.sosi&quot; for SOSI map data</title>
  79                 <link>http://www.hungry.com/~pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html</link>
  80                 <guid isPermaLink="true">http://www.hungry.com/~pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html</guid>
  81                 <pubDate>Mon, 20 May 2019 08:35:00 +0200</pubDate>
  82                 <description>&lt;p&gt;As part of my involvement in the work to
  83 &lt;a href=&quot;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard&quot;&gt;standardise
  84 a REST based API for Noark 5&lt;/a&gt;, the Norwegian archiving standard, I
  85 spent some time the last few months to try to register a
  86 &lt;a href=&quot;https://www.iana.org/assignments/media-types/&quot;&gt;MIME type&lt;/a&gt;
  87 and &lt;a href=&quot;https://www.nationalarchives.gov.uk/PRONOM/&quot;&gt;PRONOM
  88 code&lt;/a&gt; for the SOSI file format.  The background is that there is a
  89 set of formats approved for long term storage and archiving in Norway,
  90 and among these formats, SOSI is the only format missing a MIME type
  91 and PRONOM code.&lt;/p&gt;
  92
  93 &lt;p&gt;What is SOSI, you might ask?  To quote Wikipedia: SOSI is short for
  94 Samordnet Opplegg for Stedfestet Informasjon (literally &quot;Coordinated
  95 Approach for Spatial Information&quot;, but more commonly expanded in
  96 English to Systematic Organization of Spatial Information).  It is a
  97 text based file format for geo-spatial vector information used in
  98 Norway.  Information about the SOSI format can be found in English
  99 from &lt;a href=&quot;https://en.wikipedia.org/wiki/SOSI&quot;&gt;Wikipedia&lt;/a&gt;.  The
 100 specification is available in Norwegian from
 101 &lt;a href=&quot;https://www.kartverket.no/geodataarbeid/Standarder/SOSI/&quot;&gt;the
 102 Norwegian mapping authority&lt;/a&gt;.  The SOSI standard, which originated
 103 in the beginning of nineteen eighties, was the inspiration and formed the
 104 basis for the XML based
 105 &lt;a href=&quot;https://en.wikipedia.org/wiki/Geography_Markup_Language&quot;&gt;Geography
 106 Markup Language&lt;/a&gt;.&lt;/p&gt;
 107
 108 &lt;p&gt;I have so far written
 109 &lt;a href=&quot;https://github.com/file/file/pull/67&quot;&gt;a pattern matching
 110 rule&lt;/a&gt; for the file(1) unix tool to recognize SOSI files, submitted
 111 a request to the PRONOM project to have a PRONOM ID assigned to the
 112 format (reference TNA1555078202S60), and today send a request to IANA
 113 to register the &quot;text/vnd.sosi&quot; MIME type for this format (referanse
 114 &lt;a href=&quot;https://tools.iana.org/public-view/viewticket/1143144&quot;&gt;IANA
 115 #1143144&lt;/a&gt;).  If all goes well, in a few months, anyone implementing
 116 the Noark 5 Tjenestegrensesnitt API spesification should be able to
 117 use an official MIME type and PRONOM code for SOSI files.  In
 118 addition, anyone using SOSI files on Linux should be able to
 119 automatically recognise the format and web sites handing out SOSI
 120 files can begin providing a more specific MIME type.  So far, SOSI
 121 files has been handed out from web sites using the
 122 &quot;application/octet-stream&quot; MIME type, which is just a nice way of
 123 stating &quot;I do not know&quot;.  Soon, we will know. :)&lt;/p&gt;
 124
 125 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 126 activities, please send Bitcoin donations to my address
 127 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 128 </description>
 129         </item>
 130
 131         </channel>
 132 </rss>