internet4000 / explorer-discogs Goto Github PK

• create routes /releases + /releases/:id
• make it list releases without ember data first?

When you're browsing releases for an artist it renders wrong releases.

Example:

1. Go to "Malk de Koijn" https://explorer-discogs.netlify.com/artists/287559
2. Weird releases appear like https://explorer-discogs.netlify.com/releases/506939

If you visit the API endpoint for the Malk de Koijn's releasess the "wrong releases" are not even there.

• https://edapi.glitch.me/artists/287559/releases

Not sure what is happening.

Goal is to be able to play any release? Or what is the right term in discogs-lingo?

For something simple, we could use the youtube iframe api directly and the loadPlaylist method.

Sometimes on https://discogs.radio4000.com/artists/2408160 the members:hasMany:artist relationship doesn't render all items properly. The list-item is there but the name is empty. If you refresh it'll either work or be different missing items. To be investigated.

• set up model relationship
• /labels/:id renders a label

In order to avoid reaching the Discogs API rate limits we should avoid more requests than necessary.

For instance, if you go to a release, then back to the homepage and finally visit the same release again, a second uneccesary GET request is made.

• can we avoid calling it twice? who is responsible? discogs? ember data?

Another idea is to sync the the store to a local database like pouchdb, localstorage or whatever they're called these days. That could be cool, too. First look in local db, is it there, yes return, otherwise fetch.

#nicetohave

We can keep this issue open with small ideas here and there…

• the "urls" property doesn't render <a> links
• extend {{each-list}} to work for comma-separated lists
• on http://localhost:4200/releases/120096 "main artist" should be a link
• figure out what to do with master/release which both could have players
• scroll to top is needed
• make player stick to right edge and height 100%? not fixed but part of layout
• show most important community data on a release
• Include entity_type_name for companies
• Show release format info (mp3?lp? etc) and link other releases? or merge them?
• master & release https://www.discogs.com/help/doc/submission-guidelines-master-release
• move "members" above "urls" on /release/info
• format profile for all models (only artist has it for now)

Your application must provide a User-Agent string that identifies itself

https://www.discogs.com/developers/#page:home,header:home-general-information

status

• image links to radio4000.com when it should link to the ressource that is played (anywhere on the internet)
• track items link to radio4000.com/undefined/:trackId

solution

See here radio4000-player issue here internet4000/radio4000-player#104.

We can wait for a solution there, then implement it here

• set up model relationships
• /artists/:id renders an artist

We can filter the Discogs search to something like "house releases from 2018" but there' currently no way to play all of them at once.

• https://www.discogs.com/search/?sort=want%2Cdesc&year=2018&style_exact=House&type=release&page=2&advanced=1

Since these search results only includes releases, we can find a way to put the buttons directly on the search page as well as a button.

Idea came from https://www.discogs.com/forum/thread/765954 & https://www.reddit.com/r/discogs/comments/8cg0z2/fetching_youtube_links_using_discogs_api/

Currently not possible.

http://localhost:4200/artists/287559
http://localhost:4200/artists/4393110

But we have releasesUrl: https://api.discogs.com/artists/287559/releases from where we can hopefully extract the relationships. @hugurp?

let's set up some constraints. ideas

• grayscale
• maximum one font-size. use whitespace and/or font-style/weight instead.
• fullscreen fluid

Let's try gather ideas to improve the layout for search results. Right now it's difficult to scan the different types.

Example http://localhost:4200/search?search=whomadewho

• integrate authentication (https://www.discogs.com/developers/#page:authentication,header:authentication-discogs-auth-flow)
• create a search form (application level?)

make sure the search doesn't reach API limits too fast

We should create a video model. It's a relationship on the release model. Possibly others, too. The data looks like this:

videos": [
{
"duration": 489,
"description": "Nirvana - Come as you are (Andy Caldwell remix)",
"embed": true,
"uri": "https://www.youtube.com/watch?v=rPHGAO4LOLk",
"title": "Nirvana - Come as you are (Andy Caldwell remix)"
},
{
"duration": 498,
"description": "Nirvana - Come As You Are (Dirty Funker Remix)",
"embed": true,
"uri": "https://www.youtube.com/watch?v=fm8F9GikQdM",
"title": "Nirvana - Come As You Are (Dirty Funker Remix)"
},
{
"duration": 226,
"description": "Nirvana - Come As You Are",
"embed": true,
"uri": "https://www.youtube.com/watch?v=vabnZ9-ex7o",
"title": "Nirvana - Come As You Are"
}
],

(from https://api.discogs.com/masters/42457)

How does a master relate to a release?

At the moment it's blank https://explorer-discogs.netlify.com/masters/74177

Here https://explorer.radio4000.com/artists/6397969 the results on the releases, and their videos are not the same as on Discogs.

Should investigate why.

So the redis on IBM cloud is not free. But it is on redislabs.

• switch to redislabs
• configure accounts so we have access

A label like Universal http://localhost:4200/labels/22532 currently has 25k releases. So we need to paginate. Can we copy/paste from search?

https://api.discogs.com/labels/22532/releases

There are probably more places that need pagination but for now we can do this one.

using netlify