JBoDM #4 - 6) Review of the repatriation procedure after recent difficulties

Matt's writeup

1) It was decided at the last TM that repatriation would automatically occur after a conference was published. 2) The Team agreed to include me in the publication notification list so I would know it was time to repatriate. 3) As part of the repatriation process all batch jobs were stopped. 4) Christine believes the email batch job needs to keep running. 5) I concur and will update the repatriation routine to keep the email job running.

Repatriation does not affect the functionality of SPMS with the exception of synchronization. Once repatriated, a conference my no longer sync with the main repository, which was determined to be not necessary by the Team.

As far as I'm concerned we are following the agreed upon process and there are no unresolved issues. I do not wish to postpone the repatriation based on the editor's request at some future date. With the exception of Christine, I don't believe many editors would remember to notify me. This was the issue that brought about the discussion at the last TM and the decision to update the publication process to include repatriation.