user1908: A couple months ago, it was brought up that we should really figure out what to do about the outstanding [identification-request] questions. The immediate impetus for this was probably the realization that [identification-request]  was showing up on the front page as one of our top tags despite being blacklisted. Thankfully, this was fixed pretty quickly. However, the question remains: what, if anything, should we do about the remaining id-reqs?
In this post, Logan proposes (as option #4) that they all be retagged to use the tag of the series in question, with the identification-request tag removed. For example, What manga is this image with a depressed girl from? would be retagged to watamote. Gao posted another answer in support of this solution. 
I propose that we implement Logan's solution. Note that this will require moderators to do all the retagging, since all the remaining id-reqs are historical-locked - but I'm willing to spend the time doing this, and the other moderators can of course spend the time if they'd like as well. 
If, after a suitable length of time (say, a month or so), people are in agreement with this proposal, I'll start retagging the id-reqs (in small batches, so as not to flood the front page with crap).
This does make it non-trivial to identify the id-reqs that survived the Great Identification Request Cleanup of 2016... unless you use the power of SEDE.

Update (8 Feb 2017): Given that it's been a month and nobody seems to be opposed to this plan, I'm going to start retagging [identification-request] questions in small batches. 

user1908: It's done!
We started with about 396 [identification-request] questions; now, we're down to 27. The remaining questions generally fall into one or more of the following categories: 

the identified thing was non-derivative, non-published content
the identified thing was porn
the identified thing was a one-shot manga chapter
the identified thing was Western animation
the answers offered multiple options, none of which was obviously correct

This is a huge improvement! [identification-request] is now only our 49th-most-popular tag (by number of questions), putting it well out of sight for casual passersby. I also removed all of the synonyms from the tag, to reduce the odds that somebody will find the tag while typing things into the tag-picker field when asking a question.
Questions affected by this retagging effort:
Run this SEDE query.
Tags created by this retagging effort
Run this other SEDE query. Note that this might take a while because I can't into efficient SQL. 
There are going to be a few tags (on the order of a dozen or so) that are effectively created by this retagging effort that aren't captured by this query. This mostly happens in cases where the identified work's tag was added to the question (thereby creating the tag in the database) and then removed shortly thereafter, e.g. https://anime.stackexchange.com/posts/2379/revisions. 

1908: <p>A couple months ago, <a href="https://anime.meta.stackexchange.com/q/3949/">it was brought up</a> that we should really figure out what to do about the outstanding [identification-request] questions. The immediate impetus for this was probably the realization that [identification-request]  <a href="https://anime.meta.stackexchange.com/q/3944/">was showing up on the front page as one of our top tags</a> despite being blacklisted. Thankfully, <a href="https://anime.meta.stackexchange.com/a/3974/">this was fixed pretty quickly</a>. However, the question remains: what, if anything, should we do about the remaining id-reqs?</p>

<p>In <a href="https://anime.meta.stackexchange.com/a/3959/">this post</a>, Logan proposes (as option #4) that they all be retagged to use the tag of the series in question, with the <a href="https://anime.stackexchange.com/questions/tagged/identification-request" class="post-tag" title="show questions tagged &#39;identification-request&#39;" rel="tag">identification-request</a> tag removed. For example, <a href="https://anime.stackexchange.com/q/4122/">What manga is this image with a depressed girl from?</a> would be retagged to <a href="https://anime.stackexchange.com/questions/tagged/watamote" class="post-tag" title="show questions tagged &#39;watamote&#39;" rel="tag">watamote</a>. Gao posted <a href="https://anime.meta.stackexchange.com/a/3993/">another answer</a> in support of this solution. </p>

<p>I propose that we implement Logan's solution. Note that this will require moderators to do all the retagging, since all the remaining id-reqs are historical-locked - but I'm willing to spend the time doing this, and the other moderators can of course spend the time if they'd like as well. </p>

<p>If, after a suitable length of time (say, a month or so), people are in agreement with this proposal, I'll start retagging the id-reqs (in small batches, so as not to flood the front page with crap).</p>

<p>This does make it non-trivial to identify the id-reqs that survived the Great Identification Request Cleanup of 2016... <a href="http://data.stackexchange.com/anime/query/672834/" rel="nofollow noreferrer">unless you use the power of SEDE</a>.</p>

<hr>

<p><strong>Update (8 Feb 2017):</strong> Given that it's been a month and nobody seems to be opposed to this plan, I'm going to start retagging [identification-request] questions in small batches. </p>
 1908: <h3>It's done!</h3>

<p>We started with about 396 [identification-request] questions; now, we're down to 27. The remaining questions generally fall into one or more of the following categories: </p>

<ul>
<li>the identified thing was non-derivative, non-published content</li>
<li>the identified thing was porn</li>
<li>the identified thing was a one-shot manga chapter</li>
<li>the identified thing was Western animation</li>
<li>the answers offered multiple options, none of which was obviously correct</li>
</ul>

<p>This is a huge improvement! [identification-request] is now only our 49th-most-popular tag (by number of questions), putting it well out of sight for casual passersby. I also removed all of the synonyms from the tag, to reduce the odds that somebody will find the tag while typing things into the tag-picker field when asking a question.</p>

<h3>Questions affected by this retagging effort:</h3>

<p>Run <a href="http://data.stackexchange.com/anime/query/667619/" rel="nofollow noreferrer">this SEDE query</a>.</p>

<h3>Tags created by this retagging effort</h3>

<p>Run <a href="http://data.stackexchange.com/anime/query/668009/" rel="nofollow noreferrer">this other SEDE query</a>. Note that this might take a while because I can't into efficient SQL. </p>

<p>There are going to be a few tags (on the order of a dozen or so) that are effectively created by this retagging effort that <em>aren't</em> captured by this query. This mostly happens in cases where the identified work's tag was added to the question (thereby creating the tag in the database) and then removed shortly thereafter, e.g. <a href="https://anime.stackexchange.com/posts/2379/revisions">https://anime.stackexchange.com/posts/2379/revisions</a>. </p>
