extending the calendar: predefined lists of wider regions, nations, dioceses

[JohnRDOrazio]

My vision for the "extending the calendar" section of the frontend is a breadcrumb approach, starting from the more general areas down to the more specific areas:

Instead of having three separate menu items, we should always start from the Wider Region, and show a predefined list of all Wider Regions that have patron saints. In this list, we should see immediately which ones have already been created and which ones haven't (like green and red highlights). Clicking on an already created wider region will load the data, clicking on one that hasn't yet been defined will allow you to create it.

Upon creating a wider region, you can choose which nations belong to the wider region; upon selecting an already created wider region, you will have a list of nations that belong to it. From the list of nations, you should see which ones have been defined and which ones haven't.

Again, selecting an already defined nation will load it's calendar data; selecting one that hasn't yet been defined will allow to create it.

When an already created national calendar has been loaded, or a new national calendar has been created, we should see a list of dioceses that belong to that nation. And the process continues: select an already created diocesan calendar to load it, select one that hasn't yet been created in order to define it's data and create it.

Is this feasible? Are there patron saints that apply to continents? Should we start with a list of continents? Should there be multiple layers for the "wider regions"? For example, are there patron saints for wider regions that are not continents, but still comprise a number of nations?

A good start to help rationalize all this would be knowing which Romans Missals have been printed / approved, we would need a complete list. And knowing which "wider region" patron saints have been declared over the years, and map out which "wider regions" they apply to. Having this data will allow us to create the most rational frontend approach.

[JohnRDOrazio]

Let's assume that there is a case where there is a patron saint for a "wider region" that is not a continent: say for example there is a patron saint for neighbouring dioceses. I would say, don't create another middle layer, but just define the patron saint in each of the diocesan calendars: they will probably all share the same language or languages anyways. The only advantage to having the "wider region" layer is to make it easier to translate the data in a consistent manner from the weblate interface, and apply it accordingly to the subareas.

For example, a patron saint of a "wider region" that is a continent, will need to be translated into the different languages spoken within that continent. Having the data loaded into weblate to assist translation, will assist also in consistency in the presentation of the data for all the local areas that use that data.

Whereas diocesan calendars will probably never need to be translated anyways. They will simply inherit data from the wider region (continent), and then apply any extra data for that diocese.

So I'm thinking we will probably be only dealing with continents as wider regions. But again, we will be able to better handle this when we have enough data to work with.

[JohnRDOrazio]

In the meantime, we have obtained a list of all dioceses of Latin rite in the world, thanks to data from Gabriel Chow.