Search results

From MusicBrainz Wiki
Jump to navigationJump to search
  • === MusicBrainz data visualization with React === Languages/skills: JavaScript (React), data visualization<br>
    16 KB (2,489 words) - 18:05, 14 March 2022
  • === MusicBrainz data visualization with React === Languages/skills: JavaScript (React), data visualization<br>
    17 KB (2,649 words) - 18:59, 16 March 2021
  • ...t familiar with the website and database without fear of adding inadequate data. This project requires a solid knowledge of the BookBrainz schema and edit pages.
    9 KB (1,486 words) - 12:59, 30 March 2022
  • The [[MusicBrainz XML Meta Data]] (MMD schema) is used to determine the output returned from the search server. | '''version''' || [[MusicBrainz XML Meta Data|MMD]] version, defaults to 2, can be set to 1 for backwards compatibility.
    5 KB (667 words) - 07:29, 18 March 2024
  • ...oject [[Nadelnder Bambus|NadelnderBambus]], the complete [[Next Generation Schema|NextGenerationSchema]] that has been thought out on the summit. This will b ** the reorganization of the user interface (i.e. display of the data on the website)
    6 KB (879 words) - 20:30, 26 May 2015
  • ...s the API to download the data that you submitted to your server, or other data from the main AcousticBrainz server ===Statistics and data description===
    10 KB (1,594 words) - 10:19, 25 March 2019
  • ...of tangible progress on the [[mbdoc:Next Generation Schema|Next Generation Schema]] (NGS). NGS would prove to be our number one task in 2010, with no server ...p://musixmatch.com/ musiXmatch], and [http://www.zeezee.de/ ZeeZee] as new data customers in 2010.
    10 KB (1,427 words) - 03:18, 11 January 2012
  • ** Switch data dumps to every other day to save bandwidth ** Synchronize the data dumps/RDF dumps to align with replication packet serial numbers
    7 KB (1,147 words) - 20:29, 26 May 2015
  • ...tle more calm. Since our last major schema update for the Next Generation Schema, we've spent a considerable amount of time making further improvements and ...way] using MBIDs. This was the first time that a record label embraced our data and produced a very slick looking site showcasing their own artists.
    18 KB (2,597 words) - 16:24, 26 December 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 (956 words) - 16:33, 16 March 2016
  • : 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
View ( | ) (20 | 50 | 100 | 250 | 500)