Ability to rehash and rensend files to anidb in the utility menu & duplicate files (anidb moved the file)

[GoogleCodeExporter]

As you might know, anidb is not bulletproof, some users tag the files in the 
wrong place. Since JMM do not support (YET) receiving anidb Messages from the 
system telling file moves.

Like this one:

This is an automated message notifying you that an AniDB moderator moved a file 
which is part of your mylist.
There is no action required on your part.

The following file has been moved:

fid: 1200880
old anime: Seitokai no Ichizon Lv.2 (9090)
old ep: 7 - The Student Council Welcomes (145193)
new anime: Seitokai no Ichizon Lv.2 (9090)
new ep: 8 - Size S Hunter (145877)
moved by: keitarou (1294)

A button that enable the users to re-send the episode hash to anidb, and 
correct the data.
Steps: 
1) Delete all episode information including anidb data.
2) Send the episode hash to anidb.
3) Profit.

A better solution will be download all system messages. loop them, check for 
file moves, and do the above on every moved file.

if you like i could check the feasibility of that and give you a functional 
code to add to JMM.

Original issue reported on code.google.com by maximo.p...@nutzcode.com on 25 Apr 2013 at 12:57

[GoogleCodeExporter]

We should ask to add extensions to the anidb notification to correctly handle 
the file moves. Since you already have a connection with anidb dewds, here are 
the needs.
Correct me if i'm wrong.

Extensions to the NOTIFY,NOTIFYLIST and NOTIFYACK commands, for correctly 
handle (in parallel with the web site) file move messages.

NOTIFY [buddy=1] [read=1]

when read=1 
Include read messages

NOTIFYLIST [read=1]

when read=1 
Include read messages

NOTIFYACK type={str type}&id={int4 id}

NOTIFYACK type={str type}&id={int4 id}&delete=1

when delete = 1 and type=M
delete message instead of mark as read.

With this extensions, file moving inside the clients can be independent of the 
user behavior, reading messages in the website.
Otherwise if the user read the file move message before the client, the client 
will never get the file move message, because is mark as read.

Original comment by maximo.p...@nutzcode.com on 25 Apr 2013 at 1:47

[GoogleCodeExporter]

Good suggestion, I'll see what can be done

Original comment by werndly...@gmail.com on 1 May 2013 at 4:23

• Changed state: Accepted
• Added labels: Product-JMM

[GoogleCodeExporter]

https://github.com/japanesemediamanager/jmmserver/issues/55

Original comment by werndly...@gmail.com on 19 Aug 2014 at 10:45

• Changed state: Migrated