Ok… this one is going to be tricky, but I’ve been at it for a while and can’t figure out how to solve it.
Description of issue or problem I’m having:
One of the magazines in my service has followed the following migration path:
2.4.8-5 > 3.1.2-4 > 3.2.1-4
(We didn’t make the direct jump to 3.2 because we didn’t want to expose the attached documents)
The problem is that we didn’t realize that the review comments were not migrated (not shown) and now it’s been in production for 2 months, so I can’t go back to the backup copy. 
I wonder if this is a known issue or am I the first one to run into this.
Assuming that the problem is that the comment rows (not sure where and how is this info stored in OJS) have not been migrated, the only thing I can think of is:
- With the backup from 2 months ago, do a new direct migration to 3.2 (which does keep the comments).
- Extract from the migrated DB those comments.
- Inject in the production DB the missing comments.
Can anyone think of something easier than this?
Application Version - e.g., OJS 3.2.1-4