Friday, 14 October 2011

Digital humanities, music and the Material Text

Yesterday's Seminar in the History of Material Texts was given by Professor John Rink under the title 'The virtual Chopin'.  I often go to the seminars, but rarely write them up here.  This time I will, because I'm on a blogging roll, and because I do after all have a degree in music and therefore actually understood the ins-and-outs of the talk and discussion.

from Wikimedia Commons
What's the issue?
Editing the works of Chopin is a tricky business.  Each work is likely to exist in multiple sources, and these sources generally don't agree with each other.  Types of source include:
  •  preliminary sketches
  • reject public manuscripts
  • Stichvorlagen (copies from which music engravers created the plates to print from)
  • proof copies
  • 1st editions
    • These were usually simultaneously produced in England, Germany, and France, for copyright reasons.
      • Getting exemplars to three separate publishers happened in different ways through Chopin's life: sometimes proof sheets from one were sent to the other two, sometimes copies of one autograph MS would be made by an emanuensis, and at the end of Chopin's life he would make three copies of the MS himself.
    • They were printed in very small numbers at a time (25-100 copies), and corrections could be made after each run, so there are very many varying impressions of each edition.
  • Other autograph sources, such as music written in visiting books or given as gifts to patrons
  • Other non-autograph sources, such as pupils' annotations on printed copies.
Why does that matter?
The result of this multiplicity of sources are that it's not easy for editors and performers to determine what is the 'right' version.  If the French and English first editions have different notes in them, how do you choose which to print and which to play?

Rink identified a few places where copying or engraving errors have serious aural and structural implications for the music, most notably, the mistaken placement of a repeat sign in the first movement of the B-flat minor sonata.  The standard reading has the repeat marked as starting from bar 5, but Chopin's MS shows only a double bar here (no repeat dots) - the repeat should start from the very beginning of the movement, which makes a lot more harmonic sense.

A way through the thicket
It will be little surprise to hear that there is no 'right' answer to the question. Particularly in the case of Chopin, whose compositional methods and style are heavily influenced by performance and improvisation, a single definitive version of a work simply can't be pinned down.  But there are ways of helping to decide what you should do:
  • no source should be considered in isolation
  • don't take the contents of the source at face value: interpret them in context
  • the 'law of averages' is likely to be inappropriate: just because 7 sources have one thing and 1 has something else, that lonely 1 might be more 'valid' than the others.
  • multiple interpretations may be valid, even though you can only perform one at a time.

Editors vs performers
The solutions will be different for editors and performers.  Performers can only play one version of any given bar (or beat, or chord) at a time.  They *have* to choose--and they generally don't like to, wanting to be able to play the 'right version--but are also at liberty, if they can justify it on musical and historical grounds, to choose as they please (and perhaps even different version at different parts of a work).  Editors, however, have a responsibility to give the full picture, as far as is feasible.  In the case of the multiple variants of Chopin, it's pretty hard to show them all on a printed score.

The digital bit
Digital technology obviously ways of presenting all the variants that cannot be allowed for in print publications. Rink leads two research projects with online outputs:
The second allows the side-by-side comparison of individual bars from manuscripts and first editions.

It's amazing, and somewhat overwhelming, for the lay (or lay-ish) person to be able to compare all these different versions.  But it's certainly a good thing.  Without being overly flashy, or getting caught up in theory or grand claims, this is a very useful thing.

And that's pretty much all I have to say.
Screenshot of opening of Ballade no. 3 in A-flat, Op. 47. Note that the first printed bar (1st impression of French 1st edition) has a missing flat in front the the second D, which is corrected in the next image, the 2nd French impression.

Thursday, 13 October 2011

#libcampuk11 session 4: using wikimedia to improve access

(Library Camp UK 2011 home | my other posts about it)

In this session Andy Mabbett introduced us to ways of using wikimedia (the parent organisation (owned by the Wikimedia Foundation) to Wikipedia, Wiktionary, Wikimedia commons, etc.).  Andy is a real evangelist for making the most of wiki* to benefit your own organisations or products.

GLAM (Galleries, Libraries, Archives and Museums)
Wikimedia is actively seeking to encourage collaboration from heritage organisations, as you can see from the GLAM outreach wiki. Andy described a 'backstage pass event' he'd been to at Derby Museum and Art Gallery. Wikipedia editors had been invited along to a day's event, to have talks and tours about and around the museum, and a cup of tea and a biscuit, all with the aim in getting more coverage of the museum and its holdings.  Andy pointed out that by doing a little to make people special, they will do lots in return: 1,200 new articles (and translations) were created as a result of this one-day event (including this one about a racing pigeon).

There are all sorts of potential events that you can run to engage the local community, or the community of wikipedia editors, that will benefit your organisation in terms of improved visibility.

Putting stuff on wiki*
There are two criteria for including an article on Wikipedia:
  1. it must be about a notable thing - i.e. something that's written about elsewhere
  2. you have to cite what you say - you can't include original research or unsupported statements.
This leaves a lot of scope for GLAMs to include articles about themselves, their collections and their notable holdings.  You can't have an article (or links to) every single hand axe in the country, but if you're is significant, or you have a copy of book that exists in very low numbers, than that's worthy of inclusion.

You can also release images, video, audio and animations on Wikimedia Commons.  It's good to release material with a licence allowing reuse with attribution - and then your pictures can be used anywhere, and will link back to your organisation. 

If you have a large volume of images, Wikimedia can help with batch imports, and they maintain their servers so that the images are preserved.  In addition, the pictures are now available to all sorts of people who'll be able to help identify them and items in them.

QRpedia (intro | intro on GLAM wiki | actual site)
QRpedia is a doohickey that makes QR codes to link to Wikipedia pages. When someone scans the code, QRpedia return the wikipedia page in the phone's language where possible (interesting discussion of 'difficult' languages here).  Why is this cool? It means that visitors can get information about things in your exhibition in their own language without you having to make three hundred different signs.  Obviously, if you link to a very specific page there will be fewer language options that a very general one, but translations are increasing all the time...

Homework
We were encouraged to sign up for an account and to start editing Wikipedia pages, for example by correcting punctuation or by translating an article (e.g. into Simple English) (Andy suggested hitting the 'random article' button until you found something that needed tidying up).  I've set up my account, and have done my first editing (a very undramatic addition of a link at the end of an article).

Thoughts
I found this session really useful.  Wikipedia is out there, and the very thing that means that some people view it as shady and disreputable is the thing that makes it powerful for us: we can edit it.  I think it's a great idea that organisations use Wikipedia to improve their online presence: people will be looking us up there, so why not give them good information, and decent links to our own sites?

However, I can imagine that selling the use of wikipedia (e.g. via qrpedia as a help to visitors) might be difficult to sell to the organisation... or it might be seen as lazy.  Do other people think it's something they could get agreement to do?

And finally...
For those interested in that sort of thing, there's also a linked-data-y DBpedia: "a community effort to extract structured information from Wikipedia and to make this information available on the Web"

Wednesday, 12 October 2011

#libcampuk11 session 3: Enabling reuse of library/catalogue data

(Library Camp UK 2011 home | my other posts about it)

This session was facilitated by Owen Stephens, who does lots of digital library stuff, is involved in mashedlib events, and is lovely. (He could probably write a better bio than that, though.)  I'm really keen to learn more about the techy side of librarianing, so I was really pleased to see him offer this session.  It was very interesting - and I've come away with an idea for something that would made catalogues more useful for some rare books users, and lots of places to start finding out more.  My notes are a bit sketchy - a lot of links and a few ideas. Sorry about that.

The issues Owen said he hope to discuss in the session were "How do places with data interact with people who want to use it?" and "How do we make data available?".

Why do organisations publish data?
  • Accountability: by releasing data people can see what's been done and for how much money. Etc.
  • To increase the available services. 
    • People 'out there' will be able to do things that you don't have the resources to do yourself.
    • They'll also think of better things to do with your data, and by combining your data with data from other places.
    • An example that covers both of these is the public toilet map.
  • NB, the government is currently consulting on what data Local Government should release: Making Open Data Real
What does this have to do with libraries?
Library catalogues have imposed on them librarian- or supplier-made decisions about what can/can't be searched and in what way.  Some of these decisions are limited by current cataloguing rules, but not all; often the data is recorded, but not in a usable way, or is there but isn't tapped by the intereface.  For example, in most catalogues you can limit by publication type to newspapers, but you can't limit by frequency of the issues.  Releasing data means that people can start to use it in the way they want to.

Releasing data: issues
Different uses will require different kinds of data release.  To work on the newspapers query above, a dump of all the MARC (i.e. cataloguing) information would be OK.  But for an app using circulation data you'd need to use a live API.
Data protection is obviously a big issue for some kinds of data.  But it's not a deal-breaker.  You can base locations on postcode zone, not individual postcodes for example, or for course-based datasets (in a uni context), just not include data from very small courses.

Useful links