<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Oldest Article Submission to Newest</title>
	<link>http://blog.ezinearticles.com/2006/10/oldest-article-submission-to-newest.html</link>
	<description></description>
	<pubDate>Sun, 06 Jul 2008 01:18:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Edward Weiss</title>
		<link>http://blog.ezinearticles.com/2006/10/oldest-article-submission-to-newest.html#comment-4557</link>
		<pubDate>Mon, 16 Oct 2006 05:36:52 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2006/10/oldest-article-submission-to-newest.html#comment-4557</guid>
					<description>Here's an idea.... speed reading! I used to write abstracts and had to be able to quickly go through entire journal articles to glean significant info fast. Might be worth it to teach your team how to speed read. 

And what they say about higher retention rates is true! When you know how to skip and skim for specific information, it really helps.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s an idea&#8230;. speed reading! I used to write abstracts and had to be able to quickly go through entire journal articles to glean significant info fast. Might be worth it to teach your team how to speed read. </p>
<p>And what they say about higher retention rates is true! When you know how to skip and skim for specific information, it really helps.<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ed Howes</title>
		<link>http://blog.ezinearticles.com/2006/10/oldest-article-submission-to-newest.html#comment-4554</link>
		<pubDate>Mon, 16 Oct 2006 01:42:35 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2006/10/oldest-article-submission-to-newest.html#comment-4554</guid>
					<description>Chris,

Thank you for the most complete and satisfying responses I have ever received on the internet. :-)</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>Thank you for the most complete and satisfying responses I have ever received on the internet. :-)<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Christopher M. Knight</title>
		<link>http://blog.ezinearticles.com/2006/10/oldest-article-submission-to-newest.html#comment-4553</link>
		<pubDate>Mon, 16 Oct 2006 00:50:23 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2006/10/oldest-article-submission-to-newest.html#comment-4553</guid>
					<description>Ed,

I personally reviewed the first 30,000+ articles and never got bored of reviewing them...so I don't think that is an issue for most.

The editors are scanning the article for mechanics (does the article meet the 5.5 pages of editorial guidelines or not) as that consumes a high majority of their article approval attention.

It's not like they are grabbing a coffee and sitting down to read every word of every article slow enough to comprehend the content as there isn't time for that. Between checking the content for originality and exclusivity of license (ie: Can the article be found anywhere else under someone else's name) and reviewing the HTML code syntax and sentence structure and briefly the content, they are on to the next article.

There isn't a lot of turn over, so that hasn't become a problem.

Yes, editors who have been with us longer do assist in the training of newbie editors.

We have an internal training system (that's documented) that continually gets updated and added to in addition to daily internal communications to keep everyone on top.

In terms of breaks, there are many duties that editors perform beyond the basic article review and approval... from re-reviews of edited articles that need to be approved again to Platinum upgrade requests, new membership registrations to review, new alternate authors to review, new photos uploaded to eyeball, making notes on an authors account, manually adding/reviewing articles in batches based on bulk submissions from approved authors, new extended author bio's to review, new comments on articles to approve or reject, quality control review of approved articles, and the list goes on for at least another dozen items or more.</description>
		<content:encoded><![CDATA[<p>Ed,</p>
<p>I personally reviewed the first 30,000+ articles and never got bored of reviewing them&#8230;so I don&#8217;t think that is an issue for most.</p>
<p>The editors are scanning the article for mechanics (does the article meet the 5.5 pages of editorial guidelines or not) as that consumes a high majority of their article approval attention.</p>
<p>It&#8217;s not like they are grabbing a coffee and sitting down to read every word of every article slow enough to comprehend the content as there isn&#8217;t time for that. Between checking the content for originality and exclusivity of license (ie: Can the article be found anywhere else under someone else&#8217;s name) and reviewing the HTML code syntax and sentence structure and briefly the content, they are on to the next article.</p>
<p>There isn&#8217;t a lot of turn over, so that hasn&#8217;t become a problem.</p>
<p>Yes, editors who have been with us longer do assist in the training of newbie editors.</p>
<p>We have an internal training system (that&#8217;s documented) that continually gets updated and added to in addition to daily internal communications to keep everyone on top.</p>
<p>In terms of breaks, there are many duties that editors perform beyond the basic article review and approval&#8230; from re-reviews of edited articles that need to be approved again to Platinum upgrade requests, new membership registrations to review, new alternate authors to review, new photos uploaded to eyeball, making notes on an authors account, manually adding/reviewing articles in batches based on bulk submissions from approved authors, new extended author bio&#8217;s to review, new comments on articles to approve or reject, quality control review of approved articles, and the list goes on for at least another dozen items or more.<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ed Howes</title>
		<link>http://blog.ezinearticles.com/2006/10/oldest-article-submission-to-newest.html#comment-4552</link>
		<pubDate>Mon, 16 Oct 2006 00:29:27 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2006/10/oldest-article-submission-to-newest.html#comment-4552</guid>
					<description>Hey Chris,

It seems to me this will be a recurring problem as growth cycles may not be predictable enough to have new staff trained and ready. Why not have an alternative message for your submission acknowledging auto responder to alert basic members of the temporarily extended turn around time, since they will not likely see this blog post?

I like to read - when the content is of interest to me. Yet, even if I could check only content of interest to me, I can't imagine doing this editing job more than four hours per day or for more than a few months. Is there a lot of turnover in the editorial staff? Do senior editors train new staff or have additional options to give them a break? I have been curious about this for many months.</description>
		<content:encoded><![CDATA[<p>Hey Chris,</p>
<p>It seems to me this will be a recurring problem as growth cycles may not be predictable enough to have new staff trained and ready. Why not have an alternative message for your submission acknowledging auto responder to alert basic members of the temporarily extended turn around time, since they will not likely see this blog post?</p>
<p>I like to read - when the content is of interest to me. Yet, even if I could check only content of interest to me, I can&#8217;t imagine doing this editing job more than four hours per day or for more than a few months. Is there a lot of turnover in the editorial staff? Do senior editors train new staff or have additional options to give them a break? I have been curious about this for many months.<br />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jeff Herring - The Article Guy</title>
		<link>http://blog.ezinearticles.com/2006/10/oldest-article-submission-to-newest.html#comment-4551</link>
		<pubDate>Sun, 15 Oct 2006 23:30:10 +0000</pubDate>
		<guid>http://blog.ezinearticles.com/2006/10/oldest-article-submission-to-newest.html#comment-4551</guid>
					<description>Hi Chris

Nope. Did not notice any delay here. You have an awesome machine, one to be admired.

As I said on our teleseminar last week, you guys are a great example of constant and never ending improvement.

Jeff</description>
		<content:encoded><![CDATA[<p>Hi Chris</p>
<p>Nope. Did not notice any delay here. You have an awesome machine, one to be admired.</p>
<p>As I said on our teleseminar last week, you guys are a great example of constant and never ending improvement.</p>
<p>Jeff<br />
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
