Calling all voters - you can now merge releases!

Hi voters - following on from this topic, just to let you know (in case you are not aware of it yet) voters can now initiate merge release requests.

The instructions for doing this are at http://www.discogs.sitioby.com/help/submission-guidelines-merge-release.html - basically, just go the the history / edit page of either of the releases you want to merge, and follow the instructions.

At the moment, you can do one merge a day.

If you are looking for a merge to do, you can check the remove release queue http://www.discogs.sitioby.com/submissions?mode=removals for any items tagged as 'duplicate', although they'll need 4 votes to be bumped out of that queue at the moment You could ask for votes here).

You can vote on merges at http://www.discogs.sitioby.com/submissions?mode=merges

Please let me know if you see any problems.

Regarding release removals (the way we 'fixed' duplicates previously), I am planning to suspend that function temporarily whilst we transition to the new merge release function.

As it stands, there are quite a lot of releases in the remove release queue. Don't worry about voting these through (vote yes if they are a duplicate), as they will end up listed at http://www.discogs.sitioby.com/submissions?mode=removed and can be merged after that (drafts can be merged).

Also, I am wanting to expire all removals / merges that don't get enough votes after a month, so don't worry too much about all the older remove release requests in that queue (you can still vote if you want though).

We would still be able to remove non-existing releases, right?

nik
I am planning to suspend that function temporarily whilst we transition to the new merge release function.

What about releases that should be removed because they're non-existing, fake, unidentifyable?

jweijde
We would still be able to remove non-existing releases, right?

marcelrecords
What about releases that should be removed because they're non-existing, fake, unidentifyable?

Those type of release should be removed for sure. However, since the remove release function has, for the vast majority of the time, used for fixing duplicates, it would be good to have a 'break' for the remove release function just whilst we transition to the merge function. We can keep a note of the releases that need removed, then do that in a week or two once the remove release function is opened again. Does that make sense?

nik
Does that make sense?

Fine with me. If I stumble upon such entries, I will keep them in a list.

Can any releases be merged? By this, as removal is not available currently we could at least merge non-existing releases in to one "to be removed" dummy release until the removal function is back again.

nik
you can check the remove release queue http://www.www.discogs.sitioby.com/submissions?mode=removals

Extra "W's" = bad link!

Nik, a possible bug: I just got a PM about a merge. The PM states that I get this message because I either contributed, own it or want it. Neither is the case. I never even heard of that release

What is the URL of the release?

Mop66
Can any releases be merged? By this, as removal is not available currently we could at least merge non-existing releases in to one "to be removed" dummy release until the removal function is back again.

No, please don't hack the merge release function to remove releases... just list them at http://www.discogs.sitioby.com/help/forums/topic/339730 - thanks!

There appears to be an issue with information not all properly merging: see http://www.discogs.sitioby.com/history?release=1577212#latest

This can create major headaches if we have to check and see what is included in the new release info and properly update each release - especially if there are a lot of credits and companies.

Merging releases is not a good idea if the information is not properly merged...

nik
What is the URL of the release?

Vic Mizzy - The Ghost And Mr. Chicken (Original Motion Picture Soundtrack)

Kergillian
There appears to be an issue with information not all properly merging: see http://www.discogs.sitioby.com/history?release=1577212#latest

This can create major headaches if we have to check and see what is included in the new release info and properly update each release - especially if there are a lot of credits and companies.

Merging releases is not a good idea if the information is not properly merged...

The information doesn't merge, we select which version of the information to keep / use. The main importance of merge release is to preserve all collections / wantlists / lists / ratings / sales, which are lost if the duplicate release is just removed.

syke
Vic Mizzy - The Ghost And Mr. Chicken (Original Motion Picture Soundtrack)

Thanks, I have asked the developers to look into that!

nik
Thanks, I have asked the developers to look into that!

shall the merge be stopped for now until the devs looked into it?

Notification was likely due to r2326946, the other side of the merge, which you had edited: http://www.discogs.sitioby.com/history?release=2326946#latest

Obviously the messages should identify the right release.

nik
The information doesn't merge,

This means we need to carefully select the release that stays in order not to have a very basic sub in the end if a much more advanced version was available also. Not necessarily the older submission stays, which is a different approach than before. Is this summary correct?

nik
The information doesn't merge, we select which version of the information to keep / use. The main importance of merge release is to preserve all collections / wantlists / lists / ratings / sales, which are lost if the duplicate release is just removed.

Was looking forward to that functionality - but I must have neglected the details as I was expecting a way to merge data for releases to keep. In my mind was was to be expected was a way to take groups of data from one release to another - e.g. if one release had been subbed with just the mandatory data and later someone took the time to enter all data for a complete submission - then it would be great to have a "merge data" tool. Now I see that that'll, remain a wish.

Just tried my first merge - and gave it up. In my case both subs had info in fields the other didn't have - but one not the images to check it out. Doing a merge, in essence an edit - I assumed would make me "submission owner" and with no way to check info properly, I could look forward to be handling future edits for a while.

This case might not be typical. But general no experienced member would want to "own" problem subs - and merges could indicate discussions and the risk of doing wrong as the merger may not have the release in hand. And previously putting a release up for removal or voting for it didn't connect one to the release for months or years to come.

So -

1. Does the merging member become submission owner? If so - that would at least make me reluctant to merge releases I don't have - so could there be some sort of immunity for merging?

2. Large edits is happening in a merge. Should one have the release in hand when merging?

Indeed this is becoming complicated and I fear that too much information might be lost - the releases should be properly merged, IMO, as they used to be - not a once or the other scenario...

Mop66
This means we need to carefully select the release that stays in order not to have a very basic sub in the end if a much more advanced version was available also. Not necessarily the older submission stays, which is a different approach than before. Is this summary correct?

The merge always uses the oldest submitted release as the release that remains in the database. On the merge form, you select which version of the information you want to use.

gboe
In my mind was was to be expected was a way to take groups of data from one release to another - e.g. if one release had been subbed with just the mandatory data and later someone took the time to enter all data for a complete submission - then it would be great to have a "merge data" tool.

Kergillian
I fear that too much information might be lost - the releases should be properly merged, IMO, as they used to be - not a once or the other scenario...

The old merge function never allowed you to pick n mix the data that remained. This new merge function allows you to choose which version of the data is better.

Making a system that allows us to pick n mix which data to keep would be very complicated - we'd have to have something like a select box for every data field on the release. That is not practical, and in most cases not necessary. Both sets of data are kept in any case, so it is a simple (and probably quicker) matter to select the best version, then once the merge is complete you can edit the release to incorporate any other information that may have been better in the removed release.

gboe
Does the merging member become submission owner? If so - that would at least make me reluctant to merge releases I don't have - so could there be some sort of immunity for merging?

If you choose to use the data from the newer submission, that becomes an edit on the older submission on acceptance of the merge, yes. There is no immunity, but you should seriously not be worried by this, especially with the number of votes and edits you have.

gboe
Large edits is happening in a merge. Should one have the release in hand when merging?

You want to be taking care when merging. You don't necessarily have to have the release in hand, no.

Two quick questions:

Is there a list releases removed/converted to draft status by merging, similar to http://www.discogs.sitioby.com/submissions?mode=removed&view=flat ?

What can/should be done if releases are incorrectly merged?

seppuku
Is there a list releases removed/converted to draft status by merging, similar to http://www.discogs.sitioby.com/submissions?mode=removed&view=flat ?

I have requested that be added, thanks.

seppuku
What can/should be done if releases are incorrectly merged?

Merges cannot be undone. The releases that was removed and sent to draft can be resubmitted, but all the collections / wantlists / lists / comments / reviews / sales would have to be manually moved to the other release. Please always be careful when merging releases.

nik
The old merge function never allowed you to pick n mix the data that remained. This new merge function allows you to choose which version of the data is better.

Making a system that allows us to pick n mix which data to keep would be very complicated - we'd have to have something like a select box for every data field on the release. That is not practical, and in most cases not necessary. Both sets of data are kept in any case, so it is a simple (and probably quicker) matter to select the best version, then once the merge is complete you can edit the release to incorporate any other information that may have been better in the removed release.

I wasn't thinking of pick and mix - I was thinking of amalgamating everything...

How would that work? What if there is a conflict in the data? What if there is incorrect data that gets merged? Do you have any examples of sites or programs that do this?

Not wanting to be negative, I understand what you are getting at, but the solution is non-trivial, and would at the end of the day result in more complexity and more chance for incorrect data.

Well, we're going to have to edit anyhow in many cases, so if there is incorrect data that gets merged, it's six of one vs half a dozen of the other ;)

But fair enough - better to merge incomplete than not at all, I suppose :)

Question on

17.3.4. You can only merge one release per day. If you need to merge more than that, please ask another to help in the Adding & Updating forum.

Is that a 24 h limit or once per day (meaning I could do one merge at 23:59 today and another one at 00:01 tomorrow which is only 2 min apart). Just out of curiosity.

What about the data quality rating?
http://www.discogs.sitioby.com/history?release=544905#latest

This now has Needs Minor Changes because I voted on it 3 years ago.
It has just been merged and the issue I voted for no longer applies.

I think it would be better if the quality rating is set to Needs Vote after a merge.

Mop66
17.3.4. You can only merge one release per day. If you need to merge more than that, please ask another to help in the Adding & Updating forum.

Is that really true? Maybe it was the timezone, but I was able to put several up for a merge yesterday.

jweijde
Is that really true?

I did not try more than one yet, I just noticed the rule.

there is an EXTREMELY FRUSTRATING bug in the merge form right now...
http://postimage.org/image/h1bbyqriv
It's unacceptable that something like this stays unnoticed. I had this happen once already and thought I had messed up the release numbers. However it turns out the whole process is inverted, i.e. the release that should stay will be deleted!

@ HM-2; The lower/earlier numbered release stays the larger/later numbered release gets sent to draft, that's intentional. Selecting the radio button determines which data set stays.

Would be nice if in the release history it did not mention
'Merge Pending'
but
'Merge Pending with release [releaseid]'

that would make things clearer.

Need NO votes to this incorrect merge:
http://www.discogs.sitioby.com/history?release=3605485#latest

Need YES to merge these:
Models (2) - Out Of Mind Out Of Sight (newer sub)

I hope to add basicall a couple of bits together between the two (eg. the link to the actual LP from the later-subbed one, &/or adding in the Publisher if keeping the later submission but ditching the original sub)

btw, an engineering fix is also need on the older sub that I subbed. It needs one engineer to go to one track and the other added into the other track.

^^ there you go

YES's please
Elton John - Too Low For Zero (r3298074) (But Remove is now disabled so needs to be merged)

The Alan Parsons Project - Eye In The Sky
Yes to merge to eradicate same thing: subber has erroneously subbed the same thing twice (And the one that has an un-cat#-ed Festival Records label applied, is rubbish. I noticed this from trying to always keep up adding their releases into an MR, which they fail to do with every single one of their subs.

btw, I'm unclear as to basically whether this is the new form of the "Remove Request" thread, to draw attention to Merges? Or are we supposed to post what we find still, in that old open "Remove Request" thread, just basically substituting the words 'remove dupe please' with 'merge please'?

1/ Can this thread please be made a "sticky"?

2/ Merge here: Sammy Davis Jr. - Sammy Davis Jr. Belts The Best Of Broadway r2803077
For some reason, I thought I'd picked the younger sub to be nominated to remain, the other effectively eradicated (the older one) but it has gone round the other way. Maybe I ticked the wrong data box, but I didn't think so. Anyway, either way, if this is ok, please get rid of the dupe that was subbed by same 3 submissions straight after the other one.

btw, 17.2.1. The releases must represent the exact same version, going by the unique release guidelines. The system automatically keeps the first submitted release
I forgot this, & didn't transcribe the better edited info across, so what happens here for a merge? No, then perhaps update them & then initiate a merge process again?

1skinnylad
I'm unclear as to basically whether this is the new form of the "Remove Request" thread, to draw attention to Merges? Or are we supposed to post what we find still, in that old open "Remove Request" thread, just basically substituting the words 'remove dupe please' with 'merge please'?

Merging releases is for duplicate releases, or other such errors where we want to preserve the collections etc.

Remove release once reintroduced will only be for taking releases out of the database that are entirely invalid for the site.

1skinnylad
I forgot this, & didn't transcribe the better edited info across, so what happens here for a merge? No, then perhaps update them & then initiate a merge process again?

You can manually update the release once the merge goes through. The transferring of the data is just to make things easy.

ok, cool, thanks

will there be a new sticky created just for a not-limited-by-3mths-thread for merges (like the Remove Release/Request Votes on your submission/etc)?

Please vote Yes to Merge this recently added dupe:
Dire Straits - ExtendeDancEPlay (r2382203) (older sub & should stay as is, nothing needed other than to vote out the younger sub)

Btw, when will the Remove Request return please?

Ok, I had incorrectly put up my own dupe for removal. But now understand the new rules are now not to remove, rather merge instead.

So now my dupe's up for 'merge' instead (after the successfully voted "no' to a removal just prior has now been completed). Please vote yes to merge:
The Atlantics - Great Surfing Sounds Of The Atlantics
&
Atlantics, The - Great Surfing Sounds Of The Atlantics.
Thanks!

Does anyone else think these should be merged?
Real Life - Send Me An Angel
&
Real Life - Send Me An Angel
[EDIT update] the images attest to differing typesettings altogether
http://www.discogs.sitioby.com/viewimages?release=1371859
http://www.discogs.sitioby.com/image/R-3652066-1339572676-1607.jpeg
so these must be separate after all. Please ignore my request, I'll just add it to the MR instead.

Bryan Ferry - A Hard Rain's A-Gonna Fall
&
Bryan Ferry - A Hard Rain's A-Gonna Fall
needs merging. Same submitter stuck it twice in, one with pics

Please vote for merging those two releases:

http://www.discogs.sitioby.com/Residents-Ralph-Volume-One/release/3655803

and...

http://www.discogs.sitioby.com/Various-Ralph-Video-Volume-I/release/2918408

My comment on the first one: duplicated and ever incomplete sub. I asked explanations to the submitter but without success (he never answer to questions, and usually his subs are very poor or incorrect).

Thank you very much.

is this thread where I should look for votes to merge?

if so then please see the notes here:

Jackson C. Frank - Jackson C. Frank

thanks.

The Good Girls - Just Call Me (Remix)
&
Good Girls, The - Just Call Me (Remix)

i gathered these rejected removals of "dupes" upon being last No voter in the removals cue,
maybe someone has the time and skills to initiate the merge process

Miguel Migs - Find What's Mine

^^ & 3 more:

Paid & Live Feat. Lauryn Hill & Robert "Kool" Bell* - All My Time
[Invalid Release]
Lana Del Rey - Video Games Remix E.P.

Need some yes votes to merge a duplicate I submitted into the existing release:

http://www.discogs.sitioby.com/history?release=1874537#latest

Thanks.

8m2stereo
i gathered these rejected removals of "dupes" upon being last No voter in the removals cue,
maybe someone has the time and skills to initiate the merge process

& 6 more

Various - Ultimix 69

Need some votes on this one for a merge:
http://www.discogs.sitioby.com/history?release=3690761#latest

And also need votes for this merge:
http://www.discogs.sitioby.com/history?release=3690740#latest

is it here wehere we ask for votes??

http://www.discogs.sitioby.com/history?release=1227630#latest

should these be merged:
Mary Jane Girls - In My House?

removal rejected, needs to be put up for merge:

Brand New Heavies, The - Dream Come True (Brand New Mix)

same for the 25 others i posted above, all waiting to be merged ..

is anyone even interested in initiating the merges for rejected removals,
or should there maybe be a new & sticky thread about needed merges ?

8m2stereo
or should there maybe be a new & sticky thread about needed merges ?

That would be great. There are releases that should be merged without a doubt but that don't get enough votes. It would be cool to not be forced to wait a month only to ask for the same merge again.

Please vote Yes here:

http://www.discogs.sitioby.com/history?release=2008085#latest

A quite badly done dupe has been posted:
H.G. Francis - Die Drei ??? 12- und der seltsame Wecker

Thanks!

nik
Please let me know if you see any problems.

we're still stuck with some merges that do not get through, no matter how many Y-votes are cast:
http://www.discogs.sitioby.com/submissions?mode=merges&page=2#item=release/139282
http://www.discogs.sitioby.com/submissions?mode=merges&page=2#item=release/830532
http://www.discogs.sitioby.com/submissions?mode=merges&page=2#item=release/1156714
http://www.discogs.sitioby.com/submissions?mode=merges&page=2#item=release/618770
http://www.discogs.sitioby.com/submissions?mode=merges&page=2#item=release/368294
http://www.discogs.sitioby.com/submissions?mode=merges&page=2#item=release/14008
http://www.discogs.sitioby.com/submissions?mode=merges&page=2#item=release/550049
http://www.discogs.sitioby.com/submissions?mode=merges&page=2#item=release/2322272
there maybe more...
also: re-requesting a merge after the current one has expired does not help:
http://www.discogs.sitioby.com/submissions?mode=merges&page=2#item=release/1785032
could management please acknowledge the bug? thanks!

needs to be put up for merge please:

http://www.discogs.sitioby.com/history?release=1953352#latest

Hi, I need some votes to merge this duplicate item:
http://www.discogs.sitioby.com/release/3668146

to: http://www.discogs.sitioby.com/Snakefingers-Vestal-Virgins-Night-Of-Desirable-Objects/release/735359

This was done by mistake some days ago by a submitter who agree to have made an error. He asked for removal but it failed due to the new merge procedure. So I ask now for a merge.

Thank you for the help fixing that situation.

Different release imo being merged and voted yes, please vote NO

http://www.discogs.sitioby.com/history?release=3053853

Center labels
http://s.dsimg.com/image/R-3053853-1313593117.jpeg
http://s.dsimg.com/image/R-618513-1335707318.jpeg

Why do merged releases end up in the submissions queue of the who initiated the merge?

Case in point: Various - Tomorrows World 2

This horror is apparently now my responsibility, just because I merged it following a rejected removal.

Merged releases should remain the responsibility of the last editor. I won't be starting further merges until the current behavior is changed.

seppuku, in the history it says

seppuku Edit Release The release data from 3665004 was transferred to this release. about 18 hours ago view changes revert

It's treated like any other edit.

It should be more similar to the removal process - failed removals revert to the last release editor, not the person who requested the removal.

Consider this: if you edited some random release, and later it was merged by someone else (with data transferred), would you want that reverted to the last editor?

Well, the ideal would be that the merged release reverts to the last editor of the release the data is taken from (first entry or second).

In any case, when it comes to duplicates I know nothing about in future, I'll just post the numbers here and let some other sucker take responsibility for them.

seppuku
This horror is apparently now my responsibility

good luck with that one :-)

VODAR
It's treated like any other edit.

apparently it is, but that is in fact a bit hard on the merger, see seppuku's example

VODAR
if you edited some random release, and later it was merged by someone else (with data transferred), would you want that reverted to the last editor?

that's not the same case IMO and hardly comparable

seppuku
Well, the ideal would be that the merged release reverts to the last editor of the release the data is taken from (first entry or second).

I agree that would be better

Mary Jane Girls - In My House

Had forgotten to actually initiate the merge. Merge request now initiated.

this awful subber (who never adds their own submissions to MRs but awaits for everyone else to do all the work) has subbed the same thing twice, Please vote YES to merge at least these:
Lipstique (2) - Venus / Funny Games

[EDIT Update]
And these:
David Bowie - China Girl

removal rejected, possible merge candidate: Motörhead - City Kids

nik
nik (Discogs staff) wrote:

Hi voters - following on from this topic, just to let you know (in case you are not aware of it yet) voters can now initiate merge release requests.

Cool enough except I am not a voter but I can initiate merge requests so what is with that? Anyone can do it now?

Please vote yes:

http://www.discogs.sitioby.com/history?release=2968441#latest
http://www.discogs.sitioby.com/history?release=3465079#latest

Please vote No... different label typography.

http://www.discogs.sitioby.com/history?release=2323287#latest

I've been having trouble merging 3 releases into 1.
Not sure if it's been discussed before, but first I assume you the 2 releases together in question & then wait for the votes.
Once voted in the main release stays with all the credits, collectors, sales etc, but then adding release 3 into the main release after votes takes away all the credits & original images, but keeps collectors, wantlists, sales etc?!

I've sorted it now I think but it's been a bloody nightmare ;0

I believe these need to be merged.

http://www.discogs.sitioby.com/history?release=3133389#latest

thanks.

Is this a bug or does every single voter on discogs have to vote

http://www.discogs.sitioby.com/submissions?mode=saved#item=release/3053853

I believe these can be merged:

http://www.discogs.sitioby.com/history?release=3366544#latest

Thanks.

http://www.discogs.sitioby.com/history?release=408618#latest
=
Uniform Choice - Screaming For Change

http://www.discogs.sitioby.com/history?release=3755556#latest
=
http://www.discogs.sitioby.com/Traks-Long-Train-Runnin/release/3445401
http://www.discogs.sitioby.com/Daniele-Baldelli-Long-Train-Runnin/release/3755556

please vote to merge these releases

http://www.discogs.sitioby.com/release/3699480

http://www.discogs.sitioby.com/Mariah-Carey-Fantasy/release/546130

k thx bye

Hi, I need some votes to merge this duplicate item:
http://www.discogs.sitioby.com/Residents-Moleshow-Live-At-The-Roxy-October-30-1982/release/3768303

...of this one:
http://www.discogs.sitioby.com/release/1475885

The recent one was submitted today by a new who want to sell his record (very expensive BTW), it is his first sub.

Unfortunately, I vote a CC vote instead of a CI vote before asked for this merge. Is there a way to cancel a vote made by mistake?

Thank you.

please vote for a merger on this release

http://www.discogs.sitioby.com/history?release=3303512#latest

new dupe was subbed as older sub had incomplete cat#.
thanks.

some merge votes needed here: UGK Featuring Outkast - International Player Anthem (Maker Remix)

submitted twice, probably some kind of bug. no idea why it was added twice, wasn't intended though

need votes to merge two identical entries subbed by the same within 4 minutes :)
http://www.discogs.sitioby.com/history?release=3450014#latest

please vote for merge

http://www.discogs.sitioby.com/history?release=478318#latest

this 7" was pressed only on white vinyl, info from official discography of the artist
http://noise.jupitter-larsen.com/

Hi.
Trying to merge 3 identical releases, one merge started: http://www.discogs.sitioby.com/history?release=2482834#latest

One release merged, now for another: http://www.discogs.sitioby.com/history?release=2482834#latest

Thanks.

Need NO votes on this merge here:
http://www.discogs.sitioby.com/history?release=586777#latest

^the US release (586777) incorrectly has the barcode number entered as a cat#, which also happens to be same number as the cat# on the European release (1925662).

A simple catalog number correction required on 586777 ( the cat# is 82137-1 and the barcode# is 7567-82137-1 )

Please vote yes for merge here:-

http://www.discogs.sitioby.com/history?release=639088#latest

First time using this, woot woot!

to be merged:

Tanita Tikaram - Twist In My Sobriety

I believe these are the same German/Europe 7":
#1 http://www.discogs.sitioby.com/Tanita-Tikaram-Twist-In-My-Sobriety/release/323866
#2 http://www.discogs.sitioby.com/Tanita-Tikaram-Twist-In-My-Sobriety/release/3599445

#1 appears to use an incorrect image for front sleeve, which matches the French 7": http://www.discogs.sitioby.com/viewimages?release=1808300 . That image was ed on its own 5 years ago by a who previously had not contributed to the release, and the rest (which are the same as on #2) later by other s. Credits for the two singles are the same, except #1 doesn't list TELDEC and barcode - but they appear on scans however. In a nutshell, the two are identical, except for the erroneously used French front sleeve. #2 has more complete credits, so I'm using that one's data for the merged release.

NO votes are needed here, please:

http://www.discogs.sitioby.com/history?release=3311163#latest

I thought I had submitted a dupe but the front cover artwork is different, as AndysWax points out in the comments. Thanks.

narcisco
http://www.discogs.sitioby.com/history?release=3755556#latest
=
http://www.discogs.sitioby.com/Traks-Long-Train-Runnin/release/3445401
http://www.discogs.sitioby.com/Daniele-Baldelli-Long-Train-Runnin/release/3755556

malformed sub, thought to be a duplicate. Voted yes then found out the label of the latter differs slightly.
There's some sort of a stalemate now. 4 YES against 10 NO
There need to be more NO votes, so this submission can be edited.

Appears to be no difference between these two.
Merge Requested (the one with the pic is older & the one chosen to remain - no info needs updating as they're otherwise identical)
Seekers, The - Roving With The Seekers - Younger sub = r3435857

Please vote for a Merge, so we get the one duplicate submission away ;)

Peter And The Wolf, double submission due to title
http://www.discogs.sitioby.com/history?release=3794385#latest

Gary Moore - Cold Day In Hell - Special Coll. Edition
http://www.discogs.sitioby.com/history?release=2452345#latest

Please vote for a merge of the identical G-Force album submissions:

http://www.discogs.sitioby.com/history?release=920105#latest

http://www.discogs.sitioby.com/history?release=3654288#latest

Another duplicated release to be merged:

http://www.discogs.sitioby.com/history?release=3006368#latest