user warning: Unknown column 'captcha_type' in 'field list' query: SELECT module, captcha_type FROM captcha_points WHERE form_id = 'user_login_block' in /var/www/drupal/sites/all/modules/captcha/ on line 64.

Project Plan Post 6 of 7: Projected Timeline, Workplan & Overall Project Methodology

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)


Project Plan Post 5 of 7: Project Team Relationships and End User Engagement

The project team consists of Simon Dixon (PI), Mark Sandler (CI) and Kurt Jacobson (RA) from the Centre for Digital Music (C4DM) at Queen Mary University of London. C4DM is a world-leading multidisciplinary research group in the field of Music & Audio Technology. C4DM has around 50 members working on signal processing of digital music, music informatics, machine listening, audio engineering and interactive performance. Research funding obtained since 2001 totals over £14m, mainly from the EPSRC and EU.

Project Plan Post 4 of 7: IPR (Creative Commons Use & Open Source Software License)

The MusicBrainz database contains two types of information. The core data, consisting of factual data such as the names of albums, tracks and artists, is in the public domain. The remaining data, such as annotations, tags, opinions and ratings are protected by the Creative Commons Attribution-NonCommercial-ShareAlike 2.0 licence, which allows non-commercial use of the data under the conditions that MusicBrainz is given credit and that any derivative works are also made available under the same licence. Thus the linked data published by this project will follow the same licence arrangement. In particular, this allows the outputs of the project to be used freely in teaching and research.

Project Plan Post 3 of 7: Risk Analysis and Success Plan

The success of the project can be measured in immediate terms by semantic web traffic: the number of web site hits with an "Accept RDF" header, or the number of distinct users connecting to the SPARQL endpoint. In the longer term, the use of MusicBrainz URIs in third party tools and services,
and eventually new studies (enabled by being able to query the linked data) will also indicate the success of the project.

We have identified a number of risks, which are listed with mitigation actions:

1) The MusicBrainz user community votes against the proposed changes
(Likelihood: Low; Impact: Medium)

Project Plan Post 2 of 7: Wider Benefits to Sector & Achievements for Host Institution

In making music metadata available on the semantic web, we are addressing the needs of two primary types of user in the HE sector: (i) those working in the Music Informatics (or Music Information Retrieval) community, primarily in computing and engineering departments; and (ii) musicologists and musicians working in music departments. This is in addition to the (sizable) international MusicBrainz user community, who also stand to benefit from the linking of their data to other semantic web resources, as well as software developers working with on-line music services, and their users, who will indirectly benefit from this project.

Syndicate content