I did something similar for the back-end of a quite known hotels reservation site (I can't disclose, so sorry for the lack of images).
A bit of context and explanation: What we discovered when researching is that there were very common behaviors on specific periods of time. Namely: weekends, holidays, seasonal and week of the month. Since back-end users needed to mass apply conditions to these periods of time, instead of using dates, we allowed for bulk modification on these predetermined periods of time. So, an admin user could select "all second weeks on summer" and mass apply data with one click.
Because of the above, I had to find a way to identify periods of time. The one of interest for this question is week.
So what I did is simply name them as
week 3. Immediately after doing this, I found some obvious issues with this approach:
- it would only work if the first day of the month was Sunday, which obviously won't happen the following month
- even considering the above, what happens with orphan days? (in this case, 29th, 30th, 31st)
- If we assign the orphan days to (say)
week 5, what happens with the remaining days of the week?
So what I did is to consider the above issues as follows:
- First week of the month will always start on Sunday
- First week of the month will be the first Sunday with date of that specific month
- If a week from previous month (
5th week) requires days from the following month, then they're added continuing the day progression until the first Sunday of the next month. For example:
Week 5 of month: Wed 28, Thu 29, Fri 30, Sat 1 // Week 1 of following month: Sun 2, Mon 3, Tue 4..... . This usually results on
5th week NOT HAVING 7 DAYS.
Fifth weeks are bound to be incomplete weeks
This way, we could define some virtual time periods (or virtual blocks) that users can quickly modify with a few clicks, even within years.
Additionally, there is the issue of reservations spanning thru different virtual blocks, but I won't expand since it won't help you at all.
With the above in mind, we created a timeline interface. Again, since I can't show what we did, think of something like the example below:
The difference with this example is that users could filter views, displaying different levels of granularity (like any calendar: year, months, days) or using virtual blocks (weeks as mentioned, but there were others).
Then I had to solve what matters to you: labeling. Due to the problems mentioned above, this was of paramount importance. What I chose to do was to name the block as
week [n], then starting and finishing date. For example:
**Week 2:** Jul 23 - Jul 29
Please note that I didn't use numbers to call months, but the month abbreviation (which dynamically changes based on language settings).
And that would be the answer to your question and the reasoning behind it!
Please note this:
- Instead of using first Sunday of the month, you can use a First day of the month approach, and it will work the same
- I applied this to a timeline interface (as shown), a calendar view and
checkbox based filters. I assume you'll need to have extra considerations if you want to use
- All the above being said, think twice on WHY apply something like this. If your scenario doesn't consider weeks as virtual blocks, then you might be OK with just a