[#MBS-3735] Allow seeding Release Editor with Fingerprints - MusicBrainz JIRA

MusicBrainz Server

Allow seeding Release Editor with Fingerprints

Created: 06/Nov/11 02:12 AM Updated: 21/Nov/11 06:21 PM

Component/s:

Release editor

Affects Version/s:

None

Fix Version/s:

None

Description

« Hide

Analog to MBS-2266, it would be great if the release editor could be seeded with fingerprints (PUID, or even better AcoustID after it is implemented). The Picard "Add cluster as release" could utilize this!

Sort Order:

[ Permalink | « Hide ]

Lukáš Lalinský added a comment - 06/Nov/11 07:27 AM

I guess this is not doable for AcoustIDs.

[ Permalink | « Hide ]

Johannes Weißl added a comment - 06/Nov/11 12:54 PM

Why? Because of the asymmetric import process, or because AcoustIDs are stored externally?

[ Permalink | « Hide ]

Lukáš Lalinský added a comment - 06/Nov/11 05:07 PM

Because they are stored externally, MB has no way to submitting them on the user's behalf.

[ Permalink | « Hide ]

Lukáš Lalinský added a comment - 06/Nov/11 05:08 PM

Plus I don't think AcoustID will ever accept direct ID submissions. I always want to get the fingerprint together with the MBID, and determine the ID on the server side.

[ Permalink | « Hide ]

Johannes Weißl added a comment - 06/Nov/11 07:20 PM

I think there is a misunderstanding here: This ticket has nothing to do with fingerprint submission. The fingerprints would just be used to help selecting the correct recordings for compilations! In my understanding this is possible for AcoustID if MusicBrainz contains a replicated table, which I think is the longterm plan. Is it possible then?

[ Permalink | « Hide ]

Lukáš Lalinský added a comment - 07/Nov/11 07:14 AM

Oh, I misunderstood that part. Yes, then it makes sense.