-
Improvement
-
Resolution: Fixed
-
Normal
-
None
-
None
With current release browse web service, I cannot get works through inc= recording-level-rels as it is unsupported (I would also like work credits with work-rels but it requires recording-level-rels first).
/ws/2/release?inc=work-rels+... (no error but no work data) → /ws/2/release?inc=recording-level-rels+work-rels+... it errors as:
<error> <text> recording-level-rels is not a valid inc parameter for the release resource. </text> <text> For usage, please see: http://musicbrainz.org/development/mmd </text> </error>
FTR it does work in lookup mode (but one release at a time).
[MBS-6140] Add "recording-level-rels" (and "work-rels") support to "Release" browse web service
| Fix Version/s | New: 2021-09-20 [ 12032 ] | |
| Status | Original: In Beta Testing [ 10002 ] | New: Closed [ 6 ] |
| Status | Original: In Development Branch [ 10007 ] | New: In Beta Testing [ 10002 ] |
| Resolution | New: Fixed [ 1 ] |
| Status | Original: Review Submitted [ 5 ] | New: In Development Branch [ 10007 ] |
| Assignee | New: Nicolás Tamargo [ reosarevok ] |
| Status | Original: Open [ 1 ] | New: Review Submitted [ 5 ] |
| Description |
Original:
I start from the *lookup* version of the web service from which I can fetch *all I need*: http://musicbrainz.org/ws/2/release/f674f7b2-9538-476c-9ce1-b7931b63faca?inc=release-groups+recordings+artists+artist-credits+labels+recording-level-rels+work-rels *artists* seems to be redundant with *artist-credits*, I can remove it same result. But there *I have works, thanks to recording-level-rels*. Now *I would like same elements from the browse version* of the web service (usually same stuff is provided). http://musicbrainz.org/ws/2/release?inc=release-groups+recordings+artist-credits+labels+work-rels&collection=f0574792-6af6-481e-8b2f-d5ea9fc59c4d If I try to get *recording-level-rels* here, it crashes (it also crashes with *artists* but I don't care): http://musicbrainz.org/ws/2/release?inc=release-groups+recordings+artist-credits+labels+work-rels+recording-level-rels&collection=f0574792-6af6-481e-8b2f-d5ea9fc59c4d {code:xml} <error> <text> recording-level-rels is not a valid inc parameter for the release resource. </text> <text> For usage, please see: http://musicbrainz.org/development/mmd </text> </error> {code} No more luck in JSON: https://musicbrainz.org/ws/2/release?inc=release-groups+recordings+artist-credits+labels+work-rels+recording-level-rels&collection=f0574792-6af6-481e-8b2f-d5ea9fc59c4d&fmt=json |
New:
With current release browse web service, I cannot get works through inc= *recording-level-rels* as it is unsupported (I would also like work credits with *work-rels* but it requires *recording-level-rels* first). [/ws/2/release?inc=work-rels+... (*no error but no work data*)|http://musicbrainz.org/ws/2/release?inc=release-groups+recordings+artist-credits+labels+work-rels&collection=f0574792-6af6-481e-8b2f-d5ea9fc59c4d] → [/ws/2/release?inc=recording-level-rels+work-rels+...|http://musicbrainz.org/ws/2/release?inc=release-groups+recordings+artist-credits+labels+work-rels+recording-level-rels&collection=f0574792-6af6-481e-8b2f-d5ea9fc59c4d] it errors as: {code:xml} <error> <text> recording-level-rels is not a valid inc parameter for the release resource. </text> <text> For usage, please see: http://musicbrainz.org/development/mmd </text> </error> {code} [No more luck with JSON.|https://musicbrainz.org/ws/2/release?inc=release-groups+recordings+artist-credits+labels+work-rels+recording-level-rels&collection=f0574792-6af6-481e-8b2f-d5ea9fc59c4d&fmt=json] ---- FTR it does work in [lookup mode|http://musicbrainz.org/ws/2/release/f674f7b2-9538-476c-9ce1-b7931b63faca?inc=release-groups+recordings+artist-credits+labels+recording-level-rels+work-rels] (but one release at a time). |
| Issue Type | Original: Bug [ 1 ] | New: Improvement [ 4 ] |
| Summary | Original: recording-level-rels absent from Release browse web service inc parameter | New: Add "recording-level-rels" (and "work-rels") support to "Release" browse web service |
After discussing with alastairp it rather seems like a feature request, not a bug.
The implementation will return up to 500 linked recordings, to prevent load issues with the web service.