In an application, I need to present a calendar / calendar, which is composed of events and locations. I'm using the concept of repositories, where I store all queries to a given entity. In this case, events and locations have their respective repositories.
My question is: when I need to set up my calendar in this application, what would be the distribution of responsibilities for the presentation of this calendar / calendar?
Currently, the scheduler controller communicates with the event and location repositories, formats the data and provides the view. According to the mvc standard this is wrong.
Would it be a good practice to create a calendar repository and there communicate with event and location repositories so I can set up my data and provide pro controller?