This reminds me of some questions about article/issue publishing.  Can we assume 
 - that an article is only available for harvesting if the issue it is in is published? - that once an issue is published, article supplementary files are not changed/uploaded?
If so then it sounds like we avoid the issue of a harvester catching an article/supplementary file before it is ready for prime time?
Otherwise, if article supplementary files are being messed with by layout editors AFTER issue publishing, then we do have a problem.
d. 

----------------------------------------
From: "Alec Smecher" <notifications@github.com>
Sent: Tuesday, August 13, 2013 9:52 AM
To: "pkp/ojs" <ojs@noreply.github.com>
Cc: "Damion Dooley" <damion@learningpoint.ca>
Subject: Re: [ojs] XML plugin -- corrections made (#92)

In plugins/xmlMarkup/MarkupPlugin.inc.php: 

> + > +		// In all other cases... > +		return false; > +	} > +	 > +	/** > +	* Set Supplementary file's creator field to show status of document conversion process. > +	* Returns message; this may be displayed if appropriate. > +	* > +	* @param $msg string  > +	* @param $suppFile object (supplementary file record) > +	* @param $suppFileDao object primed with article > +	*/ > +	function _exitFetchStatus($msg, &$suppFile, &$suppFileDao) { > +		if ($suppFile) { > +			$suppFile->setCreator(__('plugins.generic.markup.archive.status') . $msg ,  AppLocale::getLocale());//'en_US');   

I worry about hacking the Creator field for this. What happens if a journal is harvested via OAI and it catches in-progress content? The status messages may end up in external systems.  

-
Reply to this email directly or view it on GitHub.