music/album/track property hosed?

GoogleCodeExporter commented 9 years ago

Looks like all sample queries from the MQL main online docs that involves the 
music track property fail. Is this a known issue? 

Example: 

http://www.freebase.com/queryeditor?q={%22type%22:%22/music/artist%22,%22name%22
:%22The%20Police%22,%22album%22:{%22name%22:%22Synchronicity%22,%22track%22:[]}}

Query (from the sample code in the documentation):
{
  "type" : "/music/artist",
  "name" : "The Police",
  "album" : {
    "name" : "Synchronicity",
    "track" : []
  }
}

Response:

code: "/api/status/error"
messages: [
0: {
code: "/api/status/error/mql/type"
info: {
expected_type: "/music/album"
property: "track"
message: "Type /music/album does not have property track"
path: "album"
query: {
album: {
error_inside: "."
name: "Synchronicity"
track: []
name: "The Police"
type: "/music/artist"xp
status: "200 OK"
transaction_id: "cache;cache03.p01.sjc1:8101;2011-02-12T16:21:58Z;0022"

Original issue reported on code.google.com by aviveya...@gmail.com on 12 Feb 2011 at 4:28

GoogleCodeExporter commented 9 years ago

I ran across this as well. Apparently since the documentation was written the 
schema has been refactored and albums now have releases which contain the 
tracks.

The query that works is:

{
  "type" : "/music/artist",
  "name" : "The Police",
  "album" : [{
    "name" : "Synchronicity",
    "releases" : [{
      "track" : [],
    }]
  }]
}

Original comment by wholcomb on 26 Feb 2011 at 6:12

GoogleCodeExporter commented 9 years ago

Well, the core freebase online documentation is around album and tracks, and 
ALL queries in the docs that involve a track are borken. Can anyone fix this? 
Is there anybody home in Freebase post the Google acquisition at all?

Original comment by aviveya...@gmail.com on 26 Feb 2011 at 8:28

Sachini / freebase-suggest

music/album/track property hosed? #16