Semantic Web Company
Menu
Open
Close
Menu
  • Home01
  • Solutions02
    • backSolutions
    • Search & Analytics02
    • Recommender Systems02
    • Digital Transformation02
  • Products03
    • backProducts
    • PoolParty Semantic Suite03
    • PoolParty PowerTagging03
  • Company04
    • backCompany
    • About us04
    • Leadership Team04
    • Partners04
  • Careers05
  • Learn more06
    • backLearn more
    • Research06
    • PoolParty Academy06
    • SEMANTiCS Conference06
    • Company News06
  • Legal07
    • backLegal
    • Imprint07
    • Privacy07
    • Terms of use07
  • Contact us08

Learn more

  • Apr 9, 2015

Transforming music data into a PoolParty project

  • Nolde, Thesaurus Building, Uncategorized

Goal

For the Nolde project it was requested to build a knowledge graph, containing detailed information about the austrian music scene: artists, bands and their music releases. We decided to use PoolParty, since theses entities should be accessible in an editorial workflow. More details about the implementation will be provided in a later blog post.

In the first round I want to share my experiences with the mapping of music data into SKOS. Obviously, LinkedBrainz was the perfect source to collect and transform such data since this is available as RDF/NTriples dumps and even providing a SPARQL endpoint! LinkedBrainz data is modeled using the Music Ontology.

E.g. you can select all mo:MusicArtists with relation to Austria.

SELECT query

I imported LinkedBrainz dump files and imported them into a triple store, together with DBpedia dumps.

With two CONSTRUCT queries, I was able to collect the required data and transform it into SKOS, into a PoolParty compatible format:

Construct Artists

CONSTRUCT Artists#1

Screen Shot 2015-04-10 at 10.53.36

Every matching MusicArtist results in a SKOS concept. The foaf:name is mapped to skos:prefLabel (in German).

As you can see, I used Custom Schema features to provide self-describing metadata on top of pure SKOS features: a MusicBrainz link, a MusicBrainz Id, DBpedia link, homepage…

In addition you can see in the query that also data from DBpedia was collected. In case a owl:sameAs relationship to DBpedia exists, a possible abstract is retrieved. When a DBpedia abstract is available it is mapped to skos:definition.

Construct Releases (mo:SignalGroups) with relations to Artists

Screen Shot 2015-04-10 at 10.59.50

Screen Shot 2015-04-10 at 11.00.10

Similar to the Artists, a matching SignalGroup results in a SKOS Concept. A skos:related relationship is defined between an Artist and his Releases.

Outcome

The SPARQL construct queries provided ttl files that could by imported directly into PoolParty, resulting in a project, containing nearly 1,000 Artists and 10,000 Releases:

PoolParty thesaurus

 

You can reach the knowledge graph by visting the publicly available Linked Data Frontend of PoolParty: http://nolde.poolparty.biz/AustrianMusicGraph

E.g. you can find out details and links about Peter Alexander or Conchita Wurst.

Share on twitter
Share on linkedin
Share on whatsapp
Share on email
PrevPrevious post
Next postNext
ALL POSTS

Twitter

@semwebcompany

RT @PoolParty_Team: Ready to learn an entirely new approach to content development and distribution? Don’t... Read More

Jan 30 2023, 1:38 pm
@semwebcompany

Michael Iantosca and @nagyhel discussed “Big Content & #KnowledgeGraphs” at the recent #Semantic #Content Graph... Read More

Jan 27 2023, 10:03 am
@semwebcompany

RT @PoolParty_Team: Get ready for the PoolParty Summit 2023! Register now and join us from... Read More

Jan 25 2023, 1:55 pm
More
  • Twitter
  • Linkedin
  • Youtube
  • Xing
Scroll Top

2023 © Semantic Web Company