The complete and free âout of the boxâ software solution for
-schools, Debian Edu /
-Skolelinux, is used quite a lot in Germany, and one of the people
-involved is Bernd Zeitzen, who show up on the project mailing lists
-from time to time with interesting questions and tips on how to adjust
-the setup. I managed to interview him this summer.
-
-
Who are you, and how do you spend your days?
-
-
My name is Bernd Zeitzen and I'm married with Hedda, a self
-employed physiotherapist. My former profession is tool maker, but I
-haven't worked for 30 years in this job. 30 years ago I started to
-support my wife and become her officeworker and a few years later the
-administrator for a small computer network, today based on Ubuntu
-Server (Samba, OpenVPN). For her daily work she has to use Windows
-Desktops because the software she needs to organize her business only
-works with Windows . :-(
-
-
In 1988 we started with one PC and DOS, then I learned to use
-Windows 98, 2000, XP, â¦, 8, Ubuntu, MacOSX. Today we are running a
-Linux server with 6 Windows clients and 10 persons (teacher of
-children with special needs, speech therapist, occupational therapist,
-psychologist and officeworkers) using our Samba shares via OpenVPN to
-work with the documentations of our patients.
-
-
How did you get in contact with the Skolelinux / Debian Edu
-project?
-
-
Two years ago a friend of mine asked me, if I want to get a job in
-his school (Gymnasium
-Harsewinkel). They started with Skolelinux / Debian Edu and they
-were looking for people to give support to the teachers using the
-software and the network and teaching the pupils increasing their
-computer skills in optional lessons. I'm spending 4-6 hours a week
-with this job.
-
-
What do you see as the advantages of Skolelinux / Debian
-Edu?
-
-
The independence.
-
-
First: Every person is allowed to use, share and develop the
-software. Even if you are poor, you are allowed to use the software
-included in Skolelinux/Debian Edu and all the other Free Software.
-
-
Second: The software runs on old machines and this gives us the
-possibility to recycle computers, weeded out from offices. The
-servers and desktops are running for more than two years and they are
-working reliable.
-
-
We have two servers (one tjener and one terminal server), 45
-workstations in three classrooms and seven laptops as a mobile
-solution for all classrooms. These machines are all booting from the
-terminal server. In the moment we are installing 30 laptops as mobile
-workstations. Then the pupils have the possibility to work with these
-machines in their classrooms. Internet access is realized by a WLAN
-router, connected to the schools network. This is all done without a
-dedicated system administrator or a computer science teacher.
-
-
What do you see as the disadvantages of Skolelinux / Debian
-Edu?
-
-
Teachers and pupils are Windows users. <Irony on> And Linux
-isn't cool. It's software for freaks using the command line. <Irony
-off> They don't realize the stability of the system.
-
-
Which free software do you use daily?
-
-
Firefox, Thunderbird, LibreOffice, Ubuntu Server 12.04 (Samba,
-Apache, MySQL, Joomla!, ⦠and Skolelinux / Debian Edu)
-
-
Which strategy do you believe is the right one to use to
-get schools to use free software?
-
-
In Germany we have the situation: every school is free to decide
-which software they want to use. This decision is influenced by
-teachers who learned to use Windows and MS Office. They buy a PC with
-Windows preinstalled and an additional testing version of MS
-Office. They don't know about the possibility to use Free Software
-instead. Another problem are the publisher of school books. They
-develop their software, added to the school books, for Windows.
+
+
20th April 2017
+
Jeg oppdaget i dag at nettstedet som
+publiserer offentlige postjournaler fra statlige etater, OEP, har
+begynt å blokkerer enkelte typer webklienter fra å få tilgang. Vet
+ikke hvor mange det gjelder, men det gjelder i hvert fall libwww-perl
+og curl. For å teste selv, kjør følgende:
+
+
+% curl -v -s https://www.oep.no/pub/report.xhtml?reportId=3 2>&1 |grep '< HTTP'
+< HTTP/1.1 404 Not Found
+% curl -v -s --header 'User-Agent:Opera/12.0' https://www.oep.no/pub/report.xhtml?reportId=3 2>&1 |grep '< HTTP'
+< HTTP/1.1 200 OK
+%
+
+
+
Her kan en se at tjenesten gir «404 Not Found» for curl i
+standardoppsettet, mens den gir «200 OK» hvis curl hevder å være Opera
+versjon 12.0. Offentlig elektronisk postjournal startet blokkeringen
+2017-03-02.
+
+
Blokkeringen vil gjøre det litt vanskeligere å maskinelt hente
+informasjon fra oep.no. Kan blokkeringen være gjort for å hindre
+automatisert innsamling av informasjon fra OEP, slik Pressens
+Offentlighetsutvalg gjorde for å dokumentere hvordan departementene
+hindrer innsyn i
+rapporten
+«Slik hindrer departementer innsyn» som ble publiserte i januar
+2017. Det virker usannsynlig, da det jo er trivielt å bytte
+User-Agent til noe nytt.
+
+
Finnes det juridisk grunnlag for det offentlige å diskriminere
+webklienter slik det gjøres her? Der tilgang gis eller ikke alt etter
+hva klienten sier at den heter? Da OEP eies av DIFI og driftes av
+Basefarm, finnes det kanskje noen dokumenter sendt mellom disse to
+aktørene man kan be om innsyn i for å forstå hva som har skjedd. Men
+postjournalen
+til DIFI viser kun to dokumenter det siste året mellom DIFI og
+Basefarm.
+Mimes brønn neste,
+tenker jeg.
@@ -1109,39 +616,101 @@ develop their software, added to the school books, for Windows.
-
-
23rd July 2014
-
This summer I finally had time to continue working on the Norwegian
-docbook version of the 2004 book
-Free Culture by Lawrence Lessig,
-to get a Norwegian text explaining the problems with todays copyright
-law. Yesterday, I finally completed translated the book text. There
-are still some foot/end notes left to translate, the colophon page
-need to be rewritten, and a few words and phrases still need to be
-translated, but the Norwegian text is ready for the first proof
-reading. :) More spell checking is needed, and several illustrations
-need to be cleaned up. The work stopped up because I had to give
-priority to other projects the last year, and the progress graph of
-the translation show this very well:
-
-

-
-
If you want to read the result, check out the
-github
-project pages and the
-PDF,
-EPUB
-and HTML version available in the
-archive
-directory.
-
-
Please report typos, bugs and improvements to the github project if
-you find any.
+
+
19th March 2017
+
The Nikita
+Noark 5 core project is implementing the Norwegian standard for
+keeping an electronic archive of government documents.
+The
+Noark 5 standard document the requirement for data systems used by
+the archives in the Norwegian government, and the Noark 5 web interface
+specification document a REST web service for storing, searching and
+retrieving documents and metadata in such archive. I've been involved
+in the project since a few weeks before Christmas, when the Norwegian
+Unix User Group
+announced
+it supported the project. I believe this is an important project,
+and hope it can make it possible for the government archives in the
+future to use free software to keep the archives we citizens depend
+on. But as I do not hold such archive myself, personally my first use
+case is to store and analyse public mail journal metadata published
+from the government. I find it useful to have a clear use case in
+mind when developing, to make sure the system scratches one of my
+itches.
+
+
If you would like to help make sure there is a free software
+alternatives for the archives, please join our IRC channel
+(#nikita on
+irc.freenode.net) and
+the
+project mailing list.
+
+
When I got involved, the web service could store metadata about
+documents. But a few weeks ago, a new milestone was reached when it
+became possible to store full text documents too. Yesterday, I
+completed an implementation of a command line tool
+archive-pdf to upload a PDF file to the archive using this
+API. The tool is very simple at the moment, and find existing
+fonds, series and
+files while asking the user to select which one to use if more than
+one exist. Once a file is identified, the PDF is associated with the
+file and uploaded, using the title extracted from the PDF itself. The
+process is fairly similar to visiting the archive, opening a cabinet,
+locating a file and storing a piece of paper in the archive. Here is
+a test run directly after populating the database with test data using
+our API tester:
+
+
+~/src//noark5-tester$ ./archive-pdf mangelmelding/mangler.pdf
+using arkiv: Title of the test fonds created 2017-03-18T23:49:32.103446
+using arkivdel: Title of the test series created 2017-03-18T23:49:32.103446
+
+ 0 - Title of the test case file created 2017-03-18T23:49:32.103446
+ 1 - Title of the test file created 2017-03-18T23:49:32.103446
+Select which mappe you want (or search term): 0
+Uploading mangelmelding/mangler.pdf
+ PDF title: Mangler i spesifikasjonsdokumentet for NOARK 5 Tjenestegrensesnitt
+ File 2017/1: Title of the test case file created 2017-03-18T23:49:32.103446
+~/src//noark5-tester$
+
+
+
You can see here how the fonds (arkiv) and serie (arkivdel) only had
+one option, while the user need to choose which file (mappe) to use
+among the two created by the API tester. The archive-pdf
+tool can be found in the git repository for the API tester.
+
+
In the project, I have been mostly working on
+the API
+tester so far, while getting to know the code base. The API
+tester currently use
+the HATEOAS links
+to traverse the entire exposed service API and verify that the exposed
+operations and objects match the specification, as well as trying to
+create objects holding metadata and uploading a simple XML file to
+store. The tester has proved very useful for finding flaws in our
+implementation, as well as flaws in the reference site and the
+specification.
+
+
The test document I uploaded is a summary of all the specification
+defects we have collected so far while implementing the web service.
+There are several unclear and conflicting parts of the specification,
+and we have
+started
+writing down the questions we get from implementing it. We use a
+format inspired by how The
+Austin Group collect defect reports for the POSIX standard with
+their
+instructions for the MANTIS defect tracker system, in lack of an official way to structure defect reports for Noark 5 (our first submitted defect report was a request for a procedure for submitting defect reports :).
+
+
The Nikita project is implemented using Java and Spring, and is
+fairly easy to get up and running using Docker containers for those
+that want to test the current code base. The API tester is
+implemented in Python.
@@ -1156,6 +725,83 @@ you find any.
Archive