Ok @rossella.filadoro ,
I tested possible scenarios on an OJS 3.3 test journal, and the problem became more understandable to me.
I now see that issue_id (in the database table) is not taken into any consideration during DOI pattern field for Issues. For example, the issue id 78 is not taken as an automatic number like submission id.
If it was, then you could use it.
Interestingly, chapter_id can be used in OMP 3.4 for chapter DOIs
To my tests, parameters valid only for Issue DOI pattern are Volume (%v), Number (%i) and Year (%Y) located under the Issue Data tab, and all of them have to be entered manually. None of the file id (%f), galley id (%g) or custom identifier (%x) are valid for Issue pattern. When I tried to use one of them, I end up with error stating “The DOI cannot be assigned because it contains an unresolved pattern.”
The checkboxes under the title field only define the text that appears in Journal frontend like Archives or the Last Issue. They don’t affect DOI pattern.
So, since you have left the volume and number fields empty, you are not able use these parameters. If this journal publishes one issue per year, then no problem, and no DOI conflict. But if they want to publish multiple journals per year, it will cause a conflict and will fail.
Well I learned some new things, but useless.
I see that you have already registered DOIs for 2 issues in published in 2025 and your OJS portal consist of multiple journals. Am I right?
Long story short, either you will make some code changes in the core of OJS 3.3, or you will create the Issues for the next 3-4 years now and fill in the Issue fields that you want to use by hand (like me). I am sure, the second one will not take more than 10-15 minutes.
Best regards,