Hi all, @marc after migration we had found also some issues without publish date in our OJS. We detect it because in editor’s back issues page appear as published but the issues also include the publish option and the column publish date was empty.
Getting a issue from database including published issues without publish date we discover that they comes from ojs2 from the same journals. Reviewing this journals this issues were created using ojs using Import native plugin with a custom xml file created based on the defined DTD. Issues created using xml from other installation ojs or using create/publish ojs2 option seem to be ok.
We don’t know the exact publish date for all this issues from diferent journals, so we solved it updating the creation date as 1st of january from the issue year.
I thought that in a decade and 50 magazines I had seen it all and then I remember your 500 journals and I feel there is still much to discover…
If the “sorrow of many” helps as a consolation… during our migration to ojs3 today I have detected a journal that came to us from another university without 840 articles. OJS3 was complaining about the 2400 review_assigments of those missing articles. And well, it doesn’t affect the published articles because they are all rejected ones, but from an historical perspective… just thinking about it is painful.
@asmecher thanks for creating the issue. Today I have the day full, but I promise I will work on this tomorrow.
I have found the NULL values in issue table not in submissions, last_modified date for the journal issue.
Yesterday we have done some updates in this table and now OAI dates are ok.
Ok… forget muy last post.
Bug and workaround confirmed.
Don’t tell anybody but in my head each time you wrote “issue” in my brain it was translated to “submissions”.
I checked my “issues” table and, as you said, some issues don’t have a last_modified date.
When I change it, all works like a charm.
I will look for time to understand how the upgrade script works and make a PR, but till then, if somebody needs to fix it fast, running this query over any ojs3.x will do the job:
UPDATE `issues`
SET `last_modified` = `date_published`
WHERE last_modified IS NULL;
The problem was, that we had NULL values in some date_published fields in table issues as well. Caused to XML imports years ago. So the query didn’t work in a first step. It’s all fixed now. Thanks.