OJS OCS OMP OHS

You are viewing the PKP Support Forum | PKP Home Wiki



cleaning up editor's submission queue

Are you responsible for making OJS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.

Moderators: jmacgreg, btbell, michael, bdgregg, barbarah, asmecher

Forum rules
What to do if you have a technical problem with OJS:

1. Search the forum. You can do this from the Advanced Search Page or from our Google Custom Search, which will search the entire PKP site. If you are encountering an error, we especially recommend searching the forum for said error.

2. Check the FAQ to see if your question or error has already been resolved.

3. Post a question, but please, only after trying the above two solutions. If it's a workflow or usability question you should probably post to the OJS Editorial Support and Discussion subforum; if you have a development question, try the OJS Development subforum.

cleaning up editor's submission queue

Postby benhunter » Wed Jun 13, 2007 4:02 pm

Hi,

We're currently in the process of transitioning our journal (24 issues) into OJS. We had a student worker import all of our old issues using the "Articles & Issues XML Plugin." There were some problems with the first import, so we deleted the articles (not through OJS) and re-imported all of the old issues. Everything is looking fine and falling into place now.

The problem is that the Editor has over 2300 "Unassigned" articles. Some seem to be leftovers from the previous import, and others seem to actually be part of published issues (when archived they disappear from the published issue).

Going through and manually archiving-deleting dead articles and putting live articles through the review process is too time consuming to consider. Is there a way get the "Unassigned" queue down to zero?

Thanks,
Ben
benhunter
 
Posts: 3
Joined: Wed Jun 13, 2007 3:37 pm

Postby asmecher » Wed Jun 13, 2007 4:07 pm

Hi Ben,

When writing XML for large numbers of import articles, I'd typically recommend working with a temporary install in order to get the XML right, then start with a clean install for the production import. This is much easier to clean up.

However, for the situation you describe, it should be possible to clean up with a PHP hack. You need a way of determining all the valid article IDs that you want to keep; then use $articleDao->getArticlesByJournalId(...) to loop through all articles and delete them if they're not in that list using $articleDao->deleteArticle(...). Of course, do a full backup before attempting this.

Regards,
Alec Smecher
Public Knowledge Project Team
---
Don't miss the First International PKP Scholarly Publishing Conference
July 11 - 13, 2007, Vancouver, BC, Canada
http://ocs.sfu.ca/pkp2007/
asmecher
 
Posts: 8345
Joined: Wed Aug 10, 2005 12:56 pm

Postby benhunter » Thu Jun 14, 2007 9:55 am

Thanks for your quick reply Alec, I'll give that a shot.

Ben
benhunter
 
Posts: 3
Joined: Wed Jun 13, 2007 3:37 pm

Postby benhunter » Fri Jun 15, 2007 12:18 pm

Hi,

We ended up going into the MySQL database and deleting all records where the status field was 1. The records we wanted to keep had a status of 3, so they didn't get touched. Seems to have done the trick (queue is down to 0, and the journal is intact), and it only took a couple of minutes. It's one more option for anyone who finds themselves in the same situation as us.

Ben
benhunter
 
Posts: 3
Joined: Wed Jun 13, 2007 3:37 pm


Return to OJS Technical Support

Who is online

Users browsing this forum: Google [Bot] and 4 guests