| OJS | OMP | lib | OPS |
|:----------|:----------------|:-----------------|:--------------|
| Publisher | Publisher/Press |Context (has ROR) |Host |
| Journal | Series |Series (has ISSN) |Server |
| Issue | |SubmissionGroup | |
| Section | |SubmissionGroup |Section |
| | Book TOC themes |SubmissionGroup. | |
| Category | Category |SubmissionGroup. |Category |
| Article | Book/Chapter |Submission (has DOI)| Preprint |

If we want to continue to move towards combining more code with OJS and OMP we need BIG changes.

Handling sections and series as equivalent is a big problem, because a **journal is a series**: both have an ISSN. So at the moment the Context in OJS is a series and in OMP the Context is the publisher.

The Context in both cases should be the Publisher that in many cases has a ROR.

This change affects all the others specifications.

The Series level then changes so that the Journal and the Series are the same thing. And this is true also outside PKP applications, both have an ISSN. This also means that theoretically we could allow an OJS Context to have two series (journals) on the same Context. At the moment in a multijournal installation publishers with more than one journal just create two separate contexts. (*Note that we can arrange things this way only inside the code if we want. OJS can still look the same as before and allow only one journal/series to be created.*)

Issue and Sections are Journal specific things. In the real world Sections and Series are completely different things, we should not try to handle these the same way in code either.

Nate has an excellent idea for SubmissionGroups in Github (https://github.com/pkp/pkp-lib/discussions/7964). This is what Issues and Sections are, submissions grouped in a specific way and shown as a package.

In OMP when you add chapters to a book, there is no way of grouping the chapters under specific categories/themes/subtitles that you see in many book TOCs. Some form of SubmissionGroups would probably solve this. This is not the same thing as Sections, because each book has it's own.

Lastly we have a problem with Articles, Books and Chapters. A chapter in many cases is the same thing as an article, but on code level these are handled separately. We also have a situation where in OMP you can not submit and review a separate Chapter which can be a problem for many publishers.

My suggestion there would be that let's make both Monographs and Chapters Submissions in OMP. We just define the Type of the Submission. In OMP we can then submit separate chapters or the whole book without specific chapters defined. I realize that there are open questions how to handle this, but I would say that it is easier than maintaining a separate Chapters code in OMP in the long run.

Theoretically this would move us to the direction where we could have a Context (Publisher) that has a book series and a journal on the same Context page.

EDIT July 2023: The changes would also allow an OJS Context to create multiple journal titles and ISSNs to reflect the history of changed journal names. https://github.com/pkp/pkp-lib/issues/7527