Search results

From MusicBrainz Wiki
Jump to navigationJump to search
  • : The REST-based webservice API for direct access to MusicBrainz data with output in XML and JSON (Please review the libraries above before writi ...tabrainz/mmd-schema/blob/master/schema/musicbrainz_mmd-2.0.rng XML RelaxNG schema]
    4 KB (539 words) - 14:06, 28 October 2023
  • * Are looking to switch to NGS schema by the end of the year ...would like to use MBIDs internally to make communication between incoming data sets easier
    13 KB (2,006 words) - 00:33, 1 May 2014
  • ...stable I'll ask for feedback on what we should do next. I also started the schema change process and setup calendar.musicbrainz.org with ianmcorvidae. we've Decision is to wait until October 2013 schema change to drop the PUID data from the database.
    5 KB (800 words) - 21:48, 4 February 2013
  • ...hip hop"). This is where some familiarity with Postgres (coming up with a schema) will come in handy. ...ing this would require a lot of changes however, not only for the database schema, but also in the web service, our tagger Picard, and other things using the
    6 KB (1,012 words) - 22:16, 9 February 2017
  • ...new data repository. This is intended to bridge the gap between a top-down data stream from a label and a bottom-up community like MusicBrainz. Overall the year was somewhat quiet and normal; we had the usual 2 schema change releases and a good Summer of Code. We had our annual summit and too
    20 KB (3,043 words) - 12:46, 25 July 2014
  • You will set up Solr for use with Bookbrainz' schema, drawing inspiration from existing MusicBrainz code. ...entities (as described [https://lucene.apache.org/solr/guide/6_6/uploading-data-with-index-handlers.html#UploadingDatawithIndexHandlers-JSONFormattedIndexU
    7 KB (1,133 words) - 11:51, 20 March 2019
  • ...nBrainz. You could make up some fake data for song names and artists. This data doesn't have to be real. ...d delete the ListenBrainz database on your local server to remove the fake data that you added.
    15 KB (2,483 words) - 12:55, 11 April 2022
  • ...h links to Amazon. Until the [https://blog.metabrainz.org/?p=9463 May 2022 schema change] it was only possible to change/add the cover art by adding an [[Adv ...tiple differing sources. Especially if you don't know if a last track is a data track: mostly those are not linked to sound samples while the other tracks
    4 KB (715 words) - 05:50, 16 June 2022
  • ...server. You could make up some fake data for song names and artists. This data doesn't have to be real. ...d delete the ListenBrainz database on your local server to remove the fake data that you added.
    20 KB (3,240 words) - 17:34, 1 April 2023
  • ...sure how much I have to say :) I have patches in the pipeline, considering schema changes, carrying on as usual :) ...d into caching oddities on beta.mb, increased test coverage in musicbrainz-data (nes), did a lot of reviewing, and got the release editor to create NES rel
    5 KB (860 words) - 09:53, 24 August 2013
  • * Write documentation for three different schema tables (D/T) * Investigate large libraries with public data APIs and write a short document outlining the options with pros/cons (O/R)
    8 KB (1,245 words) - 23:33, 3 November 2016
  • ===Relax NG Schema=== ...the XML version of this API. It can also be used to validate [[#Submitting data|submissions]] you're trying to make through it.
    27 KB (4,241 words) - 16:12, 27 February 2024
  • ...ing.co.uk/computing/comment/2252032/ready-web-linked-4866476 web of linked data]. ...ipedia-of-music talks with Robert Kaye] about MusicBrainz, the forthcoming schema release and the philosophy of MB.
    15 KB (2,145 words) - 18:37, 16 June 2021
  • ...plex workflow for simple use cases (such as 'adding a book') and repeating data (for example the title of a work repeated for an edition and an edition gro You will set up Solr for use with Bookbrainz' schema, drawing inspiration from existing MusicBrainz code.
    9 KB (1,504 words) - 14:23, 25 March 2020
  • ...emphasis on working on our [[mbdoc:Next Generation Schema|Next Generation Schema]] (NGS) and not focusing on business aspects of MusicBrainz as much. This t ...of 2009 was terrible and 2) the BBC had a 6 month delay in renewing their data license contract, which accounts for $9000 lost revenue that we'll collect
    10 KB (1,390 words) - 07:49, 17 November 2013
  • The SQL scripts that create the schema can be found in our [https://github.com/metabrainz/musicbrainz-server/tree/ ...ty has a main table with the same name as the entity, containing its basic data.
    21 KB (3,347 words) - 18:44, 21 July 2023
  • In 2006 MusicBrainz grew significantly as it moved to a new data center in San Luis Obispo and expanded its collection of servers from three ...2006 it became apparent that MusicBrainz is starting to capitalize on its data and software assets and enabling others to capitalize on these open assets.
    22 KB (3,222 words) - 18:37, 18 December 2011
  • ...server. You could make up some fake data for song names and artists. This data doesn't have to be real. ...d delete the ListenBrainz database on your local server to remove the fake data that you added.
    18 KB (2,856 words) - 16:10, 4 March 2024
  • ...hip hop"). This is where some familiarity with Postgres (coming up with a schema) will come in handy. ...llest extent. MusicBrainz in particular is lacking utilisation of features/data from e.g., AcousticBrainz and ListenBrainz.
    12 KB (1,901 words) - 17:21, 28 April 2020
  • ** [https://tickets.metabrainz.org/browse/MBS-8625 Data quality] + redesign * Bookbrainz roadmap, schema review, Solr/search
    9 KB (1,385 words) - 13:59, 21 June 2019
View ( | next 20) (20 | 50 | 100 | 250 | 500)