Unofficial Calibre help file seeks feedback
June 24, 2012 | 11:00 pm
By Chris Meadows

Calibre is one of the only good open-source options for managing your e-book collection, but we all know it’s notoriously user-unfriendly. On one of the mailing lists I follow, I’ve heard from Becca Price, who is trying to do something about that. She is compiling a help file for Calibre as part of a class she was taking on how to develop help files.
Becca notes that this is an entirely unofficial project, and “isn’t even quite a beta draft.” And the sound file on the “About Calibre” topic does not work reliably (apparently it works on Macs but not PCs) has since been removed. And if the site is down when you try to access it, it is because she is replacing the old file with a new one, which takes about half an hour, so try back later.
She would appreciate any comments or feedback about what is helpful, what is not, and what still needs to be added.
(Bumped for more attention Monday morning.)



Previous

SUBSCRIBE TO RSS
Comments:
I took the sound file out – it was just too unreliable.
Feedback: There is big error at the very beginning of the post.
Calibre isn’t notoriously user-unfiendly. There are many of us that think that Calibre is extremely user friendly. So the sentence “… but we all know it’s notoriously user-unfriendly.” is wrong on several levels.
Calibre interface is very intuitive and lets you do quite complicated things without having to consult the manual. For the vast majority of things that a beginner might want to do, there is easy intuitive graphical interface. There are lots of things that automated and automagicaly set with a very reasonable defaults.
Calibre also lets you do very, VERY advanced things, like use Regular Expressions, define metadata plugboards, compound columns, it lets you define “save to disk”, or “import from file” templates using many, many fancy regular expressions, custom columns computed from metadata and other things.
You find it intuitive, but I suspect you’re already a pretty advanced computer user.
“User-friendly” means that people who don’t know where the “any” key is are able to figure out how to use it. And looking at it from the perspective of such an ordinary user, I stand by what I wrote.
You do know that the “any key” business is pretty much just a joke? It plays off the significant difference between pressing “any key” and pressing “the any key”. It’s humor.
I’ve worked with a lot of computer newbies and nobody has ever squinted at their keyboard in search of a specific key labeled “any”.
Calibre is a remarkably powerful and relatively easy to use program. Anybody who has spent any time at all with any program beyond a web browser should be able to puzzle out how to load books, tag them, convert them and then search for them.
I’m baffled by the concept that calibre is “hard to use”.
I did a fair amount of user research before starting my help file. What I found is, that while Calibre by itself isn’t all that hard to use, it’s so powerful that people who are not high-level compute users can feel daunted by some of the options (what’s a recipe and why would I want to use one? what’s a heuristic? All I want to do is convert my files!).
Dear Chris.
Please read what I wrote.
I didn’t say that there aren’t any people that consider Calibre difficult. I personally know people that aren’t able to send an SMS from their own, very simple mobile phone. So there are bound to be people that find Calibre difficult. On the other hand, there are people that find Calibre very easy and user friendly.
So your sentence “but we *all* know it’s *notoriously* user-unfriendly” is still wrong on several levels.
so other than quibbling about the wording in the article, has anybody looked at the help file itself?
I found it to be far too presumptuous about readers knowledge of terminology and at the same time too simplistic in it’s instructions.
Need a hell of a lot of work to make it useful.
Howard – this is exactly the kind of feedback I need. What terminology needs further defining?
I agree that some of the stuff (adding books, etc) is overly-simplistic. I think that, if there is any value to this, it comes in the tweaks and reading list sections. As I said, this is a file for beginners. I’ve patterned the procedures off what I’ve seen friends need as I introduce them to calibre and ebooks for the first time.
User unfriendly? People really do expect the computer to do all of their thinking for them nowadays.
becca that would take too much time and work.
You need to read through it as you write it, and put yourself in the shoes of someone who is getting into eBooks but is not a computer person. Imagine they are a real person, say a women who works in Walmart and who has a PC at home where all she does is browse and send email. Imagine they are sitting next to you.
To look at one case .. the section on ‘converting’. What on earth does ‘converting’ mean on it’s own ? Nothing. It should be ‘converting from one format to another’ …. because …. formats are important ? ……
You assume too much knowledge by the reader, which is understandable because you have that knowledge.
As a Mac user of many years I would describe Calibre as very user unfriendly. It falls far short of most good mac software, perhaps PC users have a lower level of expectation.
If they spent more time working on their interface and less on their obsessive biweekly updates, it would be a much better app.
The help seems to be, at the moment, more like a skeleton for writing manual waiting to be fleshed out. For the most items is simply lists options as they appear in the menu.
Let’s have a look at “Adding books”
————————-
There are three primary ways to add multiple books at one time:
From a single directory
From multiple directories within a single higher-level directory, where there is only one book per lower-level directory
From multiple directories within a single higher-level directory, where there are several book per lower-level directory
—————–
So, what exactly has user learned here, apart from the fact that there are three choices, that should be obvious from a look at the menu?
I would expect a description of each item, with an example of book listing.
For choice 2 and 3 I would expect to learn that if there is an *.opf file that carries the info about book metadata and Calibre and that Calibre will try to import that data. I would expect to learn that user can configure Calibre to read metadata from the inside of ebook file or from the file name.
You can also describe that this is the way a part of the library from other installation of Calibre could be imported.
You can also describe that there is a powerful plugin that lets you choose between several templates for parsing the file name called “quick preferences”. You should definitely touch topic of templates for reading the metadata from filename, including a few choice Regular Expressions with templates, such as
(?P.+) – (?P[^_]+)
or even
^(?P((?!\s-\s).)+)\s-\s(?:(?:\[\s*)?(?P.+)\s(?P[\d\.]+)(?:\s*\])?\s-\s)?(?P[^(]+)(?:\(.*\))?
– analysis of the above RE is well out of scope of this manual, I think, but you might want to explain where to find more info and that there is a configuration panel where user can play and test various options.
In “Customizing the user interface” chapter you should mention that icon bar (that many find strange) can be replaced with a menu, by going to Preferences, Interface, Toolbar, removing of all icons from “The main toolbar” and putting items to “The menubar”
The structure of the manual is great, if you plan expanding each section to take up at least a few screenfuls of text. If you wish to keep chapters short, you should consider putting it as one long text with hyperlinked TOC at the left. When I read an user manual – and I *love* reading manuals – it quickly becomes very tiring to click on the new link for a few new lines of text.
At least give the user a chance to download the entire thing as one long text for printing out, or putting into a reading device.
I will comment more later
It’s a balancing act. You’re writing for people like “(name) required” here who reads manuals for fun, but you’re also writing for task-based readers who just want to get to a section, figure out how to perform an action, and get out again. They don’t need a treatise, they need to solve a problem. Technical writing is about conveying depth using brevity.
You’ve taken on an ambitious, highly useful project Becca. Thanks for your hard work, and good luck! Remember, you’re never going to please everybody.
Name (required), are you willing to contact me off-list and discuss your ideas further? I’ve made some of the changes you suggested, but I’m confused about the template for reading data from the filename stuff you talk about, and templates. Are these things a casual (not power) user would need to know about?
Preston, you’re right – This is a Caliber for Beginners document, and the intention is to provide simple, task-based procedures for people who don’t care particularly about the in-depth “whys and hows” (there’s plenty of good documentation for them) but just want to get some useful things done.
becca – I wasn’t invited but my hotmail account has the username “saoir”. I’d be happy to pitch in.
If anyone wants to communicate with me directly, my student email is
rprice (at) wccnet (dot) edu
Howard, I’m not sure how to use hotmail account names.