ClemDoum
commented
6 years ago @YipYup I'm trying to start the implementation if this feature.:
What exactly do you mean by: Changing selection requires a database purge and full-rescan:
- what tables should I drop or rather what tables should I keep?
- what functions should I call to do the full rescan only
librarysync.libraryScan?
Summary
This request is to add official support for the Discogs database as an alternative source to MusicBrainz.
Description:
Discogs is an alternate metadata database for Artists, Albums, and Tracks. I often find that many entries I lookup are more complete there than in MusicBrainz. I would like to have a way to switch Headphones to use Discogs instead of MusicBrainz.
I am offering a cash bounty for Milestone 1. Like this idea? Give your +1 Reaction and add to the bounty I started.
Bounty Milestones:
I understand it is no easy undertaking to implement this, let alone determine a proper path going forward for development milestones. My suggestion for milestones would be in summary to first offer the integration and add a selection option for the user to choose which database to use -- just one or the other but not both at the same time. Changing / setting selection would require the user to do a full complete re-scan at that time. Thus, only support one database at a time. The scope of the bounty is for the first milestone. Then, for a second milestone if this is desired by other users, find a way to marry data from both data sources as to enable metadata from both simultaneously -- however just the first milestone would be incredible and is what I am posting the bounty on.
Resources
Like this idea? Contribute to the bounty!