OJS 3.3 Importing back issues for a non OJS site (in this case EBSCO)

Hi

We have a new journal joining our collection and this journal comes with over 20 years of back issues. This back issues are available as just PDFs saved on a website and via EBSCO which has the metadata as well.

We are really keen to not Quick Submit 20 years of articles so has anyone ever imported issues from EBSCO or another (not OJS) site and if so can you tell us about it?

Thank you

1 Like

Hi,

you may use tools such as GitHub - ajnyga/tsvConverter: Excel to OJS3 XML conversion tool or GitHub - ualbertalib/ojsxml: converts a csv file to ojs native import xml to convert CSV metadata into OJS Native XML format for import. However, they support import only for OJS 3.3.

1 Like

Hi @Tuwpub ,

just yesterday I published a new version of the tsvConverter tool.

I did some testing with real world data but didnā€™t have a use case yet as big as your. If you want to try it out Iā€™m happy to support you if necessary and fix any issues that might occur.

Best wishes,
Ronald

2 Likes

Thanks @ronste1 really appreciate the offer and your work on the tool. Iā€™m hoping to get on to this next week so will at the least give you feedback.
cheers, Craig

1 Like

Hi @ronste1,
Iā€™ve just converted and uploaded one article via your updated tsvConverter tool and it looks to have worked wonderfully well.

One very minor issue to note - in the Issues & Sections table of the documentation the field issueDatepublished is listed. I believe this needs to be issueDatePublished (capital P) for the script to work. Itā€™s correct in the example files.
cheers, Craig

1 Like

Iā€™ve just loaded up 20 years of back issues to our prod journal, from an Ebsco csv export, run through the tsvConverter. FYI it was done as a single upload - the only issues being the need to increase ā€œpost_max_sizeā€ and ā€œupload_max_filesizeā€ in php.ini and a temporary bump in memory.

What awesome work by everyone involved with the plugin, and thank you @ronste1 for your updated version! This has saved my colleagues weeks of tiresome, dull and error-prone manual work.
cheers, Craig

Hi @cmurdoch ,

thanks for the feedback. Great to hear everything worked smoothly!

I will add hints to setting the upload and post size to the Readme file. This will probably be a frequent issue when importing larger sets of publications.

Best wishes,
Ronald