S

147 Messages

 • 

1.9K Points

Monday, July 11th, 2022 11:58 AM

Closed

Solved

Random System or human denials of keyword deletions that make no sense

I just tried to delete a "timeframe-2010s" from a Korean drama set in the 15h century Joseon dynasty. It went into screening and got denied.

I cannot understand, if a human is involved here, the thought process. Wasn't "timeframe-2010" bought in to try and stop users from tagging series and movies from having their year tagged by when they came out, as opposed to their setting?

I've also had a number of other weird keyword denials that are blatantly obvious. Someone denied me trying to remove "sword and sandal history" from a show set in a medieval setting. I have the references, but I'm genuinely baffled by this occasional tendency, and it's highly frustrating because things I thought were obvious have to start debates.

2.7K Messages

 • 

47K Points

2 years ago

"timeframe-" keywords have a very high level of protection.

Based on what was previously happening (a couple months ago) with keywords with main genre suffixes, I have my doubts about whether any humans actually see attempted removals of "timeframe-" keywords (in at least some cases).

cc: @Peter_pbn 

147 Messages

 • 

1.9K Points

@keyword_expert​ Yet, paradoxically... if you *convert* any keyword it often does it instantly without a fuss - despite it essentially being the same as deletion. And that actually seems include 'protected' words.

(edited)

Employee

 • 

17.5K Messages

 • 

313.5K Points

2 years ago

Hi Skavau -

Regarding your request to remove the Plot Timeframe keyword "timeframe-2010s", can you post the 18-digit submission reference number associated with this declined request as well as the other updates you referenced?  Once we have this information IMDb staff can investigate further.

147 Messages

 • 

1.9K Points

@Michelle

#220711-014710-236000 (The K-Drama)
#220710-185438-194000 (Pillars of the Earth)

(edited)

Employee

 • 

5.6K Messages

 • 

58.7K Points

Hi Skavau-

The request for this keywords deletions have been resubmitted on your behalf and approved.

Cheers!

147 Messages

 • 

1.9K Points

@Bethanny​ I have more as well... problem is, that's fine and thank you.. but am I going to have to go through this every time a keyword has "history" or "timeframe" or another protected word in the title?

There are a lot of errors on those tags.

Employee

 • 

5.6K Messages

 • 

58.7K Points

Hi Skavau- 

There should not be any more problems as this was more of a system issue than an error while processing, but please do let me know if there are any more problems.

Cheers!

2.7K Messages

 • 

47K Points

2 years ago

I can confirm from personal experience that, as of today, "timeframe-" keywords indeed remain "protected." As a result, contributions that delete "timeframe-" keywords are routinely denied after about a 48-hour wait.

The workaround solution is to correct false "timeframe-" keywords to a more applicable "timeframe-" keyword. Modifications like this are approved in a few minutes or less.

Champion

 • 

14.4K Messages

 • 

330K Points

@keyword_expert​ 

The workaround solution is to correct false "timeframe-" keywords to a more applicable "timeframe-" keyword.

I have a correction like this recently that was approved, but when I checked the page the old keyword was still there along with the new one.

2.7K Messages

 • 

47K Points

@Peter_pbn​ Wow! Same thing happened to a recent correction of mine: both keywords currently appear on the keyword page, about 48 hours after my contribution was "approved."

Contribution #220728-160230-197000 

https://www.imdb.com/title/tt5610554/keywords

This confirms that "timeframe-" keywords enjoy super-protection. I have never seen anything like this with any other type of keyword.

@Bethanny

@Michelle 
I think it's time for IMDb staff to consider undoing the protections for "timeframe-" keywords. I understand how you wanted to protect these keywords as they were being developed system-wide, but at this point the special protection of these keywords is only resulting in bad data persisting in the system.

Champion

 • 

14.4K Messages

 • 

330K Points

2 years ago

Recent examples of declined timeframe- deletions:

#220726-091609-415000

#220729-053753-798000

Employee

 • 

17.5K Messages

 • 

313.5K Points

Hi @Peter_pbn​ -

Thanks for posting these examples, these Timeframe keywords have now been removed.

Cheers!

Employee

 • 

17.5K Messages

 • 

313.5K Points

2 years ago

Hi Skavau & All -

Thanks again for the reports and submission examples of declined Timeframe keywords. 

Upon further investigation, I have identified a systematic bug that has impacted these submissions and I have filed a ticket for the appropriate team to fix.  As soon as I have an update I will confirm the status here.

Cheers!

2.7K Messages

 • 

47K Points

2 years ago

Has anyone recently tried to delete or edit a "timeframe-" keyword, and if so, how did the experience go?

The last time I tried was about 9 days ago, and the deletion was denied.

Apparently the protection of "timeframe-" keywords is still in place.

Contribution #221016-175321-021000

(edited)

Champion

 • 

14.4K Messages

 • 

330K Points

Corrected timeframe-21th-century to timeframe-21st-century on one title last week. For a short time the page displayed both versions, but it was updated eventually.

Employee

 • 

5.6K Messages

 • 

58.7K Points

@keyword_expert​ Hi! It actually is not protected anymore, checking on your submission it was not accepted in error, nothing to do with the protection they used to have, I resubmitted on your behalf and approved.

Cheers!

2.7K Messages

 • 

47K Points

@Bethanny​ There must be at least some kind of "protection" on the timeframe keywords -- enough to trigger manual review by staff. Normally, the vast majority of keyword deletions and edits are automatically approved within 5 minutes, without any staff review. It seems that timeframe keywords are still being handled differently. The next time I try to delete one, I will follow up in this thread.