Allow to ''merge file and change type'' [DONE/DENIED]
Moderator: AniDB
Allow to ''merge file and change type'' [DONE/DENIED]
... specifically for one purpose: To easily get rid of corrupted 1*-user-files.
There would be no reason to leave such files in if there was a function to merge the 1*-user-file with the CRC-correct one while at the same time changing the type of it to "corrupted version/invalid crc" for those who have it.
*) Actually, I wouldn't hesistate to merge corrupted files with 3 users either ^^
There would be no reason to leave such files in if there was a function to merge the 1*-user-file with the CRC-correct one while at the same time changing the type of it to "corrupted version/invalid crc" for those who have it.
*) Actually, I wouldn't hesistate to merge corrupted files with 3 users either ^^
I think this is a good idea.
Perhaps, you could merge it and change the 'type' field for the users with the incorrect crc to "corrupted version/invalid crc".
A automatically generated private message might be good as i would assume most people wouldn't check the crc against the one filed in the db and might actually have the correct version (as opposed to the person who originally filed the entry) and then they can change the type back to "normal/original" themselves. Or perhaps, I'm just complicating the situation.
Perhaps, you could merge it and change the 'type' field for the users with the incorrect crc to "corrupted version/invalid crc".
A automatically generated private message might be good as i would assume most people wouldn't check the crc against the one filed in the db and might actually have the correct version (as opposed to the person who originally filed the entry) and then they can change the type back to "normal/original" themselves. Or perhaps, I'm just complicating the situation.
Hm,
I don't think we should merge files if more than one user has them in their mylist. This shows that the files have somehow "spread" and it's likely that some other user will end up with the same file.
By merging the corrupted file with the correct one we would make it impossible for AoM to identify these files.
To ensure that only one user has a given corrupted file I think we should wait at least 4 weeks before we merge/remove a file based on the amount of users who have it in mylist.
BYe!
EXP
I don't think we should merge files if more than one user has them in their mylist. This shows that the files have somehow "spread" and it's likely that some other user will end up with the same file.
By merging the corrupted file with the correct one we would make it impossible for AoM to identify these files.
To ensure that only one user has a given corrupted file I think we should wait at least 4 weeks before we merge/remove a file based on the amount of users who have it in mylist.
BYe!
EXP
even in this case others might have that corrupted file and might want to use AoM to identify it. deleting it would then most likely only lead to someone readding that file later.wahaha wrote:When I wrote that I'd also merge a corrupted file if it has 3 users I had a situation like "CRC valid file: >100 users // CRC invalid file: 3 users" in mind. Keeping such an entry isn't worth much, IMO
BYe!
EXP
I agree with exp, if they are already in the DB, leave them, if they are being shared, they will just come back again at some point.
Also, just because a particular hash has more users in AniDB, that does not mean there are sources out there that reflect those numbers. I have had a few times where it was much easier to download a hash that listed only a few users than one that had a lot (I only do this if I can't get complete sources after a few weeks and/or no hash is marked as CRC valid).
I have actually used cases like this where the valid file does not have complete sources. I download the corrupted version, and when it completes parts that are missing in the valid file, I reshare that file as a valid file. A few times I have lucked out and the part(s) that were corrupted were not the parts I that were missing, so I was able to build a complete CRC valid file.wahaha wrote:When I wrote that I'd also merge a corrupted file if it has 3 users I had a situation like "CRC valid file: >100 users // CRC invalid file: 3 users" in mind. Keeping such an entry isn't worth much, IMO, but I'm fine with leaving it alone.
Also, just because a particular hash has more users in AniDB, that does not mean there are sources out there that reflect those numbers. I have had a few times where it was much easier to download a hash that listed only a few users than one that had a lot (I only do this if I can't get complete sources after a few weeks and/or no hash is marked as CRC valid).