LinkedBrainz

Discussion at JISCexpo Programme Meeting

Present: Barry Norton, Cedric Mesnage, Joe Lambert, David Bretherton, Simon Dixon

Identifiers for musical works
- Too much for one project -> crowd-sourcing
- Build on MusicBrainz infrastructure?
- Use MusicNet's alignment tool to clean up MusicBrainz (MB)
- or do the MB editors do a good enough job?
- do we need to involve musicologists in MB as super-editors
- MB only covers recorded music
- Involve publishers for scores without recordings?
- BBC Radio 3 data (Nick Humphrey?)

Bootstrapping issue to attract people to site (cheese)
- does MB already provide the right interface? could write a plugin for Picard
- is there any conflict between MB's sustainability and our specialist needs
- discography = cheese

Title of Primary Project Output: LinkedBrainz Live!

The type of user this product is for: LinkedBrainz Live is for application developers and institutions who require or use information about recorded music. Especially if thes require to interlink datasets or benefit from inference via automated reasoning.

Last Friday (2010-10-22) members of the mSpace MusicNet team met with the LinkedBrainz team at Queen Mary University of London.  The MusicNet Project aims to disambiguate classical composers across a series of resources and publish the results as linked data.

1. Directly Incurred (Total £47239)
• a) Staff Postdoctoral RA £41588
• b) Non-staff
  Travel and expenses £2200
  Hardware/software £1451
  Dissemination £2000
2. Directly Allocated (Total £24619)
   Staff £11133
   Estates £12550
   Other £936
3. Indirect Costs (Total £46759)

Total Project Cost = £118617, consisting of:

Funding from JISC: £94894
Institutional contributions: £23723

The work of the project is divided into 5 work packages (WP), three of which cover the technical work and one covers each of dissemination and management.

WP1: Convert MusicBrainz to linked data (Months 1-6)