<link>http://people.skolelinux.org/pere/blog/</link>
<atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
+ <item>
+ <title>Nikita version 0.6 released - free software archive API server</title>
+ <link>http://people.skolelinux.org/pere/blog/Nikita_version_0_6_released___free_software_archive_API_server.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Nikita_version_0_6_released___free_software_archive_API_server.html</guid>
+ <pubDate>Thu, 10 Jun 2021 17:10:00 +0200</pubDate>
+ <description><p>I am very pleased to be able to share with you
+<a href="https://lists.nuug.no/pipermail/nikita-noark/2021-June/000576.html">the
+announcement of a new version of the archiving system Nikita</a>
+published by its lead developer Thomas Sødring:</p>
+
+<p><blockquote>
+
+<p>It is with great pleasure that we can announce a new release of
+nikita. Version 0.6
+(<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core">https://gitlab.com/OsloMet-ABI/nikita-noark5-core</a>). This
+release makes new record keeping functionality available. This really
+is a maturity release. Both in terms of functionality but also code.
+Considerable effort has gone into refactoring the codebase and
+simplifying the code. Notable changes for this release include:</p>
+
+<ul>
+
+ <li>Significantly improved OData parsing</li>
+ <li>Support for business specific metadata and national identifiers</li>
+ <li>Continued implementation of domain model and endpoints</li>
+ <li>Improved testing</li>
+ <li>Ability to export and import from arkivstruktur.xml</li>
+
+</ul>
+
+<p>We are currently in the process of reaching an agreement with an
+archive institution to publish their picture archive using nikita with
+business specific metadata and we hope that we can share this with you
+soon. This is an interesting project as it allows the organisation to
+bring an older picture archive back to life while using the original
+metadata values stored as business specific metadata. Combined with
+OData means the scope and use of the archive is significantly
+increased and will showcase both the flexibility and power of
+Noark.</p>
+
+<p>I really think we are approaching a version 1.0 of nikita, even
+though there is still a lot of work to be done. The notable work at
+the moment is to implement access-control and full text indexing of
+documents.</p>
+
+<p>My sincere thanks to everyone who has contributed to this
+release!</p>
+
+<p>- Thomas</p>
+
+<p><strong>Release 0.6 2021-06-10 (d1ba5fc7e8bad0cfdce45ac20354b19d10ebbc7b)</strong></p>
+
+<ul>
+
+ <li>Refactor metadata entity search</li>
+ <li>Remove redundant security configuration</li>
+ <li>Make OpenAPI documentation work</li>
+ <li>Change database structure / inheritance model to a more sensible approach</li>
+ <li>Make it possible to move entities around the fonds structure</li>
+ <li>Implemented a number of missing endpoints</li>
+ <li>Make sure yml files are in sync</li>
+ <li>Implemented/finalised storing and use of
+ <ul>
+ <li>Business Specific Metadata</li>
+ <li>Norwegian National Identifiers</li>
+ <li>Cross Reference</li>
+ <li>Keyword</li>
+ <li>StorageLocation</li>
+ <li>Author</li>
+ <li>Screening for relevant objects</li>
+ <li>ChangeLog</li>
+ <li>EventLog</li>
+ </ul></li>
+ <li>Make generation of updated docker image part of successful CI pipeline</li>
+ <li>Implement pagination for all list requests
+ <ul>
+ <li>Refactor code to support lists</li>
+ <li>Refactor code for readability</li>
+ <li>Standardise the controller/service code</li>
+ </ul></li>
+ <li>Finalise File->CaseFile expansion and Record->registryEntry/recordNote
+expansion</li>
+ <li>Improved Continuous Integration (CI) approach via gitlab</li>
+ <li>Changed conversion approach to generate tagged PDF documents</li>
+ <li>Updated dependencies
+ <ul>
+ <li>For security reasons</li>
+ <li>Brought codebase to spring-boot version 2.5.0</li>
+ <li>Remove import of necessary dependencies</li>
+ <li>Remove non-used metrics classes</li>
+ </ul></li>
+ <li>Added new analysis to CI including</li>
+ <li>Implemented storing of Keyword</li>
+ <li>Implemented storing of Screening and ScreeningMetadata</li>
+ <li>Improved OData support
+ <ul>
+ <li>Better support for inheritance in queries where applicable</li>
+ <li>Brought in more OData tests</li>
+ <li>Improved OData/hibernate understanding of queries</li>
+ <li>Implement $count, $orderby</li>
+ <li>Finalise $top and $skip</li>
+ <li>Make sure & is used between query parameters</li>
+ </ul></li>
+ <li>Improved Testing in codebase
+ <ul>
+ <li>A new approach for integration tests to make test more readable</li>
+ <li>Introduce tests in parallel with code development for TDD approach</li>
+ <li>Remove test that required particular access to storage</li>
+ </ul></li>
+ <li>Implement case-handling process from received email to case-handler
+ <ul>
+ <li>Develop required GUI elements (digital postroom from email)</li>
+ <li>Introduced leader, quality control and postroom roles</li>
+ </ul></li>
+ <li>Make PUT requests return 200 OK not 201 CREATED</li>
+ <li>Make DELETE requests return 204 NO CONTENT not 200 OK</li>
+ <li>Replaced 'oppdatert*' with 'endret*' everywhere to match latest spec</li>
+ <li>Upgrade Gitlab CI to use python > 3 for CI scripts</li>
+ <li>Bug fixes
+ <ul>
+ <li>Fix missing ALLOW</li>
+ <li>Fix reading of objects from jar file during start-up</li>
+ <li>Reduce the number of warnings in the codebase</li>
+ <li>Fix delete problems</li>
+ <li>Make better use of cascade for "leaf" objects</li>
+ <li>Add missing annotations where relevant</li>
+ <li>Remove the use of ETAG for delete</li>
+ <li>Fix missing/wrong/broken rels discovered by runtest</li>
+ <li>Drop unofficial convertFil (konverterFil) end point</li>
+ <li>Fix regex problem for dateTime</li>
+ <li>Fix multiple static analysis issues discovered by coverity</li>
+ <li>Fix proxy problem when looking for object class names</li>
+ <li>Add many missing translated Norwegian to English (internal)
+attribute/entity names</li>
+ <li>Change UUID generation approach to allow code also set a value</li>
+ <li>Fix problem with Part/PartParson</li>
+ <li>Fix problem with empty OData search results</li>
+ <li>Fix metadata entity domain problem</li>
+ </ul></li>
+ <li>General Improvements
+ <ul>
+ <li>Makes future refactoring easier as coupling is reduced</li>
+ <li>Allow some constant variables to be set from property file</li>
+ <li>Refactor code to make reflection work better across codebase</li>
+ <li>Reduce the number of @Service layer classes used in @Controller
+classes</li>
+ <li>Be more consistent on naming of similar variable types</li>
+ <li>Start printing rels/href if they are applicable</li>
+ <li>Cleaner / standardised approach to deleting objects</li>
+ <li>Avoid concatenation when using StringBuilder</li>
+ <li>Consolidate code to avoid duplication</li>
+ <li>Tidy formatting for a more consistent reading style across
+similar class files</li>
+ <li>Make throw a log.error message not an log.info message</li>
+ <li>Make throw print the log value rather than printing in multiple
+places</li>
+ <li>Add some missing pronom codes</li>
+ <li>Fix time formatting issue in Gitlab CI</li>
+ <li>Remove stale / unused code</li>
+ <li>Use only UUID datatype rather than combination String/UUID for systemID</li>
+ <li>Mark variables final and @NotNull where relevant to indicate
+intention</li>
+ </ul></li>
+ <li>Change Date values to DateTime to maintain compliance with Noark 5
+standard</li>
+ <li>Domain model improvements using Hypersistence Optimizer
+ <ul>
+ <li>Move @Transactional from class to methods to avoid borrowing the JDBC Connection unnecessarily</li>
+ <li>Fix OneToOne performance issues</li>
+ <li>Fix ManyToMany performance issues</li>
+ <li>Add missing bidirectional synchronization support</li>
+ <li>Fix ManyToMany performance issue</li>
+ </ul></li>
+ <li>Make List<> and Set<> use final-keyword to avoid potential problems
+during update operations</li>
+ <li>Changed internal URLs, replaced "hateoas-api" with "api".</li>
+ <li>Implemented storing of Precedence.</li>
+ <li>Corrected handling of screening.</li>
+ <li>Corrected _links collection returned for list of mixed entity types
+to match the specific entity.</li>
+ <li>Improved several internal structures.</li>
+</ul>
+
+</blockquote></p>
+
+<p>If free and open standardized archiving API sound interesting to
+you, please contact us on IRC
+(<a href="irc://irc.oftc.net/%23nikita">#nikita on
+irc.oftc.net</a>) or email
+(<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">nikita-noark
+mailing list</a>).</p>
+
+<p>As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
+</description>
+ </item>
+
+ <item>
+ <title>VLC bittorrent plugin in Bullseye, saved by the bell?</title>
+ <link>http://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_in_Bullseye__saved_by_the_bell_.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_in_Bullseye__saved_by_the_bell_.html</guid>
+ <pubDate>Sat, 1 May 2021 11:00:00 +0200</pubDate>
+ <description><p>Yesterday morning I got a warning call from the Debian quality
+control system that
+<a href="https://tracker.debian.org/pkg/vlc-plugin-bittorrent">the VLC
+bittorrent plugin</a> was due to be removed because of a release
+critical bug in one of its dependencies. As you might remember, this
+plugin make VLC able to stream videos directly from a bittorrent
+source using both torrent files and magnet links, similar to using a
+HTTP source. I believe such protocol support is a vital feature in
+VLC, allowing efficient streaming from sources such at the almost 7
+million movies in <a href="https://archive.org/">the Internet
+Archive</a>.</p>
+
+<p>The dependency was the unmaintained
+<a href="https://tracker.debian.org/pkg/libtorrent-rasterbar">libtorrent-rasterbar</a>
+package, and <a href="https://bugs.debian.org/987306">the bug in
+question</a> blocked its python library from working properly. As I
+did not want Bullseye to release without bittorrent support in VLC, I
+set out to check out the status, and track down a fix for the problem.
+Luckily the issue had already been identified and fixed upstream,
+providing everything needed. All I needed to do was to fetch the
+Debian git repository, extract and trim the patch from upstream and
+apply it to the Debian package for upload.</p>
+
+<p>The fixed library was uploaded yesterday evening. But that is not
+enough to get it into Bullseye, as Debian is currently in package
+freeze to prepare for a new next stable release. Only non-critical
+packages with
+<a href="https://wiki.debian.org/ContinuousIntegration/autopkgtest">autopkgtest
+setup</a> included, in other words able to validate automatically that
+the package is working, are allowed to migrate automatically into the
+next release at this stage. And the unmaintained libtorrent-rasterbar
+lack such testing, and thus needed a manual override. I am happy to
+report that such manual override was approved a few minutes ago, thus
+increasing significantly the chance of VLC bittorrent streaming being
+available out of the box also for Debian/Buster users. A bit too
+close shave for my liking, as the Bullseye release is most likely just
+a few days away, and this did feel like the package was saved by the
+bell. I am so glad the warning email showed up in time for me to
+handle the issue, and a big thanks go to the Debian Release team for
+the quick feedback on
+<a href="irc://irc.debian.org/%23debian-release">#debian-release</a>
+and their <a href="https://bugs.debian.org/987865">swift
+unblocking</a>.</p>
+
+<p>As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
+</description>
+ </item>
+
<item>
<title>Updated Valutakrambod, now also with information from NBX</title>
<link>http://people.skolelinux.org/pere/blog/Updated_Valutakrambod__now_also_with_information_from_NBX.html</link>
looked at the code. I also added support for fetching the order book
from the newcomer Norwegian Bitcoin Exchange.</p>
-<p>I alsod decided to migrate the project from github to gitlab in the
+<p>I also decided to migrate the project from github to gitlab in the
process. If you want a python library for talking to various currency
exchanges, check out
<a href="https://gitlab.com/petterreinholdtsen/valutakrambod">code for
<p>I recommend you check out this simple and powerful approach to more
secure network connections. :)</p>
-<p>As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
-<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
-</description>
- </item>
-
- <item>
- <title>Bompenge-Norge, med noen tall fra bompengekalkulator</title>
- <link>http://people.skolelinux.org/pere/blog/Bompenge_Norge__med_noen_tall_fra_bompengekalkulator.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bompenge_Norge__med_noen_tall_fra_bompengekalkulator.html</guid>
- <pubDate>Mon, 1 Jun 2020 14:50:00 +0200</pubDate>
- <description><p>Det er tett med sensorstasjoner langs veinettet i Norge, som
-registrerer hvilke kjøretøy som passerer eller tar bilde av de som
-drar forbi. I følge
-<a href="https://vegkart.atlas.vegvesen.no/">Vegvesenets nasjonale
-veidatabank (NVDB)</a>, er det 353 bomstasjoner langs det norske
-veinettet. 21 i nordnorge, 48 i trøndelagsområdet, 13 på
-nordvestlandet, 91 i bergenstraktene og 180 på østlandsområdet. I
-tillegg finnes det et utall overvåkningskamera og noen titalls
-RFID-avlesere for bompengebrikker som samler inn informasjon om hvilke
-biler som befinner seg hvor i landet. For ikke å glemme alle
-mobilbasestasjoner som registrerer hvor brukere av mobilnettverket
-befinner seg. De er ikke tema i dag.</p>
-
-<p>De som kjører mye har interesse av å vite hvor mye bompenger det vil
-koste å kjøre fra et sted til et annet, og dette behovet har aktørene
-bak <a href="https://bompengekalkulator.no/">Bompengekalkulatoren</a>
-tatt sikte på å tilby i markedet. Fornuftig nok har de også en
-gratistjeneste, slik at de får frivillige til å gi innspill om feil i
-datagrunnlaget. Jeg ble nylig nysgjerring på hvor mye det til koste å
-kjøre på kryss og tvers i Norge, og valgte meg ut en teststrekning fra
-Oslo til Tromsø for å se hvilke beløp som gjelder.</p>
-
-<p>Bompengekalkulatoren viser frem flere rutealternativer for et gitt
-reisesøk, og i dette tilfellet, for reise fra Oslo Sentralstasjon til
-Tromsø sentrum, viser den tre alternativ. Merk, disse tallene gjelder
-bensindrevet personbil. En kan velge takstkategori i
-webgrensesnittet. Det ene rutealternativet er E6 gjennom Norge, de to
-andre er E45 og E4 gjennom sverige. E45 er innlandsruten i Sverige,
-motorvei gjennom store skoger som i følge kalkulatoren skal ta 22
-timer og 26 minutter med norsk bompengebeløp på 164 kroner. Jeg har
-mine tvil til om datasettet til Bompengekalkulatoren har svenske
-bomstasjoner, så ta dette beløpet med en klype salt. E4 er veien
-langs Bottenviken og mer befolket område, og skal ta 22 timer og 50
-minutter til en norsk bompengebeløp på 71 kroner. Den norske ruten
-langs E6 skal derimot ta 23 timer og 16 minutter og beløpe seg til 664
-kroner. Beløpene er uten autopass-brikke, slik at en slipper å få
-bilens posisjon registrert i alle bompengebrikkeavleserne som ikke
-også er bomstasjoner. For trailere er bompengekostnaden 2-3 ganger så
-høy som for personbil. I tillegg til pengebeløpet, som faktureres
-etterskuddsvis og de siste årene har blitt umulig å gjøre opp kontant
-på stedet, så kommer kostnaden med å få sine personopplysninger samlet
-inn, lagret og gjort tilgjengelig for fremmede på ubestemt tid. Jeg
-ser på den kostnaden som mye høyere en pengebeløpet som
-faktureres.</p>
-
-<p>For en tilsvarende tur fra Oslo til Bergen, så forteller
-kalkulatoren at raskeste vei er riksvei 7 på 7 timer 4 minutter med
-bompengebeløp 409 kroner. Alternativene listet opp er E134 på 8 timer
-37 minutter med bompengebeløp 318 kroner og fylkesivei 40 på 7 timer
-30 minutter med beløp 331. Det kan kanskje være greit å sjekke ut før
-en setter seg i bilen hvor ens personopplysninger vil bli samlet inn
-og lagret 5 fem år, når en velger hvilken rute en går for.</p>
-
-<p>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
-det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
-til min adresse
-<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.
-Merk, betaling med bitcoin er ikke anonymt. :)</p>
-</description>
- </item>
-
- <item>
- <title>More reliable vlc bittorrent plugin in Debian (version 2.9)</title>
- <link>http://people.skolelinux.org/pere/blog/More_reliable_vlc_bittorrent_plugin_in_Debian__version_2_9_.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_reliable_vlc_bittorrent_plugin_in_Debian__version_2_9_.html</guid>
- <pubDate>Sun, 24 May 2020 17:00:00 +0200</pubDate>
- <description><p>I am very happy to report that a more reliable
-<a href="https://tracker.debian.org/pkg/vlc-plugin-bittorrent">VLC
-bittorrent plugin</a> was just uploaded into debian. This fixes a
-couple of crash bugs in the plugin, hopefully making the VLC
-experience even better when streaming directly from a bittorrent
-source. The package is currently in Debian unstable, but should be
-available in Debian testing in two days. To test it, simply install
-it like this:</p>
-
-<p><pre>
-apt install vlc-plugin-bittorrent
-</pre></p>
-
-<p>After it is installed, you can try to use it to play a file
-downloaded live via bittorrent like this:
-
-<p><pre>
-vlc https://archive.org/download/Glass_201703/Glass_201703_archive.torrent
-</pre></p>
-
-<p>It also support magnet links and local .torrent files.</p>
-
<p>As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
projects / homepage.git / blobdiff