X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/5389aa8225cfa1bf817bfd12d59b2ef0e8234a44..cc9541789efd66d1eac7c5be35a86ddc5f681f38:/blog/index.rss diff --git a/blog/index.rss b/blog/index.rss index 7ed2b56dfc..83e9529d65 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -7,116 +7,76 @@ - Cura, the nice 3D print slicer, is now in Debian Unstable - http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html - http://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html - Sun, 17 Dec 2017 07:00:00 +0100 - <p>After several months of working and waiting, I am happy to report -that the nice and user friendly 3D printer slicer software Cura just -entered Debian Unstable. It consist of five packages, -<a href="https://tracker.debian.org/pkg/cura">cura</a>, -<a href="https://tracker.debian.org/pkg/cura-engine">cura-engine</a>, -<a href="https://tracker.debian.org/pkg/libarcus">libarcus</a>, -<a href="https://tracker.debian.org/pkg/fdm-materials">fdm-materials</a>, -<a href="https://tracker.debian.org/pkg/libsavitar">libsavitar</a> and -<a href="https://tracker.debian.org/pkg/uranium">uranium</a>. The last -two, uranium and cura, entered Unstable yesterday. This should make -it easier for Debian users to print on at least the Ultimaker class of -3D printers. My nearest 3D printer is an Ultimaker 2+, so it will -make life easier for at least me. :)</p> - -<p>The work to make this happen was done by Gregor Riepl, and I was -happy to assist him in sponsoring the packages. With the introduction -of Cura, Debian is up to three 3D printer slicers at your service, -Cura, Slic3r and Slic3r Prusa. If you own or have access to a 3D -printer, give it a go. :)</p> - -<p>The 3D printer software is maintained by the 3D printer Debian -team, flocking together on the -<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general">3dprinter-general</a> -mailing list and the -<a href="irc://irc.debian.org/#debian-3dprinting">#debian-3dprinting</a> -IRC channel.</p> - -<p>The next step for Cura in Debian is to update the cura package to -version 3.0.3 and then update the entire set of packages to version -3.1.0 which showed up the last few days.</p> + Oppdatert Noark 5 Tjenestegrenesnitt versjon 1.0 for Noark 5.5.0 + http://people.skolelinux.org/pere/blog/Oppdatert_Noark_5_Tjenestegrenesnitt_versjon_1_0_for_Noark_5_5_0.html + http://people.skolelinux.org/pere/blog/Oppdatert_Noark_5_Tjenestegrenesnitt_versjon_1_0_for_Noark_5_5_0.html + Fri, 5 Jul 2019 17:20:00 +0200 + <p>Jeg er veldig glad for å kunne fortelle at i går ble ny versjon av +<a href="https://www.arkivverket.no/forvaltning-og-utvikling/noark-standarden/noark-5/tjenestegrensesnitt-noark5">API-spesifikasjonen +for Noark 5 Tjenestegrensesnitt</a> gitt ut. Det så lenge mørkt ut +for sjansene for å få inn nødvendige korreksjoner i +spesifikasjonsteksten innen rimelig tid, men takket være intens og god +innsats fra Mona og Anne Sofie hos Arkivverket de siste ukene, så ble +resultatet som ble gitt ut på USAs frigjøringsdag mye bedre enn jeg +fryktet.</p> + +<p>Spesifikasjonen er +<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">tilgjengelig +som markdown-filer i Arkivverkets github-prosjekt for dette</a>, og de +aller fleste av forslagene til forbedringer fra oss som holder på med +<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core">Nikita-prosjektet</a> +kom med i denne nye og oppdaterte spesifikasjonsteksten. Det er +fortsatt mye som gjenstår før den er entydig, klar og sikrer samvirke +på tvers av leverandører, men utgangspunktet er veldig mye bedre enn +forrige versjon fra 2016. Ta gjerne en titt.</p> + +<p>Ellers må jeg jo si at det var hyggelig å se at min forrige +bloggpost om tjenestegrensesnittet fikk en +<ahref="https://beta.arkivverket.no/post/186020592045/noark-5-versjon-50-tjenestegrensesnitt-10">lenke +fra Arkivverket Beta</a>.</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> - Idea for finding all public domain movies in the USA - http://people.skolelinux.org/pere/blog/Idea_for_finding_all_public_domain_movies_in_the_USA.html - http://people.skolelinux.org/pere/blog/Idea_for_finding_all_public_domain_movies_in_the_USA.html - Wed, 13 Dec 2017 10:15:00 +0100 - <p>While looking at -<a href="http://onlinebooks.library.upenn.edu/cce/">the scanned copies -for the copyright renewal entries for movies published in the USA</a>, -an idea occurred to me. The number of renewals are so few per year, it -should be fairly quick to transcribe them all and add references to -the corresponding IMDB title ID. This would give the (presumably) -complete list of movies published 28 years earlier that did _not_ -enter the public domain for the transcribed year. By fetching the -list of USA movies published 28 years earlier and subtract the movies -with renewals, we should be left with movies registered in IMDB that -are now in the public domain. For the year 1955 (which is the one I -have looked at the most), the total number of pages to transcribe is -21. For the 28 years from 1950 to 1978, it should be in the range -500-600 pages. It is just a few days of work, and spread among a -small group of people it should be doable in a few weeks of spare -time.</p> - -<p>A typical copyright renewal entry look like this (the first one -listed for 1955):</p> - -<p><blockquote> - ADAM AND EVIL, a photoplay in seven reels by Metro-Goldwyn-Mayer - Distribution Corp. (c) 17Aug27; L24293. Loew's Incorporated (PWH); - 10Jun55; R151558. -</blockquote></p> - -<p>The movie title as well as registration and renewal dates are easy -enough to locate by a program (split on first comma and look for -DDmmmYY). The rest of the text is not required to find the movie in -IMDB, but is useful to confirm the correct movie is found. I am not -quite sure what the L and R numbers mean, but suspect they are -reference numbers into the archive of the US Copyright Office.</p> - -<p>Tracking down the equivalent IMDB title ID is probably going to be -a manual task, but given the year it is fairly easy to search for the -movie title using for example -<a href="http://www.imdb.com/find?q=adam+and+evil+1927&s=all">http://www.imdb.com/find?q=adam+and+evil+1927&s=all</a>. -Using this search, I find that the equivalent IMDB title ID for the -first renewal entry from 1955 is -<a href="http://www.imdb.com/title/tt0017588/">http://www.imdb.com/title/tt0017588/</a>.</p> - -<p>I suspect the best way to do this would be to make a specialised -web service to make it easy for contributors to transcribe and track -down IMDB title IDs. In the web service, once a entry is transcribed, -the title and year could be extracted from the text, a search in IMDB -conducted for the user to pick the equivalent IMDB title ID right -away. By spreading out the work among volunteers, it would also be -possible to make at least two persons transcribe the same entries to -be able to discover any typos introduced. But I will need help to -make this happen, as I lack the spare time to do all of this on my -own. If you would like to help, please get in touch. Perhaps you can -draft a web service for crowd sourcing the task?</p> - -<p>Note, Project Gutenberg already have some -<a href="http://www.gutenberg.org/ebooks/search/?query=copyright+office+renewals">transcribed -copies of the US Copyright Office renewal protocols</a>, but I have -not been able to find any film renewals there, so I suspect they only -have copies of renewal for written works. I have not been able to find -any transcribed versions of movie renewals so far. Perhaps they exist -somewhere?</p> - -<p>I would love to figure out methods for finding all the public -domain works in other countries too, but it is a lot harder. At least -for Norway and Great Britain, such work involve tracking down the -people involved in making the movie and figuring out when they died. -It is hard enough to figure out who was part of making a movie, but I -do not know how to automate such procedure without a registry of every -person involved in making movies and their death year.</p> + Teach kids to protect their privacy - the EDRi way + http://people.skolelinux.org/pere/blog/Teach_kids_to_protect_their_privacy___the_EDRi_way.html + http://people.skolelinux.org/pere/blog/Teach_kids_to_protect_their_privacy___the_EDRi_way.html + Thu, 4 Jul 2019 19:10:00 +0200 + <p>Childs need to learn how to guard their privacy too. To help them, +<a href="https://edri.org/">European Digital Rights (EDRi)</a> created +a colorful booklet providing information on several privacy related topics, +and tips on how to protect ones privacy in the digital age.</p> + +<p>The 24 page booklet titled Digital Defenders is +<a href="https://edri.org/digital-defenders-help-kids-defend-their-privacy-around-europe">available +in several languages</a>. Thanks to the valuable contributions from +members of <a href="https://efn.no/">the Electronic Foundation Norway +(EFN)</a> and others, it is also available in Norwegian Bokmål. +If you would like to have it available in your language too, +<a href="https://hosted.weblate.org/projects/efn/privacy4kids/">contribute +via Weblate</a> and get in touch.</p> + +<p>But a funny, well written and good looking PDF do not have much +impact, unless it is read by the right audience. To increase the +chance of kids reading it, I am currently assisting EFN in getting +copies printed on paper to distribute on the street and in class +rooms. Print the booklet was made possible thanks to a small et of +great sponsors. Thank you very much to each and every one of them! I +hope to have the printed booklet ready to hand out on Tuesday, when +<a href="https://www.nuug.no/>">the Norwegian Unix Users Group</a> is +organizing <a href="https://wiki.nuug.no/sommerfest2019">its yearly +barbecue for geeks and free software zealots in the Oslo area</a>. If +you are nearby, feel free to come by and check out the party and the +booklet.</p> + +<p>If the booklet prove to be a success, it would be great to get +more sponsoring and distribute it to every kid in the country. :)</p> <p>As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address @@ -125,161 +85,289 @@ activities, please send Bitcoin donations to my address - Is the short movie «Empty Socks» from 1927 in the public domain or not? - http://people.skolelinux.org/pere/blog/Is_the_short_movie__Empty_Socks__from_1927_in_the_public_domain_or_not_.html - http://people.skolelinux.org/pere/blog/Is_the_short_movie__Empty_Socks__from_1927_in_the_public_domain_or_not_.html - Tue, 5 Dec 2017 12:30:00 +0100 - <p>Three years ago, a presumed lost animation film, -<a href="https://en.wikipedia.org/wiki/Empty_Socks">Empty Socks from -1927</a>, was discovered in the Norwegian National Library. At the -time it was discovered, it was generally assumed to be copyrighted by -The Walt Disney Company, and I blogged about -<a href="http://people.skolelinux.org/pere/blog/Opphavsretts_status_for__Empty_Socks__fra_1927_.html">my -reasoning to conclude</a> that it would would enter the Norwegian -equivalent of the public domain in 2053, based on my understanding of -Norwegian Copyright Law. But a few days ago, I came across -<a href="http://www.toonzone.net/forums/threads/exposed-disneys-repurchase-of-oswald-the-rabbit-a-sham.4792291/">a -blog post claiming the movie was already in the public domain</a>, at -least in USA. The reasoning is as follows: The film was released in -November or Desember 1927 (sources disagree), and presumably -registered its copyright that year. At that time, right holders of -movies registered by the copyright office received government -protection for there work for 28 years. After 28 years, the copyright -had to be renewed if the wanted the government to protect it further. -The blog post I found claim such renewal did not happen for this -movie, and thus it entered the public domain in 1956. Yet someone -claim the copyright was renewed and the movie is still copyright -protected. Can anyone help me to figure out which claim is correct? -I have not been able to find Empty Socks in Catalog of copyright -entries. Ser.3 pt.12-13 v.9-12 1955-1958 Motion Pictures -<a href="http://onlinebooks.library.upenn.edu/cce/1955r.html#film">available -from the University of Pennsylvania</a>, neither in -<a href="https://babel.hathitrust.org/cgi/pt?id=mdp.39015084451130;page=root;view=image;size=100;seq=83;num=45">page -45 for the first half of 1955</a>, nor in -<a href="https://babel.hathitrust.org/cgi/pt?id=mdp.39015084451130;page=root;view=image;size=100;seq=175;num=119">page -119 for the second half of 1955</a>. It is of course possible that -the renewal entry was left out of the printed catalog by mistake. Is -there some way to rule out this possibility? Please help, and update -the wikipedia page with your findings. + Nikita og Noark 5 tjenestegrensesnittet tilbyr ny måte å tenke arkivering + http://people.skolelinux.org/pere/blog/Nikita_og_Noark_5_tjenestegrensesnittet_tilbyr_ny_m_te___tenke_arkivering.html + http://people.skolelinux.org/pere/blog/Nikita_og_Noark_5_tjenestegrensesnittet_tilbyr_ny_m_te___tenke_arkivering.html + Fri, 21 Jun 2019 11:30:00 +0200 + <p><em>av Thomas Sødring (OsloMet) og Petter Reinholdtsen (foreningen +NUUG)</em></p> + +<p>Nikita Noark 5-kjerne er et fri programvareprosjekt som tar i bruk +Arkivverkets spesifikasjonen for Noark 5 Tjenestegrensesnitt og tilbyr +et maskinlesbart grensesnitt (arkiv-API) til datasystemer som trenger å +arkivere dokumenter og informasjon. I tillegg tilbyr Nikita et +nettleserbasert brukergrensesnitt for brukere av arkivet. Dette +brukergrensesnittet benytter det maskinlesbare grensesnittet. Noark 5 +Tjenestegrensesnitt er en ny måte å tenke arkivering, med fokus på +automatisering og maskinell behandling av arkivmateriale, i stedet for +å fokusere på brukergrensesnitt. En kan tenke på +tjenestegrensesnittet som arkivet uten brukergrensesnitt, der flere +aktører kan koble til ulike brukergrensesnitt, tilpasset ulike +behov.</p> + +<p>Historisk sett gjorde Noark standarden en veldig bra jobb med +overgangen fra +papir til digital saksbehandling, men det har kommet til kort på andre +områder. Den teknologiske utviklingen har brakt oss ditt at vi kan og +skal forvente langt mer fra en arkivkjerne enn før, men det offentlig +er ofte konservativ når det gjelder nytenking. For lengst skulle +begreper som samvirke mellom datasystemer, metadata, prosess og +tjenestegrensesnitt (API) vært dominerende når systemer kjøpes +inn. Dessverre er det slik at ikke alle ønsker samvirke mellom +datasystemer velkommen, og det kan være trygt å kjøpe «svarte bokser» +der du slipper å ta stilling til hvordan man skal få flere systemer +til å virke sammen. Men IT-arkitektur er et begrep arkivfolk også +begynner å ta inn over seg.</p> + +<p>Slike systemer for å organisere metadata bør ha nettbaserte +tjenestegrensesnitt der brukergrensesnitt er tydelig adskilt fra +bakenforliggende system. Det finnes mange rapporter som snakker om å +bryte ned siloer i forvaltningen og standardiserte tjenestegrensesnitt +er det viktigste virkemiddel mot datasiloer og legger til rette for +økt samvirke mellom systemer. Et standardisert tjenestegrensesnitt er +et viktig middel for å få systemer til å samhandle da det sikrer at +ulike produsenters systemer kan snakke sammen på tvers. Samfunnet +fungerer ikke uten standardisering. Vi har alle samme strømstyrke og +kontakter i veggene og kjører alle på høyre side av veien i Norge. Det er i en slik +sammenheng at prosjektet «Noark 5 Tjenestegrensesnitt» er veldig +viktig. Hvis alle leverandører av arkivsystemer forholdt seg til et +standardisert tjenestegrensesnitt kunne kostnadene for arkivering +reduseres. Tenk deg at du er en kommune som ønsker et fagsystem integrert +med arkivløsningen din. I dag må fagsystemleverandøren vite og +tilpasse seg den spesifikke versjonen og varianten av arkivløsningen +du har. Hvis vi antar at alle leverandører av arkivkjerner har solgt +inn enten SOAP eller REST-grensesnitt til kunder de siste 10 årene og +det kommer endret versjon av grensesnittet innimellom, så gir det +veldig mange forskjellige tjenestegrensesnitt en fagsystemleverandør +må forholde seg til. Med 12 leverandører og kvartalsvise oppdateringer +kan det potensielt bli 96 ulike varianter hvert eneste år. Det sier +seg selv at det blir dyrt. Men det blir faktisk verre. Hvis du senere +ønsker å bytte ut arkivsystemet med et annet så er du avhengig å få +alle integrasjonene dine laget på nytt. Dette kan gjøre at du velger å +forbli hos en dårlig leverandør framfor å skaffe nytt system, fordi +det blir for vanskelig og dyrt å bytte. Dermed etableres det «små» +monopolsituasjoner som er vanskelig å bryte ut av. Dårlige valg i dag +kan ha uante kostander på sikt. I Nikita-prosjektet har vi kun jobbet +opp mot Noark 5 Tjenestegrensesnittet. Det har tatt en god del +ressurser å sette seg inn i spesifikasjonen og ta den i bruk, spesielt +på grunn av uklarheter i spesifikasjonen. Hvis vi måtte gjøre det +samme for alle versjoner og varianter av de forskjellige +tjenestegrensesnittene ville det blitt veldig tidkrevende og +kostbart.</p> + +<p>For deg som arkivar er digitalisering og systemer som skal virke +sammen en del av den nye hverdagen. Du har kanskje blitt skånet for +det ved å kjøpe svarte bokser, men du risikerer at du gjør deg selv en +bjørnetjeneste. Det kan oppleves som kjedelig å fortelle kolleger at +du skal sette deg inn i et tjenestegrensesnitt, men dette er faktisk +veldig spennende. Tjenestegrensesnittet er på en måte blitt levende og +det er spesielt et begrep du bør merke deg: OData. Å trekke inn deler +av OData-standarden som en måte å filtrere entitetsøk i et arkivsystem +var et nyttig trekk i prosjektet. Følgende eksempel er en +OData-spørring det går an å sende inn til en standardisert +arkivkjerne:</p> -<p>As usual, if you use Bitcoin and want to show your support of my -activities, please send Bitcoin donations to my address +<p><blockquote> +.../sakarkiv/journalpost?filter=contains(tittel, 'nabovarsel') +</blockquote></p> + +<p>Spørringen over vil hente en liste av alle dine journalposter der +tittelen til journalposten inneholder ordet 'nabovarsel'. Alle +leverandører som implementerer tjenestegrensesnittet vil måtte tilby +dette. Det betyr at hvis du lærer dette språket for et system, vil det +være gjeldende for alle. Dette er egentlig en ny måte å søke i +arkivdatabasen på og vil være svært nyttig, for eksempel kan søk i +tjenestegrensesnittet antagelig brukes til å hente ut offentlig +postjournal. I arkivverden pleier vi å like teknologier som er +menneskelesbart, da vet vi det er enkelt og nyttig! OData er også +viktig fordi det kan bli en ny måte å svare innsynsforespørsler på i +tråd med offentlighetsloven § 9, der retten til å kreve innsyn i +sammenstilling fra databaser er nedfelt. I dag ser vi +forvaltningsorganer som avviser slike krav fordi det «ikke kan gjøres +med enkle framgangsmåter». Bruken av OData i tjenestegrensesnittet, +sammen med maskinlesbar markeringsformater kan være et viktig bidrag +til å åpne arkivene i tråd med prinsippene om en åpen og transparent +forvaltning.</p> + +<p>Standardisering er viktig fordi det <em>kan</em> sikre samvirke. +Men den effekten kommer kun hvis standardiseringen sikrer at alle +forstår standarden på samme måte, dvs. at den er entydig og klar. En +god måte å sikre en entydig og klar spesifikasjon er ved å kreve at +det finnes minst to ulike implementasjoner som følger spesifikasjonen +og som kan snakke sammen, det vil si at de snakker samme språk, slik +IETF krever for alle sine standarder, før spesifikasjonen anses å være +ferdig. Tilbakemelding fra miljøet forteller at både leverandører og +kunder har et avslappet forhold til Noark 5 Tjenestegrensesnitt og det +er så langt kun Evry som har visst offentlig at de har en +implementasjon av tjenestegrensesnittet. Evry, HK Data og Fredrikstad +kommune er igang med et pilotprosjekt på Noark 5 +Tjenestegrensesnitt. For å redusere kostnadene for samvirkende +datasystemer betraktelig, er det veldig viktig at vi kommer i en +situasjon der alle leverandører har sine egne implementasjoner av +tjenestegrensesnittet, og at disse oppfører seg likt og i tråd med det +som er beskrevet i spesifikasjonen.</p> + +<p>Det er her fri programvare spiller en viktig rolle. Med en uklar +standard blir det som en polsk riksdag, der ingenting fungerer. Nikita +er en fri programvareimplementasjon av tjenestegrensesnitt og kan +fungere som teknisk referanse slik at leverandører enklere kan se og +forstå hvordan standarden skal tolkes. Vi har i Nikitaprosjektet +erfart å ende opp med vidt forskjellige tolkninger når +prosjektmedlemmene leser spesifikasjonsteksten, en effekt av en uklar +spesifikasjon. Men Nikitaprosjektet har også utviklet et test-program +som sjekker om et tjenestegrensesnitt er i samsvar med standarden, og +prosjektet bruker det hele tiden for å sikre at endringer og +forbedringer fungerer. Egenerklæringsskjemaenes dager kan være talte! +Snart vil du selv kunne teste hver oppdatering av arkivsystemet med en +uavhengig sjekk.</p> + +<p>Fri programvare representerer en demokratisering av kunnskap der +tolkning- og innlåsingsmakt flyttes fra leverandør til allmenheten. +Med fri programvare har du en litt annerledes verdikjede, der selve +produktet ikke holdes hemmelig for å tjene penger, slik en gjør med +ufri programvare og skytjenester som ikke bruker fri programvare, men +du kan tjene penger på andre deler av verdikjeden. Med fri programvare +kan samfunnet betale for å videreutvikle nyttig +fellesfunksjonalitet.</p> + +<p>Nikita er en fri programvareimplementasjon av tjenestegrensesnittet og +kan fungere som en referanseimplementasjon dersom det er ønskelig. +Alle har lik tilgang til koden og det koster ingenting å ta den i bruk +og utforske det. Nikitaprosjektet ønsker tjenestegrensesnittet +velkommen og stiller veldig gjerne opp i diskusjoner om tolkning av +tjenestegrensesnittet. Nikita er bygget på moderne +programmeringsrammeverk og utviklet i full åpenhet. Men Nikita er ikke +noe du kan kjøpe. Nikita er først og fremst et verktøy for forsking og +utvikling laget for å fremme forskning på arkivfeltet. Systemer som +virker sammen har alltid vært hovedfokus og vil være det fremover. +Det brukes som undervisningsverktøy der studentene ved OsloMet lærer +om administrativt oppsett, saksbehandling, uttrekk og samvirkende +datasystemer. Det brukes også som forskningsobjekt der vi ser på +import av dokumentsamlinger, bruk av blokkjede og andre nyskapende +måter å tenke arkiv på. Det er dog helt greit om andre tar Nikita og +pakker det for å selge det som produkt. Forvaltningsorganer med +sterke drift- og utviklingsmiljøer kan også se på Nikita og utforske +hva som er mulig. Dette kan de gjøre uten å måtte betale for +bruksrettigheter eller tilgang til konsulenter. Men arkivering blir +ikke gratis på grunn av Nikita. Det trengs fortsatt folk med +kompetanse og tid til å ta i bruk Nikita.</p> + +<p>Nikita har nylig kommet med en ny utgave, den sjette i rekken. +Systemet er ikke ferdig, mest på grunn av at API-spesifikasjonen for +Noark 5 Tjenestegrensesnitt ikke er ferdig, men allerede i dag kan en +bruke Nikita som arkiv. Vi har laget eksempelsystem for å importere +data fra deponi-XML og slik gjøre eksisterende arkivdata tilgjengelig +via et API. Vi har også laget en testklient som importerer epost inn +i arkivet med vedlegg der epostenes trådinformasjon brukes til å legge +eposttråder i samme arkivmappe, og en annen testklient som henter +epost ut av en arkivmappe på mbox-format slik at en vanlig epostklient +kan brukes til å lese igjennom og svare på epostene i en +arkivmappe. De som vil ta en titt på Nikita kan besøke +<a href="https://nikita.oslomet.no">https://nikita.oslomet.no</a> og +logge inn med brukernavn «admin@example.com» og passord «password». +Dette gir tilgang til det forenklede brukergrensesnittet som brukes +til undervisning. De som heller vil ta en titt under panseret kan +besøke +<a href="https://nikita.oslomet.no/browse.html">https://nikita.oslomet.no/browse.html</a> +og der se hvordan API-et fungerer mer i detalj. Innloggingsdetaljer +her er det samme som for brukergrensesnittet.</p> + +<p>Fremover er fokuset på forbedring av spesifikasjonen Noark 5 +Tjenestegrensesnitt. De som skrev tjenestegrensesnittet gjorde et +interessant og framtidsrettet grep, de skilte sak fra arkiv. +Tjenestegrensesnittet består av flere "pakker", der noen er +grunnleggende mens andre bygger på de grunnleggende pakkene. Pakkene +som er beskrevet så langt heter «arkivstruktur», «sakarkiv», +«administrasjon», «loggogsporing» og «moeter» (dessverre +<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/pull/120">planlagt +fjernet</a> i første utgave). Etter hvert håper vi å utforske +prosses- og metadatabeskrivelser til flere fagområder og bidra til at +tjenestegrensesnittet kan legge til flere pakker som «byggarkiv», +«barnevern», «personal», «barnehage», der arkivfaglig metadata- og +dokumentasjonsbehov er kartlagt og standardisert.</p> + +<p>Nikita utvikles av en liten prosjektgruppe, og vi er alltid +interessert å bli flere. Hvis en åpen, fri og standardisert tilnærming +til arkivering høres interessant ut, bli med oss på veien videre. Vi +er tilstede på IRC-kanalen #nikita hos FreeNode (tilgjengelig via +nettleser på +<a href="https://webchat.freenode.net?channels=#nikita">https://webchat.freenode.net?channels=#nikita</a>), +og har en e-postliste nikita-noark@nuug.no hos NUUG (tilgjengelig for +påmelding og arkiv på +<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">https://lists.nuug.no/mailman/listinfo/nikita-noark</a>) +der en kan følge med eller være med oss på den spennende veien videre. +Spesifikasjonen for Noark 5 Tjenestegrensesnitt vedlikeholdes på +github, +<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/</a>.</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>.</p> - Metadata proposal for movies on the Internet Archive - http://people.skolelinux.org/pere/blog/Metadata_proposal_for_movies_on_the_Internet_Archive.html - http://people.skolelinux.org/pere/blog/Metadata_proposal_for_movies_on_the_Internet_Archive.html - Tue, 28 Nov 2017 12:00:00 +0100 - <p>It would be easier to locate the movie you want to watch in -<a href="https://www.archive.org/">the Internet Archive</a>, if the -metadata about each movie was more complete and accurate. In the -archiving community, a well known saying state that good metadata is a -love letter to the future. The metadata in the Internet Archive could -use a face lift for the future to love us back. Here is a proposal -for a small improvement that would make the metadata more useful -today. I've been unable to find any document describing the various -standard fields available when uploading videos to the archive, so -this proposal is based on my best quess and searching through several -of the existing movies.</p> - -<p>I have a few use cases in mind. First of all, I would like to be -able to count the number of distinct movies in the Internet Archive, -without duplicates. I would further like to identify the IMDB title -ID of the movies in the Internet Archive, to be able to look up a IMDB -title ID and know if I can fetch the video from there and share it -with my friends.</p> - -<p>Second, I would like the Butter data provider for The Internet -archive -(<a href="https://github.com/butterproviders/butter-provider-archive">available -from github</a>), to list as many of the good movies as possible. The -plugin currently do a search in the archive with the following -parameters:</p> - -<p><pre> -collection:moviesandfilms -AND NOT collection:movie_trailers -AND -mediatype:collection -AND format:"Archive BitTorrent" -AND year -</pre></p> - -<p>Most of the cool movies that fail to show up in Butter do so -because the 'year' field is missing. The 'year' field is populated by -the year part from the 'date' field, and should be when the movie was -released (date or year). Two such examples are -<a href="https://archive.org/details/SidneyOlcottsBen-hur1905">Ben Hur -from 1905</a> and -<a href="https://archive.org/details/Caminandes2GranDillama">Caminandes -2: Gran Dillama from 2013</a>, where the year metadata field is -missing.</p> - -So, my proposal is simply, for every movie in The Internet Archive -where an IMDB title ID exist, please fill in these metadata fields -(note, they can be updated also long after the video was uploaded, but -as far as I can tell, only by the uploader): - -<dl> - -<dt>mediatype</dt> -<dd>Should be 'movie' for movies.</dd> - -<dt>collection</dt> -<dd>Should contain 'moviesandfilms'.</dd> - -<dt>title</dt> -<dd>The title of the movie, without the publication year.</dd> - -<dt>date</dt> -<dd>The data or year the movie was released. This make the movie show -up in Butter, as well as make it possible to know the age of the -movie and is useful to figure out copyright status.</dd> - -<dt>director</dt> -<dd>The director of the movie. This make it easier to know if the -correct movie is found in movie databases.</dd> - -<dt>publisher</dt> -<dd>The production company making the movie. Also useful for -identifying the correct movie.</dd> - -<dt>links</dt> - -<dd>Add a link to the IMDB title page, for example like this: &lt;a -href="http://www.imdb.com/title/tt0028496/"&gt;Movie in -IMDB&lt;/a&gt;. This make it easier to find duplicates and allow for -counting of number of unique movies in the Archive. Other external -references, like to TMDB, could be added like this too.</dd> - -</dl> - -<p>I did consider proposing a Custom field for the IMDB title ID (for -example 'imdb_title_url', 'imdb_code' or simply 'imdb', but suspect it -will be easier to simply place it in the links free text field.</p> - -<p>I created -<a href="https://github.com/petterreinholdtsen/public-domain-free-imdb">a -list of IMDB title IDs for several thousand movies in the Internet -Archive</a>, but I also got a list of several thousand movies without -such IMDB title ID (and quite a few duplicates). It would be great if -this data set could be integrated into the Internet Archive metadata -to be available for everyone in the future, but with the current -policy of leaving metadata editing to the uploaders, it will take a -while before this happen. If you have uploaded movies into the -Internet Archive, you can help. Please consider following my proposal -above for your movies, to ensure that movie is properly -counted. :)</p> - -<p>The list is mostly generated using wikidata, which based on -Wikipedia articles make it possible to link between IMDB and movies in -the Internet Archive. But there are lots of movies without a -Wikipedia article, and some movies where only a collection page exist -(like for <a href="https://en.wikipedia.org/wiki/Caminandes">the -Caminandes example above</a>, where there are three movies but only -one Wikidata entry).</p> + Jami/Ring, finally functioning peer to peer communication client + http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html + http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html + Wed, 19 Jun 2019 08:50:00 +0200 + <p>Some years ago, in 2016, I +<a href="http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html">wrote +for the first time about</a> the Ring peer to peer messaging system. +It would provide messaging without any central server coordinating the +system and without requiring all users to register a phone number or +own a mobile phone. Back then, I could not get it to work, and put it +aside until it had seen more development. A few days ago I decided to +give it another try, and am happy to report that this time I am able +to not only send and receive messages, but also place audio and video +calls. But only if UDP is not blocked into your network.</p> + +<p>The Ring system changed name earlier this year to +<a href="https://en.wikipedia.org/wiki/Jami_(software)">Jami</a>. I +tried doing web search for 'ring' when I discovered it for the first +time, and can only applaud this change as it is impossible to find +something called Ring among the noise of other uses of that word. Now +you can search for 'jami' and this client and +<a href="https://jami.net/">the Jami system</a> is the first hit at +least on duckduckgo.</p> + +<p>Jami will by default encrypt messages as well as audio and video +calls, and try to send them directly between the communicating parties +if possible. If this proves impossible (for example if both ends are +behind NAT), it will use a central SIP TURN server maintained by the +Jami project. Jami can also be a normal SIP client. If the SIP +server is unencrypted, the audio and video calls will also be +unencrypted. This is as far as I know the only case where Jami will +do anything without encryption.</p> + +<p>Jami is available for several platforms: Linux, Windows, MacOSX, +Android, iOS, and Android TV. It is included in Debian already. Jami +also work for those using F-Droid without any Google connections, +while Signal do not. +<a href="https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol">The +protocol</a> is described in the Ring project wiki. The system uses a +distributed hash table (DHT) system (similar to BitTorrent) running +over UDP. On one of the networks I use, I discovered Jami failed to +work. I tracked this down to the fact that incoming UDP packages +going to ports 1-49999 were blocked, and the DHT would pick a random +port and end up in the low range most of the time. After talking to +the developers, I solved this by enabling the dhtproxy in the +settings, thus using TCP to talk to a central DHT proxy instead of + +peering directly with others. I've been told the developers are +working on allowing DHT to use TCP to avoid this problem. I also ran +into a problem when trying to talk to the version of Ring included in +Debian Stable (Stretch). Apparently the protocol changed between +beta2 and the current version, making these clients incompatible. +Hopefully the protocol will not be made incompatible in the +future.</p> + +<p>It is worth noting that while looking at Jami and its features, I +came across another communication platform I have not tested yet. The +<a href="https://en.wikipedia.org/wiki/Tox_(protocol)">Tox protocol</a> +and <a href="https://tox.chat/">family of Tox clients</a>. It might +become the topic of a future blog post.</p> <p>As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address @@ -288,151 +376,116 @@ activities, please send Bitcoin donations to my address - Legal to share more than 3000 movies listed on IMDB? - http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_3000_movies_listed_on_IMDB_.html - http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_3000_movies_listed_on_IMDB_.html - Sat, 18 Nov 2017 21:20:00 +0100 - <p>A month ago, I blogged about my work to -<a href="http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html">automatically -check the copyright status of IMDB entries</a>, and try to count the -number of movies listed in IMDB that is legal to distribute on the -Internet. I have continued to look for good data sources, and -identified a few more. The code used to extract information from -various data sources is available in -<a href="https://github.com/petterreinholdtsen/public-domain-free-imdb">a -git repository</a>, currently available from github.</p> - -<p>So far I have identified 3186 unique IMDB title IDs. To gain -better understanding of the structure of the data set, I created a -histogram of the year associated with each movie (typically release -year). It is interesting to notice where the peaks and dips in the -graph are located. I wonder why they are placed there. I suspect -World War II caused the dip around 1940, but what caused the peak -around 2010?</p> - -<p align="center"><img src="http://people.skolelinux.org/pere/blog/images/2017-11-18-verk-i-det-fri-filmer.png" /></p> - -<p>I've so far identified ten sources for IMDB title IDs for movies in -the public domain or with a free license. This is the statistics -reported when running 'make stats' in the git repository:</p> - -<pre> - 249 entries ( 6 unique) with and 288 without IMDB title ID in free-movies-archive-org-butter.json - 2301 entries ( 540 unique) with and 0 without IMDB title ID in free-movies-archive-org-wikidata.json - 830 entries ( 29 unique) with and 0 without IMDB title ID in free-movies-icheckmovies-archive-mochard.json - 2109 entries ( 377 unique) with and 0 without IMDB title ID in free-movies-imdb-pd.json - 291 entries ( 122 unique) with and 0 without IMDB title ID in free-movies-letterboxd-pd.json - 144 entries ( 135 unique) with and 0 without IMDB title ID in free-movies-manual.json - 350 entries ( 1 unique) with and 801 without IMDB title ID in free-movies-publicdomainmovies.json - 4 entries ( 0 unique) with and 124 without IMDB title ID in free-movies-publicdomainreview.json - 698 entries ( 119 unique) with and 118 without IMDB title ID in free-movies-publicdomaintorrents.json - 8 entries ( 8 unique) with and 196 without IMDB title ID in free-movies-vodo.json - 3186 unique IMDB title IDs in total -</pre> - -<p>The entries without IMDB title ID are candidates to increase the -data set, but might equally well be duplicates of entries already -listed with IMDB title ID in one of the other sources, or represent -movies that lack a IMDB title ID. I've seen examples of all these -situations when peeking at the entries without IMDB title ID. Based -on these data sources, the lower bound for movies listed in IMDB that -are legal to distribute on the Internet is between 3186 and 4713. - -<p>It would be great for improving the accuracy of this measurement, -if the various sources added IMDB title ID to their metadata. I have -tried to reach the people behind the various sources to ask if they -are interested in doing this, without any replies so far. Perhaps you -can help me get in touch with the people behind VODO, Public Domain -Torrents, Public Domain Movies and Public Domain Review to try to -convince them to add more metadata to their movie entries?</p> - -<p>Another way you could help is by adding pages to Wikipedia about -movies that are legal to distribute on the Internet. If such page -exist and include a link to both IMDB and The Internet Archive, the -script used to generate free-movies-archive-org-wikidata.json should -pick up the mapping as soon as wikidata is updates.</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> + More sales number for my Free Culture paper editions (2019-edition) + http://people.skolelinux.org/pere/blog/More_sales_number_for_my_Free_Culture_paper_editions__2019_edition_.html + http://people.skolelinux.org/pere/blog/More_sales_number_for_my_Free_Culture_paper_editions__2019_edition_.html + Tue, 11 Jun 2019 16:05:00 +0200 + <p>The first book I published, +<a href="http://www.free-culture.cc/">Free Culture by Lawrence +Lessig</a>, is still selling a few copies. Not a lot, but enough to +have contributed slightly over $500 to the <a +href="https://creativecommons.org/">Creative Commons Corporation</a> +so far. All the profit is sent there. Most books are still sold via +Amazon (83 copies), with Ingram second (49) and Lulu (12) and Machette (7) as +minor channels. Bying directly from Lulu bring the largest cut to +Creative Commons. The English Edition sold 80 copies so far, the +French 59 copies, and Norwegian only 8 copies. Nothing impressive, +but nice to see the work we put down is still being appreciated. The +ebook edition is available for free from +<a href="https://github.com/petterreinholdtsen/free-culture-lessig">Github</a>.</p> + +<table border="0"> +<tr><th rowspan="2" valign="bottom">Title / language</th> +<th colspan="7">Quantity</th></tr> +<tr> +<th>2016 jan-jun</th> +<th>2016 jul-dec</th> +<th>2017 jan-jun</th> +<th>2017 jul-dec</th> +<th>2018 jan-jun</th> +<th>2018 jul-dec</th> +<th>2019 jan-may</th> +</tr> + +<tr> + <td><a href="http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html">Culture Libre / French</a></td> + <td align="right">3</td> + <td align="right">6</td> + <td align="right">19</td> + <td align="right">11</td> + <td align="right">7</td> + <td align="right">6</td> + <td align="right">7</td> +</tr> + +<tr> + <td><a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Fri kultur / Norwegian</a></td> + <td align="right">7</td> + <td align="right">1</td> + <td align="right">0</td> + <td align="right">0</td> + <td align="right">0</td> + <td align="right">0</td> + <td align="right">0</td> +</tr> + +<tr> + <td><a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html">Free Culture / English</a></td> + <td align="right">14</td> + <td align="right">27</td> + <td align="right">16</td> + <td align="right">9</td> + <td align="right">3</td> + <td align="right">7</td> + <td align="right">3</td> +</tr> + +<tr> + <td>Total</td> + <td align="right">24</td> + <td align="right">34</td> + <td align="right">35</td> + <td align="right">20</td> + <td align="right">10</td> + <td align="right">13</td> + <td align="right">10</td> +</tr> + +</table> + +<p>It is fun to see the French edition being more popular than the +English one.</p> + +<p>If you would like to translate and publish the book in your native +language, I would be happy to help make it happen. Please get in +touch.</p> - Some notes on fault tolerant storage systems - http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html - http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html - Wed, 1 Nov 2017 15:35:00 +0100 - <p>If you care about how fault tolerant your storage is, you might -find these articles and papers interesting. They have formed how I -think of when designing a storage system.</p> - -<ul> - -<li>USENIX :login; <a -href="https://www.usenix.org/publications/login/summer2017/ganesan">Redundancy -Does Not Imply Fault Tolerance. Analysis of Distributed Storage -Reactions to Single Errors and Corruptions</a> by Aishwarya Ganesan, -Ramnatthan Alagappan, Andrea C. Arpaci-Dusseau, and Remzi -H. Arpaci-Dusseau</li> - -<li>ZDNet -<a href="http://www.zdnet.com/article/why-raid-5-stops-working-in-2009/">Why -RAID 5 stops working in 2009</a> by Robin Harris</li> - -<li>ZDNet -<a href="http://www.zdnet.com/article/why-raid-6-stops-working-in-2019/">Why -RAID 6 stops working in 2019</a> by Robin Harris</li> - -<li>USENIX FAST'07 -<a href="http://research.google.com/archive/disk_failures.pdf">Failure -Trends in a Large Disk Drive Population</a> by Eduardo Pinheiro, -Wolf-Dietrich Weber and Luiz André Barroso</li> - -<li>USENIX ;login: <a -href="https://www.usenix.org/system/files/login/articles/hughes12-04.pdf">Data -Integrity. Finding Truth in a World of Guesses and Lies</a> by Doug -Hughes</li> - -<li>USENIX FAST'08 -<a href="https://www.usenix.org/events/fast08/tech/full_papers/bairavasundaram/bairavasundaram_html/">An -Analysis of Data Corruption in the Storage Stack</a> by -L. N. Bairavasundaram, G. R. Goodson, B. Schroeder, A. C. -Arpaci-Dusseau, and R. H. Arpaci-Dusseau</li> - -<li>USENIX FAST'07 <a -href="https://www.usenix.org/legacy/events/fast07/tech/schroeder/schroeder_html/">Disk -failures in the real world: what does an MTTF of 1,000,000 hours mean -to you?</a> by B. Schroeder and G. A. Gibson.</li> - -<li>USENIX ;login: <a -href="https://www.usenix.org/events/fast08/tech/full_papers/jiang/jiang_html/">Are -Disks the Dominant Contributor for Storage Failures? A Comprehensive -Study of Storage Subsystem Failure Characteristics</a> by Weihang -Jiang, Chongfeng Hu, Yuanyuan Zhou, and Arkady Kanevsky</li> - -<li>SIGMETRICS 2007 -<a href="http://research.cs.wisc.edu/adsl/Publications/latent-sigmetrics07.pdf">An -analysis of latent sector errors in disk drives</a> by -L. N. Bairavasundaram, G. R. Goodson, S. Pasupathy, and J. Schindler</li> - -</ul> - -<p>Several of these research papers are based on data collected from -hundred thousands or millions of disk, and their findings are eye -opening. The short story is simply do not implicitly trust RAID or -redundant storage systems. Details matter. And unfortunately there -are few options on Linux addressing all the identified issues. Both -ZFS and Btrfs are doing a fairly good job, but have legal and -practical issues on their own. I wonder how cluster file systems like -Ceph do in this regard. After all, there is an old saying, you know -you have a distributed system when the crash of a computer you have -never heard of stops you from getting any work done. The same holds -true if fault tolerance do not work.</p> - -<p>Just remember, in the end, it do not matter how redundant, or how -fault tolerant your storage is, if you do not continuously monitor its -status to detect and replace failed disks.</p> + Official MIME type "text/vnd.sosi" for SOSI map data + http://people.skolelinux.org/pere/blog/Official_MIME_type__text_vnd_sosi__for_SOSI_map_data.html + http://people.skolelinux.org/pere/blog/Official_MIME_type__text_vnd_sosi__for_SOSI_map_data.html + Tue, 4 Jun 2019 09:20:00 +0200 + <p>Just 15 days ago, +<ahref="http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html">I +mentioned</a> my submission to IANA to register an official MIME type +for the SOSI vector map format. This morning, just an hour ago, I was +notified that +<a href="https://www.iana.org/assignments/media-types/text/vnd.sosi">the +MIME type "text/vnd.sosi"</a> is registered for this format. In +addition to this registration, my +<a href="https://github.com/file/file/blob/master/magic/Magdir/sosi">file(1) +patch for a pattern matching rule for SOSI files</a> has been accepted +into the official source of that program (pending a new release), and +I've been told by the team behind +<a href="https://www.nationalarchives.gov.uk/PRONOM/">PRONOM</a> that +the SOSI format will be included in the next release of PRONOM, which +they plan to release this summer around July.</p> + +<p>I am very happy to see all of this fall into place, for use by +<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">the +Noark 5 Tjenestegrensesnitt</a> implementations.</p> <p>As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address @@ -441,42 +494,69 @@ activities, please send Bitcoin donations to my address - Web services for writing academic LaTeX papers as a team - http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html - http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html - Tue, 31 Oct 2017 21:00:00 +0100 - <p>I was surprised today to learn that a friend in academia did not -know there are easily available web services available for writing -LaTeX documents as a team. I thought it was common knowledge, but to -make sure at least my readers are aware of it, I would like to mention -these useful services for writing LaTeX documents. Some of them even -provide a WYSIWYG editor to ease writing even further.</p> - -<p>There are two commercial services available, -<a href="https://sharelatex.com">ShareLaTeX</a> and -<a href="https://overleaf.com">Overleaf</a>. They are very easy to -use. Just start a new document, select which publisher to write for -(ie which LaTeX style to use), and start writing. Note, these two -have announced their intention to join forces, so soon it will only be -one joint service. I've used both for different documents, and they -work just fine. While -<a href="https://github.com/sharelatex/sharelatex">ShareLaTeX is free -software</a>, while the latter is not. According to <a -href="https://www.overleaf.com/help/17-is-overleaf-open-source">a -announcement from Overleaf</a>, they plan to keep the ShareLaTeX code -base maintained as free software.</p> - -But these two are not the only alternatives. -<a href="https://app.fiduswriter.org/">Fidus Writer</a> is another free -software solution with <a href="https://github.com/fiduswriter">the -source available on github</a>. I have not used it myself. Several -others can be found on the nice -<a href="https://alternativeto.net/software/sharelatex/">alterntiveTo -web service</a>. - -<p>If you like Google Docs or Etherpad, but would like to write -documents in LaTeX, you should check out these services. You can even -host your own, if you want to. :)</p> + The space rover coquine, or how I ended up on the dark side of the moon + http://people.skolelinux.org/pere/blog/The_space_rover_coquine__or_how_I_ended_up_on_the_dark_side_of_the_moon.html + http://people.skolelinux.org/pere/blog/The_space_rover_coquine__or_how_I_ended_up_on_the_dark_side_of_the_moon.html + Sun, 2 Jun 2019 23:55:00 +0200 + <p>A while back a college and friend from Debian and the Skolelinux / +Debian Edu project approached me, asking if I knew someone that might +be interested in helping out with a technology project he was running +as a teacher at <a href="https://www.ecolefrancodanoise.dk/">L'école +franco-danoise</a> - the Danish-French school and kindergarden. The +kids were building robots, rovers. The story behind it is to build a +rover for use +<a href="http://blog.ecolefrancodanoise.dk/first-week-on-the-dark-side">on +the dark side of the moon</a>, and remote control it. As travel cost +was a bit high for the final destination, and they wanted to test the +concept first, he was looking for volunteers to host a rover for the +kids to control in a foreign country. I ended up volunteering as a +host, and last week the rover arrived. It took a while to arrive +after <a href="http://blog.ecolefrancodanoise.dk/model-moms">it was +built and shipped</a>, because of customs confusion. Luckily we were +able fix it quickly with help from my colleges at work.</p> + +<p>This is what it looked like when the rover arrived. Note the cute +eyes looking up on me from the wrapping</p> + +<img src="http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-esken-med-det-rare-i.jpeg" width="32%" style="clear:left"/> +<img src="http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-den-ser-meg.jpeg" width="32%" style="clear:left"/> +<img src="http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-en-skrue-loes.jpeg" width="32%" style="clear:left"/> + +<p style="text-align:left">Once the robot arrived, we needed to track +down batteries and figure out how to build custom firmware for it with +the appropriate wifi settings. I asked a friend if I could get two +18650 batteries from his pile of Tesla batteries (he had them from the +wrack of a crashed Tesla), so now the rover is running on Tesla +batteries.</p> + +<p>Building +<a href="https://gitlab.com/ecolefrancodanoise/arduino-efd/">the rover +firmware</a> proved a bit harder, as the code did not work out of the +box with the Arduino IDE package in Debian Buster. I suspect this is +due to a unsolved +<a href="https://github.com/arduino/Arduino/pull/2703"> license problem +with arduino</a> blocking Debian from upgrading to the latest version. +In the end we gave up debugging why the IDE failed to find the +required libraries, and ended up using the Arduino Makefile from the +<a href="https://tracker.debian.org/pkg/arduino-mk">arduino-mk Debian +package</a> instead. Unfortunately the camera library is missing from +the Arduino environment in Debian, so we disabled the camera support +for the first firmware build, to get something up and running. With +this reduced firmware, the robot could be controlled via the +controller server, driving around and measuring distance using its +internal acoustic sensor.</p> + +<p>Next, With some help from my friend in Denmark, which checked in the +camera library into the gitlab repository for me to use, we were able +to build a new and more complete version of the firmware, and the +robot is now up and running. This is what the "commander" web page +look like after taking a measurement and a snapshot:</p> + +<img src="http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-commander.png" width="40%" border="1" align="center"/> + +<p>If you want to learn more about this project, you can check out the +<a href="https://hackaday.io/project/164082-the-dark-side-challenge">The +Dark Side Challenge</a> Hackaday web pages.</p> <p>As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address @@ -485,285 +565,66 @@ activities, please send Bitcoin donations to my address - Locating IMDB IDs of movies in the Internet Archive using Wikidata - http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html - http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html - Wed, 25 Oct 2017 12:20:00 +0200 - <p>Recently, I needed to automatically check the copyright status of a -set of <a href="http://www.imdb.com/">The Internet Movie database -(IMDB)</a> entries, to figure out which one of the movies they refer -to can be freely distributed on the Internet. This proved to be -harder than it sounds. IMDB for sure list movies without any -copyright protection, where the copyright protection has expired or -where the movie is lisenced using a permissive license like one from -Creative Commons. These are mixed with copyright protected movies, -and there seem to be no way to separate these classes of movies using -the information in IMDB.</p> - -<p>First I tried to look up entries manually in IMDB, -<a href="https://www.wikipedia.org/">Wikipedia</a> and -<a href="https://www.archive.org/">The Internet Archive</a>, to get a -feel how to do this. It is hard to know for sure using these sources, -but it should be possible to be reasonable confident a movie is "out -of copyright" with a few hours work per movie. As I needed to check -almost 20,000 entries, this approach was not sustainable. I simply -can not work around the clock for about 6 years to check this data -set.</p> - -<p>I asked the people behind The Internet Archive if they could -introduce a new metadata field in their metadata XML for IMDB ID, but -was told that they leave it completely to the uploaders to update the -metadata. Some of the metadata entries had IMDB links in the -description, but I found no way to download all metadata files in bulk -to locate those ones and put that approach aside.</p> - -<p>In the process I noticed several Wikipedia articles about movies -had links to both IMDB and The Internet Archive, and it occured to me -that I could use the Wikipedia RDF data set to locate entries with -both, to at least get a lower bound on the number of movies on The -Internet Archive with a IMDB ID. This is useful based on the -assumption that movies distributed by The Internet Archive can be -legally distributed on the Internet. With some help from the RDF -community (thank you DanC), I was able to come up with this query to -pass to <a href="https://query.wikidata.org/">the SPARQL interface on -Wikidata</a>: - -<p><pre> -SELECT ?work ?imdb ?ia ?when ?label -WHERE -{ - ?work wdt:P31/wdt:P279* wd:Q11424. - ?work wdt:P345 ?imdb. - ?work wdt:P724 ?ia. - OPTIONAL { - ?work wdt:P577 ?when. - ?work rdfs:label ?label. - FILTER(LANG(?label) = "en"). - } -} -</pre></p> - -<p>If I understand the query right, for every film entry anywhere in -Wikpedia, it will return the IMDB ID and The Internet Archive ID, and -when the movie was released and its English title, if either or both -of the latter two are available. At the moment the result set contain -2338 entries. Of course, it depend on volunteers including both -correct IMDB and The Internet Archive IDs in the wikipedia articles -for the movie. It should be noted that the result will include -duplicates if the movie have entries in several languages. There are -some bogus entries, either because The Internet Archive ID contain a -typo or because the movie is not available from The Internet Archive. -I did not verify the IMDB IDs, as I am unsure how to do that -automatically.</p> - -<p>I wrote a small python script to extract the data set from Wikidata -and check if the XML metadata for the movie is available from The -Internet Archive, and after around 1.5 hour it produced a list of 2097 -free movies and their IMDB ID. In total, 171 entries in Wikidata lack -the refered Internet Archive entry. I assume the 70 "disappearing" -entries (ie 2338-2097-171) are duplicate entries.</p> - -<p>This is not too bad, given that The Internet Archive report to -contain <a href="https://archive.org/details/feature_films">5331 -feature films</a> at the moment, but it also mean more than 3000 -movies are missing on Wikipedia or are missing the pair of references -on Wikipedia.</p> - -<p>I was curious about the distribution by release year, and made a -little graph to show how the amount of free movies is spread over the -years:<p> - -<p><img src="http://people.skolelinux.org/pere/blog/images/2017-10-25-verk-i-det-fri-filmer.png"></p> - -<p>I expect the relative distribution of the remaining 3000 movies to -be similar.</p> - -<p>If you want to help, and want to ensure Wikipedia can be used to -cross reference The Internet Archive and The Internet Movie Database, -please make sure entries like this are listed under the "External -links" heading on the Wikipedia article for the movie:</p> - -<p><pre> -* {{Internet Archive film|id=FightingLady}} -* {{IMDb title|id=0036823|title=The Fighting Lady}} -</pre></p> - -<p>Please verify the links on the final page, to make sure you did not -introduce a typo.</p> - -<p>Here is the complete list, if you want to correct the 171 -identified Wikipedia entries with broken links to The Internet -Archive: <a href="http://www.wikidata.org/entity/Q1140317">Q1140317</a>, -<a href="http://www.wikidata.org/entity/Q458656">Q458656</a>, -<a href="http://www.wikidata.org/entity/Q458656">Q458656</a>, -<a href="http://www.wikidata.org/entity/Q470560">Q470560</a>, -<a href="http://www.wikidata.org/entity/Q743340">Q743340</a>, -<a href="http://www.wikidata.org/entity/Q822580">Q822580</a>, -<a href="http://www.wikidata.org/entity/Q480696">Q480696</a>, -<a href="http://www.wikidata.org/entity/Q128761">Q128761</a>, -<a href="http://www.wikidata.org/entity/Q1307059">Q1307059</a>, -<a href="http://www.wikidata.org/entity/Q1335091">Q1335091</a>, -<a href="http://www.wikidata.org/entity/Q1537166">Q1537166</a>, -<a href="http://www.wikidata.org/entity/Q1438334">Q1438334</a>, -<a href="http://www.wikidata.org/entity/Q1479751">Q1479751</a>, -<a href="http://www.wikidata.org/entity/Q1497200">Q1497200</a>, -<a href="http://www.wikidata.org/entity/Q1498122">Q1498122</a>, -<a href="http://www.wikidata.org/entity/Q865973">Q865973</a>, -<a href="http://www.wikidata.org/entity/Q834269">Q834269</a>, -<a href="http://www.wikidata.org/entity/Q841781">Q841781</a>, -<a href="http://www.wikidata.org/entity/Q841781">Q841781</a>, -<a href="http://www.wikidata.org/entity/Q1548193">Q1548193</a>, -<a href="http://www.wikidata.org/entity/Q499031">Q499031</a>, -<a href="http://www.wikidata.org/entity/Q1564769">Q1564769</a>, -<a href="http://www.wikidata.org/entity/Q1585239">Q1585239</a>, -<a href="http://www.wikidata.org/entity/Q1585569">Q1585569</a>, -<a href="http://www.wikidata.org/entity/Q1624236">Q1624236</a>, -<a href="http://www.wikidata.org/entity/Q4796595">Q4796595</a>, -<a href="http://www.wikidata.org/entity/Q4853469">Q4853469</a>, -<a href="http://www.wikidata.org/entity/Q4873046">Q4873046</a>, -<a href="http://www.wikidata.org/entity/Q915016">Q915016</a>, -<a href="http://www.wikidata.org/entity/Q4660396">Q4660396</a>, -<a href="http://www.wikidata.org/entity/Q4677708">Q4677708</a>, -<a href="http://www.wikidata.org/entity/Q4738449">Q4738449</a>, -<a href="http://www.wikidata.org/entity/Q4756096">Q4756096</a>, -<a href="http://www.wikidata.org/entity/Q4766785">Q4766785</a>, -<a href="http://www.wikidata.org/entity/Q880357">Q880357</a>, -<a href="http://www.wikidata.org/entity/Q882066">Q882066</a>, -<a href="http://www.wikidata.org/entity/Q882066">Q882066</a>, -<a href="http://www.wikidata.org/entity/Q204191">Q204191</a>, -<a href="http://www.wikidata.org/entity/Q204191">Q204191</a>, -<a href="http://www.wikidata.org/entity/Q1194170">Q1194170</a>, -<a href="http://www.wikidata.org/entity/Q940014">Q940014</a>, -<a href="http://www.wikidata.org/entity/Q946863">Q946863</a>, -<a href="http://www.wikidata.org/entity/Q172837">Q172837</a>, -<a href="http://www.wikidata.org/entity/Q573077">Q573077</a>, -<a href="http://www.wikidata.org/entity/Q1219005">Q1219005</a>, -<a href="http://www.wikidata.org/entity/Q1219599">Q1219599</a>, -<a href="http://www.wikidata.org/entity/Q1643798">Q1643798</a>, -<a href="http://www.wikidata.org/entity/Q1656352">Q1656352</a>, -<a href="http://www.wikidata.org/entity/Q1659549">Q1659549</a>, -<a href="http://www.wikidata.org/entity/Q1660007">Q1660007</a>, -<a href="http://www.wikidata.org/entity/Q1698154">Q1698154</a>, -<a href="http://www.wikidata.org/entity/Q1737980">Q1737980</a>, -<a href="http://www.wikidata.org/entity/Q1877284">Q1877284</a>, -<a href="http://www.wikidata.org/entity/Q1199354">Q1199354</a>, -<a href="http://www.wikidata.org/entity/Q1199354">Q1199354</a>, -<a href="http://www.wikidata.org/entity/Q1199451">Q1199451</a>, -<a href="http://www.wikidata.org/entity/Q1211871">Q1211871</a>, -<a href="http://www.wikidata.org/entity/Q1212179">Q1212179</a>, -<a href="http://www.wikidata.org/entity/Q1238382">Q1238382</a>, -<a href="http://www.wikidata.org/entity/Q4906454">Q4906454</a>, -<a href="http://www.wikidata.org/entity/Q320219">Q320219</a>, -<a href="http://www.wikidata.org/entity/Q1148649">Q1148649</a>, -<a href="http://www.wikidata.org/entity/Q645094">Q645094</a>, -<a href="http://www.wikidata.org/entity/Q5050350">Q5050350</a>, -<a href="http://www.wikidata.org/entity/Q5166548">Q5166548</a>, -<a href="http://www.wikidata.org/entity/Q2677926">Q2677926</a>, -<a href="http://www.wikidata.org/entity/Q2698139">Q2698139</a>, -<a href="http://www.wikidata.org/entity/Q2707305">Q2707305</a>, -<a href="http://www.wikidata.org/entity/Q2740725">Q2740725</a>, -<a href="http://www.wikidata.org/entity/Q2024780">Q2024780</a>, -<a href="http://www.wikidata.org/entity/Q2117418">Q2117418</a>, -<a href="http://www.wikidata.org/entity/Q2138984">Q2138984</a>, -<a href="http://www.wikidata.org/entity/Q1127992">Q1127992</a>, -<a href="http://www.wikidata.org/entity/Q1058087">Q1058087</a>, -<a href="http://www.wikidata.org/entity/Q1070484">Q1070484</a>, -<a href="http://www.wikidata.org/entity/Q1080080">Q1080080</a>, -<a href="http://www.wikidata.org/entity/Q1090813">Q1090813</a>, -<a href="http://www.wikidata.org/entity/Q1251918">Q1251918</a>, -<a href="http://www.wikidata.org/entity/Q1254110">Q1254110</a>, -<a href="http://www.wikidata.org/entity/Q1257070">Q1257070</a>, -<a href="http://www.wikidata.org/entity/Q1257079">Q1257079</a>, -<a href="http://www.wikidata.org/entity/Q1197410">Q1197410</a>, -<a href="http://www.wikidata.org/entity/Q1198423">Q1198423</a>, -<a href="http://www.wikidata.org/entity/Q706951">Q706951</a>, -<a href="http://www.wikidata.org/entity/Q723239">Q723239</a>, -<a href="http://www.wikidata.org/entity/Q2079261">Q2079261</a>, -<a href="http://www.wikidata.org/entity/Q1171364">Q1171364</a>, -<a href="http://www.wikidata.org/entity/Q617858">Q617858</a>, -<a href="http://www.wikidata.org/entity/Q5166611">Q5166611</a>, -<a href="http://www.wikidata.org/entity/Q5166611">Q5166611</a>, -<a href="http://www.wikidata.org/entity/Q324513">Q324513</a>, -<a href="http://www.wikidata.org/entity/Q374172">Q374172</a>, -<a href="http://www.wikidata.org/entity/Q7533269">Q7533269</a>, -<a href="http://www.wikidata.org/entity/Q970386">Q970386</a>, -<a href="http://www.wikidata.org/entity/Q976849">Q976849</a>, -<a href="http://www.wikidata.org/entity/Q7458614">Q7458614</a>, -<a href="http://www.wikidata.org/entity/Q5347416">Q5347416</a>, -<a href="http://www.wikidata.org/entity/Q5460005">Q5460005</a>, -<a href="http://www.wikidata.org/entity/Q5463392">Q5463392</a>, -<a href="http://www.wikidata.org/entity/Q3038555">Q3038555</a>, -<a href="http://www.wikidata.org/entity/Q5288458">Q5288458</a>, -<a href="http://www.wikidata.org/entity/Q2346516">Q2346516</a>, -<a href="http://www.wikidata.org/entity/Q5183645">Q5183645</a>, -<a href="http://www.wikidata.org/entity/Q5185497">Q5185497</a>, -<a href="http://www.wikidata.org/entity/Q5216127">Q5216127</a>, -<a href="http://www.wikidata.org/entity/Q5223127">Q5223127</a>, -<a href="http://www.wikidata.org/entity/Q5261159">Q5261159</a>, -<a href="http://www.wikidata.org/entity/Q1300759">Q1300759</a>, -<a href="http://www.wikidata.org/entity/Q5521241">Q5521241</a>, -<a href="http://www.wikidata.org/entity/Q7733434">Q7733434</a>, -<a href="http://www.wikidata.org/entity/Q7736264">Q7736264</a>, -<a href="http://www.wikidata.org/entity/Q7737032">Q7737032</a>, -<a href="http://www.wikidata.org/entity/Q7882671">Q7882671</a>, -<a href="http://www.wikidata.org/entity/Q7719427">Q7719427</a>, -<a href="http://www.wikidata.org/entity/Q7719444">Q7719444</a>, -<a href="http://www.wikidata.org/entity/Q7722575">Q7722575</a>, -<a href="http://www.wikidata.org/entity/Q2629763">Q2629763</a>, -<a href="http://www.wikidata.org/entity/Q2640346">Q2640346</a>, -<a href="http://www.wikidata.org/entity/Q2649671">Q2649671</a>, -<a href="http://www.wikidata.org/entity/Q7703851">Q7703851</a>, -<a href="http://www.wikidata.org/entity/Q7747041">Q7747041</a>, -<a href="http://www.wikidata.org/entity/Q6544949">Q6544949</a>, -<a href="http://www.wikidata.org/entity/Q6672759">Q6672759</a>, -<a href="http://www.wikidata.org/entity/Q2445896">Q2445896</a>, -<a href="http://www.wikidata.org/entity/Q12124891">Q12124891</a>, -<a href="http://www.wikidata.org/entity/Q3127044">Q3127044</a>, -<a href="http://www.wikidata.org/entity/Q2511262">Q2511262</a>, -<a href="http://www.wikidata.org/entity/Q2517672">Q2517672</a>, -<a href="http://www.wikidata.org/entity/Q2543165">Q2543165</a>, -<a href="http://www.wikidata.org/entity/Q426628">Q426628</a>, -<a href="http://www.wikidata.org/entity/Q426628">Q426628</a>, -<a href="http://www.wikidata.org/entity/Q12126890">Q12126890</a>, -<a href="http://www.wikidata.org/entity/Q13359969">Q13359969</a>, -<a href="http://www.wikidata.org/entity/Q13359969">Q13359969</a>, -<a href="http://www.wikidata.org/entity/Q2294295">Q2294295</a>, -<a href="http://www.wikidata.org/entity/Q2294295">Q2294295</a>, -<a href="http://www.wikidata.org/entity/Q2559509">Q2559509</a>, -<a href="http://www.wikidata.org/entity/Q2559912">Q2559912</a>, -<a href="http://www.wikidata.org/entity/Q7760469">Q7760469</a>, -<a href="http://www.wikidata.org/entity/Q6703974">Q6703974</a>, -<a href="http://www.wikidata.org/entity/Q4744">Q4744</a>, -<a href="http://www.wikidata.org/entity/Q7766962">Q7766962</a>, -<a href="http://www.wikidata.org/entity/Q7768516">Q7768516</a>, -<a href="http://www.wikidata.org/entity/Q7769205">Q7769205</a>, -<a href="http://www.wikidata.org/entity/Q7769988">Q7769988</a>, -<a href="http://www.wikidata.org/entity/Q2946945">Q2946945</a>, -<a href="http://www.wikidata.org/entity/Q3212086">Q3212086</a>, -<a href="http://www.wikidata.org/entity/Q3212086">Q3212086</a>, -<a href="http://www.wikidata.org/entity/Q18218448">Q18218448</a>, -<a href="http://www.wikidata.org/entity/Q18218448">Q18218448</a>, -<a href="http://www.wikidata.org/entity/Q18218448">Q18218448</a>, -<a href="http://www.wikidata.org/entity/Q6909175">Q6909175</a>, -<a href="http://www.wikidata.org/entity/Q7405709">Q7405709</a>, -<a href="http://www.wikidata.org/entity/Q7416149">Q7416149</a>, -<a href="http://www.wikidata.org/entity/Q7239952">Q7239952</a>, -<a href="http://www.wikidata.org/entity/Q7317332">Q7317332</a>, -<a href="http://www.wikidata.org/entity/Q7783674">Q7783674</a>, -<a href="http://www.wikidata.org/entity/Q7783704">Q7783704</a>, -<a href="http://www.wikidata.org/entity/Q7857590">Q7857590</a>, -<a href="http://www.wikidata.org/entity/Q3372526">Q3372526</a>, -<a href="http://www.wikidata.org/entity/Q3372642">Q3372642</a>, -<a href="http://www.wikidata.org/entity/Q3372816">Q3372816</a>, -<a href="http://www.wikidata.org/entity/Q3372909">Q3372909</a>, -<a href="http://www.wikidata.org/entity/Q7959649">Q7959649</a>, -<a href="http://www.wikidata.org/entity/Q7977485">Q7977485</a>, -<a href="http://www.wikidata.org/entity/Q7992684">Q7992684</a>, -<a href="http://www.wikidata.org/entity/Q3817966">Q3817966</a>, -<a href="http://www.wikidata.org/entity/Q3821852">Q3821852</a>, -<a href="http://www.wikidata.org/entity/Q3420907">Q3420907</a>, -<a href="http://www.wikidata.org/entity/Q3429733">Q3429733</a>, -<a href="http://www.wikidata.org/entity/Q774474">Q774474</a></p> + Nikita version 0.4 released - free software archive API server + http://people.skolelinux.org/pere/blog/Nikita_version_0_4_released___free_software_archive_API_server.html + http://people.skolelinux.org/pere/blog/Nikita_version_0_4_released___free_software_archive_API_server.html + Wed, 22 May 2019 11:30:00 +0200 + <p>This morning, a new release of +<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core/">Nikita +Noark 5 core project</a> was +<a href="https://lists.nuug.no/pipermail/nikita-noark/2019-May/000468.html">announced +on the project mailing list</a>. The Nikita free software solution is +an implementation of the Norwegian archive standard Noark 5 used by +government offices in Norway. These were the changes in version 0.4 +since version 0.3, see the email link above for links to a demo site:</p> + +<ul> + + <li>Roll out OData handling to all endpoints where applicable</li> + <li>Changed the relation key for "ny-journalpost" to the official one.</li> + <li>Better link generation on outgoing links.</li> + <li>Tidy up code and make code and approaches more consistent throughout + the codebase</li> + <li>Update rels to be in compliance with updated version in the + interface standard</li> + <li>Avoid printing links on empty objects as they can't have links</li> + <li>Small bug fixes and improvements</li> + <li>Start moving generation of outgoing links to @Service layer so access + control can be used when generating links</li> + <li>Log exception that was being swallowed so it's traceable</li> + <li>Fix name mapping problem</li> + <li>Update templated printing so templated should only be printed if it + is set true. Requires more work to roll out across entire + application.</li> + <li>Remove Record->DocumentObject as per domain model of n5v4</li> + <li>Add ability to delete lists filtered with OData</li> + <li>Return NO_CONTENT (204) on delete as per interface standard</li> + <li>Introduce support for ConstraintViolationException exception</li> + <li>Make Service classes extend NoarkService</li> + <li>Make code base respect X-Forwarded-Host, X-Forwarded-Proto and + X-Forwarded-Port</li> + <li>Update CorrespondencePart* code to be more in line with Single + Responsibility Principle</li> + <li>Make package name follow directory structure</li> + <li>Make sure Document number starts at 1, not 0</li> + <li>Fix isues discovered by FindBugs</li> + <li>Update from Date to ZonedDateTime</li> + <li>Fix wrong tablename</li> + <li>Introduce Service layer tests</li> + <li>Improvements to CorrespondencePart</li> + <li>Continued work on Class / Classificationsystem</li> + <li>Fix feature where authors were stored as storageLocations</li> + <li>Update HQL builder for OData</li> + <li>Update OData search capability from webpage</li> + +</ul> + +<p>If free and open standardized archiving API sound interesting to +you, please contact us on IRC +(<a href="irc://irc.freenode.net/%23nikita">#nikita on +irc.freenode.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 @@ -772,23 +633,52 @@ activities, please send Bitcoin donations to my address - A one-way wall on the border? - http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html - http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html - Sat, 14 Oct 2017 22:10:00 +0200 - <p>I find it fascinating how many of the people being locked inside -the proposed border wall between USA and Mexico support the idea. The -proposal to keep Mexicans out reminds me of -<a href="http://www.history.com/news/10-things-you-may-not-know-about-the-berlin-wall">the -propaganda twist from the East Germany government</a> calling the wall -the “Antifascist Bulwark” after erecting the Berlin Wall, claiming -that the wall was erected to keep enemies from creeping into East -Germany, while it was obvious to the people locked inside it that it -was erected to keep the people from escaping.</p> - -<p>Do the people in USA supporting this wall really believe it is a -one way wall, only keeping people on the outside from getting in, -while not keeping people in the inside from getting out?</p> + MIME type "text/vnd.sosi" for SOSI map data + http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html + http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html + Mon, 20 May 2019 08:35:00 +0200 + <p>As part of my involvement in the work to +<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard">standardise +a REST based API for Noark 5</a>, the Norwegian archiving standard, I +spent some time the last few months to try to register a +<a href="https://www.iana.org/assignments/media-types/">MIME type</a> +and <a href="https://www.nationalarchives.gov.uk/PRONOM/">PRONOM +code</a> for the SOSI file format. The background is that there is a +set of formats approved for long term storage and archiving in Norway, +and among these formats, SOSI is the only format missing a MIME type +and PRONOM code.</p> + +<p>What is SOSI, you might ask? To quote Wikipedia: SOSI is short for +Samordnet Opplegg for Stedfestet Informasjon (literally "Coordinated +Approach for Spatial Information", but more commonly expanded in +English to Systematic Organization of Spatial Information). It is a +text based file format for geo-spatial vector information used in +Norway. Information about the SOSI format can be found in English +from <a href="https://en.wikipedia.org/wiki/SOSI">Wikipedia</a>. The +specification is available in Norwegian from +<a href="https://www.kartverket.no/geodataarbeid/Standarder/SOSI/">the +Norwegian mapping authority</a>. The SOSI standard, which originated +in the beginning of nineteen eighties, was the inspiration and formed the +basis for the XML based +<a href="https://en.wikipedia.org/wiki/Geography_Markup_Language">Geography +Markup Language</a>.</p> + +<p>I have so far written +<a href="https://github.com/file/file/pull/67">a pattern matching +rule</a> for the file(1) unix tool to recognize SOSI files, submitted +a request to the PRONOM project to have a PRONOM ID assigned to the +format (reference TNA1555078202S60), and today send a request to IANA +to register the "text/vnd.sosi" MIME type for this format (referanse +<a href="https://tools.iana.org/public-view/viewticket/1143144">IANA +#1143144</a>). If all goes well, in a few months, anyone implementing +the Noark 5 Tjenestegrensesnitt API spesification should be able to +use an official MIME type and PRONOM code for SOSI files. In +addition, anyone using SOSI files on Linux should be able to +automatically recognise the format and web sites handing out SOSI +files can begin providing a more specific MIME type. So far, SOSI +files has been handed out from web sites using the +"application/octet-stream" MIME type, which is just a nice way of +stating "I do not know". Soon, we will know. :)</p> <p>As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address @@ -797,45 +687,148 @@ activities, please send Bitcoin donations to my address - Generating 3D prints in Debian using Cura and Slic3r(-prusa) - http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html - http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html - Mon, 9 Oct 2017 10:50:00 +0200 - <p>At my nearby maker space, -<a href="http://sonen.ifi.uio.no/">Sonen</a>, I heard the story that it -was easier to generate gcode files for theyr 3D printers (Ultimake 2+) -on Windows and MacOS X than Linux, because the software involved had -to be manually compiled and set up on Linux while premade packages -worked out of the box on Windows and MacOS X. I found this annoying, -as the software involved, -<a href="https://github.com/Ultimaker/Cura">Cura</a>, is free software -and should be trivial to get up and running on Linux if someone took -the time to package it for the relevant distributions. I even found -<a href="https://bugs.debian.org/706656">a request for adding into -Debian</a> from 2013, which had seem some activity over the years but -never resulted in the software showing up in Debian. So a few days -ago I offered my help to try to improve the situation.</p> - -<p>Now I am very happy to see that all the packages required by a -working Cura in Debian are uploaded into Debian and waiting in the NEW -queue for the ftpmasters to have a look. You can track the progress -on -<a href="https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org">the -status page for the 3D printer team</a>.</p> - -<p>The uploaded packages are a bit behind upstream, and was uploaded -now to get slots in <a href="https://ftp-master.debian.org/new.html">the NEW -queue</a> while we work up updating the packages to the latest -upstream version.</p> - -<p>On a related note, two competitors for Cura, which I found harder -to use and was unable to configure correctly for Ultimaker 2+ in the -short time I spent on it, are already in Debian. If you are looking -for 3D printer "slicers" and want something already available in -Debian, check out -<a href="https://tracker.debian.org/pkg/slic3r">slic3r</a> and -<a href="https://tracker.debian.org/pkg/slic3r-prusa">slic3r-prusa</a>. -The latter is a fork of the former.</p> + PlantUML for text based UML diagram modelling - nice free software + http://people.skolelinux.org/pere/blog/PlantUML_for_text_based_UML_diagram_modelling___nice_free_software.html + http://people.skolelinux.org/pere/blog/PlantUML_for_text_based_UML_diagram_modelling___nice_free_software.html + Mon, 25 Mar 2019 09:35:00 +0100 + <p>As part of my involvement with the +<a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core/">Nikita +Noark 5 core project</a>, I have been proposing improvements to the +API specification created by <a href="https://www.arkivverket.no/">The +National Archives of Norway</a> and helped migrating the text from a +version control system unfriendly binary format (docx) to Markdown in +git. Combined with the migration to a public git repository (on +github), this has made it possible for anyone to suggest improvement +to the text.</p> + +<p>The specification is filled with UML diagrams. I believe the +original diagrams were modelled using Sparx Systems Enterprise +Architect, and exported as EMF files for import into docx. This +approach make it very hard to track changes using a version control +system. To improve the situation I have been looking for a good text +based UML format with associated command line free software tools on +Linux and Windows, to allow anyone to send in corrections to the UML +diagrams in the specification. The tool must be text based to work +with git, and command line to be able to run it automatically to +generate the diagram images. Finally, it must be free software to +allow anyone, even those that can not accept a non-free software +license, to contribute.</p> + +<p>I did not know much about free software UML modelling tools when I +started. I have used dia and inkscape for simple modelling in the +past, but neither are available on Windows, as far as I could tell. I +came across a nice +<a href="https://modeling-languages.com/text-uml-tools-complete-list/">list +of text mode uml tools</a>, and tested out a few of the tools listed +there. <a href="http://plantuml.com/">The PlantUML tool</a> seemed +most promising. After verifying that the packages +<a href="https://tracker.debian.org/pkg/plantuml">is available in +Debian</a> and found <a href="https://github.com/plantuml/plantuml">its +Java source</a> under a GPL license on github, I set out to test if it +could represent the diagrams we needed, ie the ones currently in +<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">the +Noark 5 Tjenestegrensesnitt specification</a>. I am happy to report +that it could represent them, even thought it have a few warts here +and there.</p> + +<p>After a few days of modelling I completed the task this weekend. A +temporary link to the complete set of diagrams (original and from +PlantUML) is available in +<a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/issues/76">the +github issue discussing the need for a text based UML format</a>, but +please note I lack a sensible tool to convert EMF files to PNGs, so +the "original" rendering is not as good as the original was in the +publised PDF.</p> + +<p>Here is an example UML diagram, showing the core classes for +keeping metadata about archived documents:</p> + +<pre> +@startuml +skinparam classAttributeIconSize 0 + +!include media/uml-class-arkivskaper.iuml +!include media/uml-class-arkiv.iuml +!include media/uml-class-klassifikasjonssystem.iuml +!include media/uml-class-klasse.iuml +!include media/uml-class-arkivdel.iuml +!include media/uml-class-mappe.iuml +!include media/uml-class-merknad.iuml +!include media/uml-class-registrering.iuml +!include media/uml-class-basisregistrering.iuml +!include media/uml-class-dokumentbeskrivelse.iuml +!include media/uml-class-dokumentobjekt.iuml +!include media/uml-class-konvertering.iuml +!include media/uml-datatype-elektronisksignatur.iuml + +Arkivstruktur.Arkivskaper "+arkivskaper 1..*" <-o "+arkiv 0..*" Arkivstruktur.Arkiv +Arkivstruktur.Arkiv o--> "+underarkiv 0..*" Arkivstruktur.Arkiv +Arkivstruktur.Arkiv "+arkiv 1" o--> "+arkivdel 0..*" Arkivstruktur.Arkivdel +Arkivstruktur.Klassifikasjonssystem "+klassifikasjonssystem [0..1]" <--o "+arkivdel 1..*" Arkivstruktur.Arkivdel +Arkivstruktur.Klassifikasjonssystem "+klassifikasjonssystem [0..1]" o--> "+klasse 0..*" Arkivstruktur.Klasse +Arkivstruktur.Arkivdel "+arkivdel 0..1" o--> "+mappe 0..*" Arkivstruktur.Mappe +Arkivstruktur.Arkivdel "+arkivdel 0..1" o--> "+registrering 0..*" Arkivstruktur.Registrering +Arkivstruktur.Klasse "+klasse 0..1" o--> "+mappe 0..*" Arkivstruktur.Mappe +Arkivstruktur.Klasse "+klasse 0..1" o--> "+registrering 0..*" Arkivstruktur.Registrering +Arkivstruktur.Mappe --> "+undermappe 0..*" Arkivstruktur.Mappe +Arkivstruktur.Mappe "+mappe 0..1" o--> "+registrering 0..*" Arkivstruktur.Registrering +Arkivstruktur.Merknad "+merknad 0..*" <--* Arkivstruktur.Mappe +Arkivstruktur.Merknad "+merknad 0..*" <--* Arkivstruktur.Dokumentbeskrivelse +Arkivstruktur.Basisregistrering -|> Arkivstruktur.Registrering +Arkivstruktur.Merknad "+merknad 0..*" <--* Arkivstruktur.Basisregistrering +Arkivstruktur.Registrering "+registrering 1..*" o--> "+dokumentbeskrivelse 0..*" Arkivstruktur.Dokumentbeskrivelse +Arkivstruktur.Dokumentbeskrivelse "+dokumentbeskrivelse 1" o-> "+dokumentobjekt 0..*" Arkivstruktur.Dokumentobjekt +Arkivstruktur.Dokumentobjekt *-> "+konvertering 0..*" Arkivstruktur.Konvertering +Arkivstruktur.ElektroniskSignatur -[hidden]-> Arkivstruktur.Dokumentobjekt +@enduml +</pre> + +<p><a href="http://plantuml.com/class-diagram">The format</a> is quite +compact, with little redundant information. The text expresses +entities and relations, and there is little layout related fluff. One +can reuse content by using include files, allowing for consistent +naming across several diagrams. The include files can be standalone +PlantUML too. Here is the content of +<tt>media/uml-class-arkivskaper.iuml<tt>:</p> + +<pre> +@startuml +class Arkivstruktur.Arkivskaper <Arkivenhet> { + +arkivskaperID : string + +arkivskaperNavn : string + +beskrivelse : string [0..1] +} +@enduml +</pre> + +<p>This is what the complete diagram for the PlantUML notation above +look like:</p> + +<p><img width="80%" src="http://people.skolelinux.org/pere/blog/images/2019-03-25-noark5-plantuml-diagrameksempel.png"></p> + +<p>A cool feature of PlantUML is that the generated PNG files include +the entire original source diagram as text. The source (with include +statements expanded) can be extracted using for example +<tt>exiftool</tt>. Another cool feature is that parts of the entities +can be hidden after inclusion. This allow to use include files with +all attributes listed, even for UML diagrams that should not list any +attributes.</p> + +<p>The diagram also show some of the warts. Some times the layout +engine place text labels on top of each other, and some times it place +the class boxes too close to each other, not leaving room for the +labels on the relationship arrows. The former can be worked around by +placing extra newlines in the labes (ie "\n"). I did not do it here +to be able to demonstrate the issue. I have not found a good way +around the latter, so I normally try to reduce the problem by changing +from vertical to horizontal links to improve the layout.</p> + +<p>All in all, I am quite happy with PlantUML, and very impressed with +how quickly its lead developer responds to questions. So far I got an +answer to my questions in a few hours when I send an email. I +definitely recommend looking at PlantUML if you need to make UML +diagrams. Note, PlantUML can draw a lot more than class relations. +Check out the documention for a complete list. :)</p> <p>As usual, if you use Bitcoin and want to show your support of my activities, please send Bitcoin donations to my address