Search results

From MusicBrainz Wiki
Jump to navigationJump to search
  • * musicbrainz-db-schema (creation of the database) ...tomatically fetch and import data may be appropriate in the musicbrainz-db-schema package, however.
    941 bytes (129 words) - 08:41, 15 March 2009
  • ...undamentally 2 different types of branches: schema change branches and non-schema change branches. These branches have different workflows, both of which are == Non-schema change releases ==
    3 KB (582 words) - 14:02, 7 March 2012
  • ...dbrainz] MusicBrainz-R2RML project provides a mapping from the musicbrainz schema to RDF: Data dumps are infrequently updated, and available from:
    278 bytes (37 words) - 14:12, 26 May 2015
  • ...history of all the changes that the MusicBrainz community has made to the data. ==Data overview==
    4 KB (579 words) - 12:46, 26 May 2022
  • ...code (which creates a log of changes to tables using triggers), but change data link between master and mirror from "direct Postgres connection" to some fi ==Schema Sequence Number==
    9 KB (1,283 words) - 14:51, 1 March 2022
  • This page is for defining the mapping of [[Next Generation Schema]] and [[Advanced Relationships]] to RDF. Much of the old content has been The following objects exist in the [[Next Generation Schema]]. Here we make a clear distinction between '''core entities''' which have
    5 KB (764 words) - 14:12, 26 May 2015
  • ...For this you will need a tool to check an xml document against a RelaxNG schema. For this you can use 'jing', which should be available in most linux dist ...let-bill:~/tags$ curl --silent http://svn.musicbrainz.org/mmd-schema/trunk/schema/musicbrainz_mmd-2.0.rng -o musicbrainz_mmd-2.0.rng
    3 KB (444 words) - 12:21, 12 November 2011
  • ...matching the query 'Beatles' so I can find the one I want and ask for more data"). :Data submission, as well as requests that involve user information, require [[wi
    3 KB (534 words) - 05:08, 7 October 2020
  • mkdir /usr/local/pgsql/data sudo chown postgres /usr/local/pgsql/data
    3 KB (409 words) - 23:53, 30 April 2014
  • ...might be "database" slaves (i.e. like dbmirror); some might update derived data stores (e.g. Lucene); some might spool out the changes to a file (replicati ...of files. If the SQL transaction (to update the slave status) fails, that data would have to be "un-spooled".
    6 KB (967 words) - 00:52, 11 November 2011
  • == Data flow == # which then gathers data to be indexed from the database,
    8 KB (1,143 words) - 08:38, 21 January 2021
  • :A quick introduction to how changes to MusicBrainz data are made. ;[[MusicBrainz Database/Schema|Database Schema]]
    2 KB (328 words) - 06:20, 15 August 2023
  • .../blog.metabrainz.org/2019/03/07/schema-change-release-may-13-2019/ 2019 Q2 schema change]. ...abrainz.org/2017/03/13/may-2017-schema-change-release-may-15-2017/ 2017 Q2 schema change].
    5 KB (731 words) - 17:07, 18 January 2024
  • ...t familiar with the website and database without fear of adding inadequate data. Languages/skills: SQL, Node.js, knowledge of BookBrainz schema<br>
    5 KB (815 words) - 21:21, 29 March 2023
  • ...XML] based Web Service, that doesn't support all the latest changes in the schema. [[Image:Attention.png]] '''This service is now deprecated and should NOT b The XML returned by this Web Service is documented in [[MusicBrainz XML Meta Data]] and the overall Web Service is described in [[XML Web Service]].
    2 KB (297 words) - 03:42, 19 September 2012
  • *Classical schema planning *Data quality
    12 KB (1,966 words) - 05:53, 7 February 2012
  • ...SQL format]], most of the MusicBrainz data is also accessible via separate data dumps in JSON format. The data dumps are available for download from [https://metabrainz.org/datasets/post
    5 KB (761 words) - 13:25, 5 May 2023
  • ===Next Generation Schema=== The [[Next Generation Schema]] of the database was released in mid-May 2011 and was the culmination of f
    6 KB (933 words) - 11:46, 26 May 2015
  • * Schema change (this week or next?) (ian) ; reosarevok : Fixed some small errors, wrote a schema change patch.
    4 KB (520 words) - 21:46, 28 January 2013
  • === Data Importing === ...ace to the BookBrainz site to allow users to review automatically imported data, and approve it.
    3 KB (492 words) - 21:56, 14 March 2017
  • === Data Importing === ...ace to the BookBrainz site to allow users to review automatically imported data, and approve it.
    3 KB (492 words) - 04:34, 17 January 2018
  • * Fully support the NGS data model and web service # Gather data for the parser
    4 KB (547 words) - 00:03, 16 January 2013
  • ...quest data from the RDF web service and look up [[TRM]] IDs from WAV audio data. ; [http://bugs.musicbrainz.org/browser/mmd-schema mmd-schema]
    4 KB (616 words) - 15:23, 24 June 2013
  • ...o add information that usually doesn't fit into the strict structural data schema of MusicBrainz (be it due to technical limitations that may be addressed la ...an what MusicBrainz currently allows to enter: some tips for entering this data can be found in [[Sub Optimal Credits]].
    3 KB (565 words) - 19:14, 23 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===
    8 KB (1,324 words) - 14:52, 23 January 2018
  • ...ADME.rst to install the package and create a new BookBrainz database, with data from the dumps. Then, clone the bookbrainz-ws [https://github.com/bookbrain === Data Importing ===
    5 KB (811 words) - 21:55, 14 March 2017
  • ...ss the schema and example documents via [https://github.com/metabrainz/mmd-schema GitHub] or clone it locally: <code><nowiki>git clone https://github.com/metabrainz/mmd-schema.git</nowiki></code>
    16 KB (2,378 words) - 20:09, 10 July 2020
  • ...ease]]s - Different releases that are hard to fit into the [[MusicBrainz]] schema. ...Other Databases|OtherDatabases]] can be helpfull resources for editing the data in [[MusicBrainz]].
    5 KB (711 words) - 19:10, 17 August 2017
  • Very often editors have to type the data contained in the cover art images. The MusicBrainz database has an SQL schema defined under
    6 KB (852 words) - 12:03, 27 February 2024
  • ...inz Database]] product page and the [[MusicBrainz Database/Schema|database schema]] documentation if you are not familiar with the MusicBrainz Database. The data dumps are made available in a format that can be loaded into a local instan
    7 KB (1,142 words) - 11:15, 24 October 2023
  • ...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.
    8 KB (1,206 words) - 13:55, 25 May 2021
  • ...uld assume that they are going to be built on top of our [[Next Generation Schema]]. We will not accept proposals based on our old code base. ...ages with the intention of providing more thorough access to artist credit data.
    7 KB (1,187 words) - 19:46, 31 January 2012
  • ...s reproducible. Test it on both the live server, if it's not dangerous to data or something you can cancel out of, and on the test server. ...his. Picard may though. Includes "CRASH", if it causes damage to existing data.
    6 KB (1,071 words) - 08:11, 15 March 2009
  • ...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===
    5 KB (899 words) - 15:12, 3 February 2020
  • ...ers. Fortunately, it is easy to combine multiple pieces of well structured data into something that fits a user’s desired end-use. ...nsidered to be canonical in one data dump may not be canonical in the next data dump (for example after a release or recording merge). We don't expect this
    6 KB (925 words) - 13:27, 5 May 2023
  • === MusicBrainz data visualization with React === Languages/skills: JavaScript (React), data visualization<br>
    14 KB (2,150 words) - 11:51, 23 February 2023
  • While the MusicBrainz schema can correctly store a huge amount of data, at some moment you'll probably find something that just can't be entered w
    2 KB (250 words) - 12:28, 24 September 2018
  • '''We did it!''' The [[mbdoc:MusicBrainz Database/Schema|Next Generation Schema]] (NGS) went live in May 2011 after more than five years of planning and tw ...n music metadata. For many years we'd known that we needed to overhaul our schema and our website and deciding what and how we wanted to do it took more than
    11 KB (1,575 words) - 20:20, 12 April 2012
  • ### Events, Venues, Studios (geographical data) ### all kinds of other data and then some
    17 KB (2,972 words) - 11:26, 30 October 2011
  • ...October 17 will focus on companies using or wishing to use the MusicBrainz data. Anyone is welcome to attend any portion of the summit, but October 15/16 w * New data quality system
    10 KB (1,600 words) - 00:50, 19 January 2012
  • === 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
View (previous 50 | ) (20 | 50 | 100 | 250 | 500)