1) Issue’s status in the plugin is “In progress” but it is “Deposited” in the onix.csv file
Looking at the plugin “status” tab, I see some journals issues whose status is “In progress” (see screenshot below).
If I check on this file https://pkp.sfu.ca/files/pkppn/onix.csv
those issues are listed with a “Deposited date” (see screenshot below)
2) Issue’s status in the plugin is “In progress” but it is not listed in the onix.csv file
Looking at the plugin “status” tab, I see some issues whose status is “In progress” (see screenshot below).
If I check on this file https://pkp.sfu.ca/files/pkppn/onix.csv
those issue are not listed at all
Checking the scheduledTasks log files I see the following XML errors related to the same issue (Vol. 27 No. 2 - Issue ID: 826)
[2025-01-18 09:58:01] [Notice] Trying status update for 100 (Issue: 826) (Local Status: [Transferred], Processing Status: [Received], Lockss Status: [Unknown])
[2025-01-18 09:58:02] [Notice] Processing status got for 100 -> (xml-error)
I did try to export the issue using the tool in “Tools > Native XML Plugin” to check for xml errors,
but no errors are shown and the xml file is correctly exported.
I’m using OJS 3.3.0-8 and PKP|PN (PKP Preservation Network) Plugin v2.0.4.
I’ve recently updated the PKP-PN Plugin. In the previous version of the plugin there were already problem with the deposit but the deposit status in the plugin was “error” for almost all the issues where now is “In progress”
Maybe @jonasraoni or someone else can help me here?
The issues you’ve mentioned are still in progress, when the content appears at the ONIX file, it just means that we’ve sent the file to be preserved, the status will move to completed once most of the nodes in the network receive the deposit.
Regarding the vol 27/2, the “XML error” means that the deposit failed to be validated on our side, and the reason is a bug on your OJS application. If you upgrade it to the latest OJS 3.3.X (currently 3.3.0-20), it’s very possible that the error will be gone or a better error message will show up.
Thanks @jonasraoni for the very quick reply!
I’m gonna upgrade the OJS instance soon and try again depositing the issues that gave xml-errors.
One more problem with PKP PN Plugin (that you probably are already aware of) is that the Italian version (don’t know abot other non english languages) of the scheduledTask log file don’t writes error codes but the variables that those codes should contain.
Apparently, localization file are not well formed.
And one last question:
after upgrading to OJS 3.3.0-20, do I need to manually re-submit issues with xml-errors or does it work automatically?
Great! The upgrade should be fast, there are no breaking changes if you follow the steps properly (or download the ready package).
One more problem with PKP PN Plugin (that you probably are already aware of) is that the Italian version (…)
Regarding the translations, only the 3.4 version and its related plugins are being updated properly (due to technical debt, it’s not so easy to migrate the translations to older versions). But for this plugin it’s pretty easy, so I’ll synchronize and release a new version of it.
(…) do I need to manually re-submit issues with xml-errors or does it work automatically?
Thank you so much for your work, @jonasraoni.
If I download and install the stable-3_3_0 branch from GitHub (GitHub - pkp/pln at stable-3_3_0)
does it include the updated localization?
Does it contains other fix or features against the latest released version?
Hello @jonasraoni
I had a look to the locale folder here pln/locale at stable-3_3_0 · pkp/pln · GitHub
It seams that the Italian localization files (it_IT folder) haven’t been updated.
Unfortunately, Italian is the main language of my OJS installation.
If you give my some hints on what needs to be updated I can try do it myself and share my work.
Thanks in advance
Hi @jonasraoni , I had a look to the locale.po file in it_IT and it was quite easy to understand what was wrong in there. There were broken variable in the translated strings.
Here is an example of badly localized string:
msgid "plugins.generic.pln.depositor.transferringdeposits.processing"
msgstr ""
"Tentativo di trasferimento del deposito {$ depositId} ({$ objectType}: {$ "
"objectId}) (stato locale: [{$ statusLocal}], stato di elaborazione: [{$ "
"statusProcessing}], stato Lockss: [{$ statusLockss}])"
I fixed the file myself and now I’m waiting to see the next log file which will be generated from the scheduled task tomorrow.
Meanwhile, let me know if upgrading your OJS fixed or helped to understand what’s wrong, I can help to fix any kind of problem related to the Preservation Network.
HI @jonasraoni
I did upgrade to OJS 3.3.0-20 yesterday and checked the new scheduledTaskLogs for the PKPPN Deposit.
I can see better logs, actually.
I see many issues whose state is like this below: [2025-01-29 10:00:34] [Notice] Trying status update for 69 (Issue: 489) (Local Status: [Transferred], Processing Status: [Sent to LOCKSS], Lockss Status: [Received])
and just one issue whose state is this below: [2025-01-29 10:00:34] [Notice] Trying status update for 157 (Issue: 1308) (Local Status: [Transferred], Processing Status: [unknown], Lockss Status: [unknown])
The 1308 seems to be ok, if it was transferred to our service, then you need to wait some time until the PKP PN processes it, it might take days until the status is moved from “In Progress” to “Completed”.
