With this post, I would like to raise a fundamental question for discussion concerning the year-based division of series and its application under the Colnect guidelines in the field of Cinderellas.
Unlike official postage stamps, Cinderellas of a given country are typically issued by multiple different institutions. The issuing body therefore represents one of the most important criteria for organization and searchability from a collector’s perspective.
Accordingly, in many Cinderella sections on Colnect, the issuing institutions are either explicitly named in the series title or can be clearly inferred from it. This allows collectors to retrieve all issues of a particular issuer across multiple years using the series filter.
If, in such cases, the series are additionally split by year, this provides no added value in terms of usability: The year is already available as a separate filter criterion, while dividing the series by year actually makes it more difficult—or even impossible—to view all issues of a given issuer in a coherent way. This applies both to series with an explicitly named issuer and to those where the issuer is implicitly but unambiguously defined by the series title (e.g., Christmas Seals in the USA or Tuberculosis Charity Seals in Sweden).
Against this background, I currently see three possible approaches to addressing this issue:
Clarification in the guidelines
Adding a note to the Colnect guidelines stating that, for Cinderellas where the issuer can be identified directly or clearly indirectly from the series title, an additional division of the series by year is not required.
Introduction of a new filterable attribute “issued by”
Implementing a dedicated, systematically filterable issuer field for Cinderellas (programmatically more demanding).
Modification of Colnect catalog codes
Extending catalog codes to include a standardized issuer identifier, allowing all issues of a given issuer to be retrieved via the “catalog code” filter (editorially very labor-intensive).
I personally consider option 1 to be the most practical and conceptually sound solution, but I am deliberately presenting all three options for discussion and would welcome alternative suggestions from the community.



