Friday, 20 April 2018

TextWrangler is end of life, and why I care

For those of you unfamiliar with the product, TextWrangler is a very nice language aware text editor for OS X from the same people who produce BBEdit.

Over the years I've used in mainly to write MarkDown, raw HTML and Perl, and it's done my proud. The folks at BBEdit have now decided to cease development of TextWrangler, and encourage people to move to BBEdit, although existing TextWrangler installations will continue to work provided you don't upgrade to the latest version of OS X (now Mac OS).

Essentially if you move to BBEdit, you get a thirty day free trial of the paid for product after which time you can say 'No thanks' and dropdown from the paid for product to a free version BBedit Lite, which has all the features currently in TextWrangler.

BBedit don'd publish product roadmaps, so we can't say with certainty what's the future of BBEdit Lite, but it's probably fair enough to assume that it'll be around for a few years.

Unfortunate, but that's life. It's their product, and they can do what they like with it.

Personally, I find that these days I'm increasingly going back to the Windows platform, so I'll probably not be that inconvenienced by its demise.

However, over the years, I've helped several citizen science, local history, and other community projects get going, be it counting bugs (real bugs ones with six legs) or transcribing old records.

These projects usually struggle to buy a box of teabags and a pack of MacVities digestives, and this is usually where I get involved.

These projects are often very reliant on volunteer labour and have next to no budget for anything. Basically what I do is try and get their recording methodology in place and help them get software installed.

Often they acquire what IT equipment they have through donations - old iMacs from dentist's surgeries, local library system cast offs, or PC's donated via a bank's community programme.

Now the people involved in these projects are often highly skilled in their specialisation, but they're not really into digital archiving or indeed IT generally.

So, when helping them get going I've tended to emphasise open products with open file formats so that the data can be imported into something else later with a minimum of effort. At the same time I've usually encouraged people to use text as a format for working notes and records because of it's clarity and simplicity.

And where possible, I've tried to leave them in a situation where they can be self supporting with simple products that it doesn't matter too much if they don't upgrade.

Now, remember these iMacs from the dentists surgery (and others from other places).

Over the last 10 or 12 years I've been recommending TextWrangler to my Mac users, because (a) it was rock solid, and (b) free. It's running on old machines, many of which will never, or can never, be upgraded to the latest version of OS X.

That shouldn't be a problem, except that TextWrangler now tells you it's end of life when it checks for updates, and this confuses people. They think they have to upgrade, even when they don't, and the  whole 'try before you buy' thing confuses them even more.

And that's creating a support problem. Like I said, unfortunate.

Monday, 16 April 2018

Standard Notes

About a month ago, I bought myself an old ThinkPad as a stopgap replacement computer and installed Standard Notes on it.

Since then I've played with standard notes as a note taking application.

Just to be clear, I use OneNote and Evernote to manage documents, be they scanned nineteenth century newspaper extracts, household bills, or useful web pages. On the whole I don't use them to manage working notes.

These I usually simply write up in Markdown - my markdown documents are more of an expanded dot point list rather than a complex document with embedded images and links - using an editor such as Kate and save them with a filename starting with the date and something sensible.

Probably I ought to use something a bit more structured to group documents together rather than a self documenting file structure, but then I've survived forty years on the fringes of academia working that way.

Cherrytree, about which I blogged some time ago, would be a suitable tool, especially as you can locate the .ctb file on Dropbox, OneDrive or what have you to share between machines (and incidentally provide a backup of sorts).

The only concern is that CherryTree is basically a one person project, which has long term support implications, while Standard Notes is owned by a small company and possibly a better option for long term support. Basically if you need to do due diligence on your software tools as part of a project, Standard Notes would probably come out ahead on longevity and risk.

So I had a play with Standard Notes. Out of the box it's fairly sparse, you need a subscription to unlock the clever edits, saving to OneDrive, and other nice features.

Featurewise the basic version is much of a muchness with CherryTree. Given the way I work there's effectively no difference in functionality.

The lack of a native markdown editor in the basic version isn't really a problem, as I've said I usually type up my drafts in an editor to create a file a little like this wiki example. As Markdown is fundamentally a text file it's easy enough to cut and paste the markdown text into the standard notes application to make a new text note.

For me, as the idea of using markdown is to improve readability (basically all I use is indenting and section titling) pasting the fie as a text file works fine. If you do some clever things in your note taking, this probably won't work for you.

So, it's a competent product. Out of the box it has some restrictions and limitations, and if you want a full featured note management application, you might want to look elsewhere. As an application for managing working notes in text format it's fine. It does everything that you would expect.

And, unlike its big brothers, it's available for linux.

I would however like to have a 'try before you buy' evaluation mode for the various extensions to be able to explore its capabilities more fully.

But, if you need a competent note taker and management application for text based notes, standard notes might well do the job, especially if you are a linux user ...

Saturday, 17 March 2018

And now, an old Thinkpad

My old Dell Inspiron that I've used since 2010 is finally reaching the stage where it's running out of puff, not disastrously, but getting to the stage where one would start to think about replacing it.

Of course I could just put up with it's huffing and puffing and use my MacBook Air as a day to day machine, but I'd reached the stage where a new Windows machine seemed like a necessity.

The only problem was that we'd just paid out for a trip to Borneo, and I really couldn't justify the extra money right now.

Well, I'd always half planned to buy myself an ex-lease Thinkpad for Linux work, so after a little bit of agonising I bought myself a X230 with Windows 7 professional license, reasoning that I could use it as a windows machine, and perhaps even convert it to dual boot - Windows 7 and Linux, for the simple reason that the documentation project I've volunteered for is built around windows, meaning I need One Note, and that most of the rest of my personal notes and documentation is in Evernote, which again is not available for Linux.

So I paid my two hundred and thirty bucks to one of these companies that refurbish ex-lease machines and a few days later it arrived, beautifully packed in shock absorbing packaging and with a refurbisher's test report, and nicely imaged with a clean copy of Windows 7 with an install of Open Office 3 thrown in.

Out of the box, battery life was better than my Air, which realistically manages about two hours work these days between charges. The Thinkpad claimed a realistic four hours thirty out of the box and the what's more the battery is easy to replace down the track if needs be.

So, installing things.

First off were the standard utilities that I use:

  • Focuswriter - for distraction free writing
  • Kate - for when only a text editor would do
  • Open live writer - an open source clone of windows live writer for bloggin
  • Tweeten - a desktop twitter client
  • Gnumeric - spreadsheet for data manipulation
  • Libre Office - when I need to write something and format it nicely
  • Thunderbird - for email and calendaring
  • Texts - for wysiwyg markdown editing

And then it was the data intensive things

  • Dropbox - for data sharing
  • One Drive - cloudy filestore
  • One Note - Microsoft's note management tool which has all my project documentation
  • Evernote - which basically contains my entire life, invoices, bills, research notes and so on

All in all, close to 40GB of data to download, which took around a day with a few timeouts when we wanted to watch the morning news on iView, or actually use the internet. Given that our internet and phone plan has a stupidly large cap ( a terabyte of data per 28 days - effectively it's unlimited, we usually only use around 10% of it) I wan't worried by the download size..

Also given my general interest in note taking applications I installed Standard Notes for fun, and I should probably also install the windows version of CherryTree given that I waxed lyrical about it a few months ago.

It might have been quicker, but windows also wanted to download a zillion patches (actually a little over 200) and apply them, all of which took time out of the process.

At the end of it I've a machine with reasonable battery life, a decent form factor for working on the train and these silly little tables.

I havn't installed virtual box yet, but I'm planning to do so to build a virtual machine to put together a prototype Omeka site to showcase the project so far.

Sooner of later I'll probably add a couple of extra applications - such as the Gramps family history tool.

The only Linux software I really need is tesseract and cuneiform for OCR work on pdfs from old printed documents and they'll run equally well in a Linux VM.

So, next steps.

Basically use it, and keep the old Inspiron for backing up data from documentation project.

I do face a decision down the track as to whether I keep the machine, or migrate it to linux as originally intended. If I keep the machine I probably need to think about an upgrade to Windows 10, but for the moment seven is good enough. After all it's the software base that's important, not the operating system...

[update 18/03/2018]

... and this morning I was looking up some references and discovered I'd totally forgotten to install my preferred refernce maneger - Zotero, doh!

Wednesday, 7 March 2018

Lecture recordings and intellectual property

There's a strike over pensions in the UK university system at the moment and it's brought to light an interesting little argument over intellectual property.

Obviously, if a lecturer is on strike, a scheduled lecture is not going to be delivered. Some universities have tried to force lecturers to deliver cancelled lectures once they return to work, or persuade non striking colleagues to deliver them with varied degrees of success.

But some have tried a different tack, giving students access to the lecture recording of the previous years lecture.

Lecture recordings vary. Some simply record voice or else voice and video somewhat in the style of nineteen seventies Open University recordings. Others record voice and the accompanying powerpoint slides.

Lecture recording systems are usually touted as a revision aid for students, or else as allowing students at multi site institutions access to material delivered at another location. Cynically, it allows students who discover Statistics 1B is timetabled for 0830 on a Monday an extra hour in bed.

Individual universities rules on intellectual property and lecture content all differ slightly.

In many cases they were drawn up  some years ago before lecture capture systems were in widespread use, and before the world went digital.

In some cases the university owns the teaching material, some cases the individual owns it, and in some cases the lecture is owned by the university, but handouts, including the powerpoint slides, are owned by the individual.

And some lecture recording products have terms of use that require consent by the lecturer before the material can be reused. And of course there's the case where a teaching assistant delivers a lecture using existing notes and material when the lecturer whose course it is is on sabbatical. We won't talk about MOOCs here, but that's another problem, especially if material from other lecture courses is reused.

Basically it's a very grey area. In fact once you start to poke into it it's a complete nightmare ...

Friday, 2 March 2018

When an isbn isn't really an isbn...

Now we all know that isbn's are persistent identifiers par excellence, but I recently came across a case where they weren't

I'd bought a version of Valentine Baker's Clouds in the East, the book he wrote while imprisoned for his assault on Miss Dickinson, as part of my reading about the Great Game.

I'd bought the reprint from one of these Indian print on demand companies that reprint out of print out of copyright nineteenth century books.

Unlike some of these reprints this one came nicely bound with a card, as opposed to paper, cover and had a barcode, an isbn, and a suggested price in both Indian Rupees and US dollars, in other words rather than print on demand it looked like one of batch produced for retail sale.

So I entered it into LibraryThing - no such ISBN. Now I know from past experience of having bought books from India that they usually in Amazon's database, so I was a little surprised.

I tried Amazon India directly - no such luck. Neither was it on or, so I'm guessing it's an invalid isbn generated by the publisher when packaging the book up to make it look like a 'proper' retail copy.

Strange, hadn't come across that before ...

Wednesday, 28 February 2018

Working in a really small public library ...

Today on the documentation project I was chased out for an Hour or so when we had a large tour group come through.

It was too early for a coffee, and I had some notes to write up, so what to do?

It wasn't worth going home, but then I had a brainwave. I googled local library, and discovered there was a local branch library in the town, and it was (a) open and (b) had wifi.

I've written before about working in larger public libraries, but this wasn't the case here - this library was basically a largeish room like a conference room in an old local government building and didn't really have much in the way of workspace provision - just a couple of comfy chairs and an old table with a couple of desktop computers.

But they did have wifi - which claimed to be 5G, and had been moved from some other library as it still had the old name as the SSID, but it worked, or at least it did once I asked the library staff to reset the router for me - apparently a known problem.

I don't actually know what they were using, from my view of it it was a standard looking wifi router -  how it was connected I don't know but I guess over whatever infrastructure the local library corporation provides - I'd guess ADSL.

As a working experience,  it was really good - quiet, I could get my work done, no background clamour of coffee making and enough space to sit comfortably if unergonomically with my laptop on my knees, and notebook on the chair adjoining.

So next time you need a place to sit and use wifi, think about (and support) your local public library!

Tuesday, 20 February 2018

Provenance - it's all about provenance

Six months ago, on a plane between Singapore and Melbourne, I watched a remarkable documentary about the attempt by the city of Detroit to sell off the contents of its art museum to defray the city's debts.

The scheme ultimately foundered - because of provenance.

One of the original founders of the museum apparently used to go on collecting tours of Europe, buying paintings from cash strapped aristocrats who had lost everything in the first world war - so you would think it would be easy to work out provenance.

But, no. The person in question was an art collector in his own right, and while he would sometimes use the museum's money to pay for items, sometimes he would use his own, and sometimes he would 'sell' a piece to the museum at below cost and claim it as a tax loss.

And the records were a complete mess.

It wasn't clear which had been bought on behalf of the museum, which were on loan, and which were donations - and of course the more saleable paintings' records were as confused as the less valuable.

In this case having an unclear provenance worked for the museum - they couldn't sell what wasn't theirs, and the didn't know what wasn't theirs.

And I suspect that this is the case with a lot of museums who developed their collections in the late nineteenth and early twentieth century - the documentation is quite unclear.

Not for everything of course, for example the Elgin Marbles have a clear provenance and the case really depends on the legality or otherwise of Elgin's actions and whether his firman from the Ottoman governor really gave him permission.

But then we have cases like the Nizam of Hyderabad's mummy, which I blogged about back in 2015, where provenance is unclear, we know he bought it, but not if it was illegally acquired. Likewise in Amelia Edwards' account of her trip up the Nile in the 1870's, she recounts the story of the tourists who bought a mummy at vast expense, and after a week or so found that they could not stand the sweet odour emanating from it, and (literally) jettisoned their losses by throwing it in the Nile.

And this all makes the problem of artefacts acquired during the period of European colonialism.

Were the items acquired legally, were they acquired under duress or what.

And of course rules change. Egypt, for example started to license archaeological digs quite early and had clear rules about both documentation and ownership - basically that the more significant items were automatically property of the Egyptian department of Antiquities, which is why so much of the material is in the Egyptian Museum in Cairo, but as we know, there are significant collections elsewhere, and as the Nizam of Hyderabad case shows us, the system was not perfect.

Other countries, especially those under colonial rule, were not so strict.

And for this reason, probably one thing that should be done is to digitise the museum records and correspondence, as well as that of individual archaeologists and collectors, to both settle the question of provenance, but also to provide an unrivalled insight into the history of archaeology, and it's relationship to the antiquities trade in the nineteenth century ...