Uploaded image for project: 'Zapped: AcousticBrainz'
  1. Zapped: AcousticBrainz
  2. AB-21

Webservice API : getting data for multiple recordings with one request

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Normal Normal
    • None
    • None
    • Server

      It would be useful if you could request data for multiple recordings with only one request, rather than doing N requests.

      The use case I'm thinking about is to collect data for all tracks of a release.
      So an alternative could be to request by release MBID.

      Originally reported by murdos on GitHub (issue #53).

      alastair commented on Dec 9, 2014:
      Good idea, but for now we don't have metadata in the server (I don't really want to trust release mbids, as there's no guarantee that they're correct [recording ids either, but that's another discussion])
      We were thinking about setting up a slave that could be used for this kind of additional metadata task.

      murdos commented on Dec 22, 2014:
      Requesting by release MBID was just a suggestion.

      My real need is something like https://acoustid.org/webservice#list_by_mbid in order to create a "MusicBrainz / AcousticBrainz integration" script in a similary way to https://bitbucket.org/acoustid/musicbrainz-acoustid/src/

          [AB-21] Webservice API : getting data for multiple recordings with one request

          Alastair Porter added a comment -

          Merged, waiting for release

          Alastair Porter added a comment - Merged, waiting for release

          Rashi Sah added a comment -

          Hi Paul,
          Yeah, I guess as soon as Alastair or Param will review and approve the Pull Request - https://github.com/metabrainz/acousticbrainz-server/pull/261.

          Rashi Sah added a comment - Hi Paul, Yeah, I guess as soon as Alastair or Param will review and approve the Pull Request - https://github.com/metabrainz/acousticbrainz-server/pull/261 .

          Paul Taylor added a comment -

          Looking at low-level V1 is it valid at the top level to recordingId:Offset:_lowlevel should it not be more recordingId:_recordingId,_offset:Offset:lowlevel:_lowleveldata

          i.e what I mean is that shouldn't recordingId and offset have a label to identify that the value is a recording id or an offset ?

           

          Paul Taylor added a comment - Looking at low-level V1 is it valid at the top level to recordingId : Offset:_lowlevel should it not be more recordingId:_recordingId,_offset :Offset: lowlevel:_lowleveldata i.e what I mean is that shouldn't recordingId and offset have a label to identify that the value is a recording id or an offset ?  

          Paul Taylor added a comment -

          Hi Rashi, do you know when your work will be deployed on the server so it is available for use ?

          Paul Taylor added a comment - Hi Rashi, do you know when your work will be deployed on the server so it is available for use ?

          Rashi Sah added a comment - - edited

          Support for fetching JSON document for high-level data with multiple recording ids.
          https://github.com/metabrainz/acousticbrainz-server/pull/261

          Rashi Sah added a comment - - edited Support for fetching JSON document for high-level data with multiple recording ids. https://github.com/metabrainz/acousticbrainz-server/pull/261

          Alastair Porter added a comment -

          Available for low-level: http://acousticbrainz.readthedocs.io/api.html#get--api-v1-low-level
          We should add highlevel too

          Alastair Porter added a comment - Available for low-level: http://acousticbrainz.readthedocs.io/api.html#get--api-v1-low-level We should add highlevel too

            rsh Rashi Sah
            murdos Aurélien Mino
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package