search

wafflesfm / batter

It makes Waffles.
Other
83 stars 18 forks source link

Discogs API Validation #13

Open Ell opened 11 years ago

Ell commented 11 years ago

All music uploads should be validated as much as possible against discogs. we should also implement adding stuff not on the discogs website too

superbobry commented 11 years ago

So the question remains the same: what is the expected behaviour if the uploaded release is missing in the Discogs database?

Woodenhead commented 11 years ago

Definitely an important question, as it will happen often enough. No DB is fully complete, after all.

edgewyn commented 11 years ago

If the uploaded release is not in the Discogs database, we should mark it as "unverified". Later on, moderators can examine the queue of unverified uploads and manually ensure that the upload corresponds to an actual release.

superbobry commented 11 years ago

Should we submit it to Discogs or moderators will do this manually?

Ell commented 11 years ago

Discogs also has its own notion of Verified and Not Verified in the API too. Do we just want to check against Verified entries in the discogs api or every entry?

Woodenhead commented 11 years ago

Oh gawd no - moderators shouldn't be manually validating this stuff. There's no way they'd be able to keep up. If anything, users (a specific class perhaps) could verify them. But we shouldn't rely so heavily on the discogs API - we'll need a more typical upload page (where all fields get filled manually by the user), for when there's no entry in the Discogs DB. It'll happen more often than you'd think. (pre-release, scene, bootleg, live Phish concerts, (haha) etc.) Which also ties into Verified vs. Unverified, I think.

ghost commented 11 years ago

At AB we have the concept of "Wiki Students" whose entire purpose is to basically verify and tidy metadata. A similar thing could work for Waffles as well.

Also, having a single upload form with a Discogs autofill could work.

Woodenhead commented 11 years ago

Now we're talking! That is basically what I was thinking of doing with the Waffle Irons as well, at one point, but perhaps it'll be its own class. At any rate, everything you posted works for me.

[aside: user classes/permissions will be a big part of Batter - need to be very flexible]

superbobry commented 11 years ago

Also, having a single upload form with a Discogs autofill could work.

Sounds good.