Journal-Issues with multiple Date-nodes

Some JournalIssues (ie. MATCH (n:JournalIssue{_id:"a6dbdc44b8c56434afb6d9417048a85f"}) RETURN n) have a lot of Date Nodes (in this case 211) Which is bad cause we need the "correct" date for the evaluation

The Problem are JournalIssues that do not have an Issue and/or Volume property, because they will accumulate a lot of Date Nodes

Idea: Create an artificial Issue-property for each distinct year

Question: Should every JournalIssue only have 1 Date-Node?