seq-Field not working

[errotu]

Thank you for this great tool!

We are currently using it to migrate our journal to OJS. Unfortunately, it seems like the seq-Field does not have any effect. The articles appear unordered in OJS. I took a quick look into the generated xml-file and it seems like "seq" is always filled with a zero:

<seq>0</seq>

Is is possible that the converter currently ignores the value in the given xslx-file?

[ajnyga]

hi!

Yes true, I usually order the sheet with Excel using the issueDatePublished and seq fields. The original plan was to do this automatically in the script but I recall having some issues with the excel library I am using which I could not solve. To put it simply, I forgot about this and have not bumped to the issue myself because do the ordering outside the script.

I will fix this probably, but can not promise a quick schedule. Probably when I upgrade this for OJS 3.3

[errotu]

Thank you for the quick reply!

Is the order in the Excel sheet taken into account while doing the XML conversion and later respected by OJS? I feel like there is no order at all (it actually even changes when I refresh the website) before I open the configuration and explicitly save one specific order.

[ajnyga]

sorry i've missed this other question.

The order is saved to the xml. I am aware that there are cases where it seems like the order does not work, but this is a problem in the OJS import itself. Things that might affect it are for example the order of sections you have in journal settings. Also the issue order depends where you are checking it. If I remember correctly, the public issue archive will show the order based on the issueID if no other data is available and the internal archive for editors uses the datestamp. What I always do is that I save the order from Issues > Old Issues so that the one with datestamps is used also in the frontend.