DEV Community

Cover image for Modelling a music scene as entities, not as a blog dump
Spicanet
Spicanet

Posted on Edited on Originally published at dropthebass.co

Modelling a music scene as entities, not as a blog dump

If you only glance at DROP THE BASS, it can look like a music site with a lot of sections. The more accurate description is a portal, running since 2002, whose public catalogue is built around entity types — artist, label, release, rave — with a subgenre vocabulary and a separate editorial layer. The catalogue is compiled from public music and event sources and editorially curated. This is about that model. It is not a pipeline disclosure, and it is not a claim to have ingested any particular commercial platform.

The about page states the shape in plain terms: artist profiles (DJs, MCs, producers), labels and promoters; releases, mixes and videos; raves; news and other editorial. An MC, here, is the host of a night, not automatically “the rapper.” A selector is the person choosing the music. Most pages are readable without an account. A login exists for a junglist profile — “junglist” meaning someone in jungle and drum & bass culture, not a tropical-travel tag — plus follows and saved items.

Jungle and drum & bass are related on the site and are not treated as one word. Jungle is a style and a culture, not a rainforest aesthetic and not a synonym for every track in the 170 zone (the informal name for the usual tempo, around 170 BPM). Subgenre pages further split the field — liquid funk, neurofunk, jump-up, halftime and others — as a browsing taxonomy whose borders remain disputed. The site should be used that way, not as a canon.

The artists index is one concrete slice of the entity model: people pages that can connect to releases, labels and, where listed, nights. This article does not invent a headcount or a size claim for the roster. The useful fact is the type: an artist is a first-class object, not only a string on a track title.

Dubplates are another type, and the FAQ keeps them distinct from demos. On this site a dubplate (sometimes just “a plate” or “a dub”) is a public-catalogue item: a standalone tune, a VIP or unreleased pressure, synced from SoundCloud. A demo is private, sent to a label that has claimed its page. Raves, similarly, are published through promoter, venue or festival profiles, not asserted here as a silent scrape of every event site. Once live, a rave can also appear on the relevant city page. Anything more specific about ingestion is not on the about or FAQ pages, so it is not stated in this article.

Mixes and videos follow the same attachment pattern: their own sections, still linked to artists and labels rather than living as an unrelated media dump. Editorial pages — news, and a smaller set of long reads and guides — sit beside the entity graph, not in place of it.

The same model is what you meet on a city page or a festival listing: those are views onto rave entities, not a second unofficial website. Coverage is uneven because a night only appears once it has been published through a profile. A gap is usually a publishing gap, not proof that a city has no scene. The public FAQ is the source for that publishing path; this article does not add unofficial workarounds. If you are used to thinking in records and relations, that is the whole point: curated entities, a contested vocabulary, and a public/private split for plates versus demos. No rankings, and no implied completeness.

For the front door, use DROP THE BASS. The about page, the artists index and the dubplates catalogue are the three places to test what this article has just described.

Top comments (0)