Suport de The Movie Database
Suport → Suport de l'API
Feature Request: Redirect on merged movies
publicat per Raymond WagnerSTAFFMOD el dia 5 n de 2013 a les 5:14 P.M.
Periodically, movies will get duplicated, and then one or more is deleted. If we try to access those subsequently deleted movies, we get an error code 6, with the message, "Invalid id - The pre-requisite id is invalid or not found". It would be useful to have a special error code when content was deleted as a duplicate, with reference to the new ID.
Resposta per Travis Bell
el 5 n de 2013 a les 11:22 P.M.
Hey Raymond,
I can see where you're coming from but that would require someone entering the new ID when it actually gets deleted which would make deleting movies a lot more work (this is entirely a manual process right now).
I'll think about this in the future but I don't think this will end up on my radar for a while. Thanks.
Resposta per Karl Dietz
el 6 n de 2013 a les 2:25 P.M.
Do you ever simply delete a movie as a duplicate? In my experience its basically always a merge of two entries for the same movie into one, thus leaving one ID unused but keeping all data from both entries. Thus I'm wondering if reporting a movie as duplicate should ask the user which item it is a duplicate of? E.g. by simply pasting in the URL of the "master". (giving the master url/ID its own field) A moderator could then open the redundant entry, move all translations, pictures, etc over to the master entry (From my understanding that is what they do now, too) and at the end of the process hit the "I'm done moving, delete it" button on the duplicate, which would look into the list of open duplicate reports and suggest which movie everything got moved into, maybe closing multiple discussions if the duplicate was reported more then one time.
Resposta per Möhre
el 8 n de 2013 a les 10:27 A.M.
Hi Travis, i would prefer Karl's way too. I always use fields like "deleted" (timestamp) and "duplicated_id" (int) to have the possibility to maintenance/merge the removed dataset. All queries can get filtered by these fields and if it is to much work to rebuild all the queries, just use e.g. views (if the db allows you).
Resposta per Travis Bell
el 8 n de 2013 a les 10:41 A.M.
Yes, that could exist one day but it's a fairly massive change since it affects everything. Every association (cast, reviews, images ratings, favourites, etc… etc…) and search would have to be updated. Would it be better? Sure, but given the list of other things I have to do I regard this as fairly low priority.
In fact, there is already a ticket open to deal with this first part. Extending that functionality to make duplicate handling better would be easy enough at that point.
Resposta per Möhre
el 8 n de 2013 a les 11:17 A.M.
I agree there is higher prio stuff - I didn't want to get you in hurry. Maybe it is possible to help you with little coding somehow?