problems with artists and albums
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Trying to retrieve artist and album links for a given artist, and running into a few issues:
#1 - If I search for artist "David Sanborn" using the endpoint https://api.soundcloud.com/users?q=David Sanborn&limit=200&offset=0&linked_partitioning=true, I get a payload with several artists of that name. Is there any way within the api to distinguish between users and actual recording artists?
#2 - Assuming I land on the right user id (203409966), I then want to retrieve all albums featuring David Sanborn. For this, I use the endpoint https://api.soundcloud.com/users/soundcloud:users:203409966/playlists?linked_partitioning=1&page_size=200&show_tracks=false and everything looks good in that I see a partial list of albums by David Sanborn. However, next_href in this payload reads as follows: https://api.soundcloud.com/users/soundcloud:users:203409966/playlists?cursor=1978-05-10T00%3A00%3A00.000Z%2Cplaylists%2C00000000000244135998&linked_partitioning=1&page_size=200&show_tracks=false and when I issue that request, I receive a response code of 200 but a payload as follows:
{
"collection": [],
"next_href": null
}
What am I missing here? Do I need to modify the next_href before sending it to get it to work, and if so, how?
Thank you.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the artist search and playlist pagination requests for user 203409966 using the endpoints and next_href shown in the report. Determine whether the API provides a way to distinguish recording artists from similarly named users and why the returned cursor produces an empty collection. Done means a confirmed API behavior or fix, with the required request documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100