2023: Week 48 - Reporting Week Calendars

Challenge by: Jenny Martin

It's always been interesting to me how reporting dates can be so different for different industries. There is often a table that is centrally maintained explaining how the reporting date translates to the calendar date. This way any dataset can be easily enriched with the reporting dates. 

This challenge will be all about creating a dynamically updating reporting date table.

Imagine a company uses the following logic:
  • Their reporting year begins on the Monday before 1st February
    • e.g. In 2023, 1st February fell on a Wednesday. Therefore the first day of the reporting year will be 30th January
  • Each Reporting Month contains exactly 4 Reporting Weeks
This is the logic we will use for this challenge, but you can imagine how it could be easily updated to fit another organisation's logic.

Input

The input this week is very simple. We'll update this value so the user can choose a calendar year to generate the reporting dates for.

Requirements

These will be scarce this week as there will be many ways of tackling this challenge and we're excited to see the creative ways the community comes up with! 
  • Input the data
  • Create a way for the user to choose which calendar year they want to get the reporting dates for
  • Make sure to have a row for each date in the selected year
  • Create a field for the Reporting Year (based off the above logic)
  • Create a field for the Reporting Day
    • Day 1 will be the Monday before the 1st Feb
  • Create a field for the Reporting Week
  • Create a field for the Reporting Month
    • Each month contains exactly 4 weeks
  • Output the data, naming the file according to calendar year selected when the workflow runs

Output

  • 5 fields
    • Calendar Date
    • Reporting Year
    • Reporting Month
    • Reporting Week
    • Reporting Day
  • 365 Rows (366 including headers)
You can download the output from here.

After you finish the challenge make sure to fill in the participation tracker, then share your solution on Twitter using #PreppinData and tagging @Datajedininja, @JennyMartinDS14 & @TomProwse1

You can also post your solution on the Tableau Forum where we have a Preppin' Data community page. Post your solutions and ask questions if you need any help! 

Popular posts from this blog

2023: Week 1 The Data Source Bank

Image
 Created by: Carl Allchin Welcome to a New Year of Preppin' Data. These are weekly exercises to help you learn and develop data preparation skills. We publish the challenges on a Wednesday and share a solution the following Tuesday. You can take the challenges whenever you want and we love to see your solutions. With data preparation, there is never just one way to complete the tasks so sharing your solutions will help others learn too. Share on Twitter, LinkedIn, the Tableau Forums or wherever you want to too. Tag Jenny Martin, Tom Prowse or myself or just use the #PreppinData to share your solutions.  The challenges are designed for learning Tableau Prep but we have a broad community who complete the challenges in R, Python, SQL, DBT, EasyMorph and many other tools. We love seeing people learn new tools so feel free to use whatever tools you want to complete the challenges.  A New Year means we start afresh so January's challenges will be focused on beginners. We will use dif
Read more

2023: Week 2 - International Bank Account Numbers

Image
Challenge By: Jenny Martin For week 2 of our beginner month, Data Source Bank has a requirement to construct International Bank Account Numbers (IBANs), even for Transactions taking place in the UK. We have all the information in separate fields, we just need to put it altogether in the following order: Inputs A list of the transactions, with information about the receiving bank account  A lookup table for the SWIFT Bank Codes  Requirements Input the data In the Transactions table, there is a Sort Code field which contains dashes. We need to remove these so just have a 6 digit string ( hint ) Use the SWIFT Bank Code lookup table to bring in additional information about the SWIFT code and Check Digits of the receiving bank account ( hint ) Add a field for the Country Code ( hint ) Hint: all these transactions take place in the UK so the Country Code should be GB Create the IBAN as above ( hint ) Hint: watch out for trying to combine sting fields with numeric fields - check data types Re
Read more

How to...Handle Free Text

Image
Free isn't always a good thing. In data, Free text is the example to state when proving that statements correct. However, lots of benefit can be gained from understanding data that has been entered in Free Text fields. What do we mean by Free Text? Free Text is the string based data that comes from allowing people to type answers in to systems and forms. The resulting data is normally stored within one column, with one answer per cell. As Free Text means the answer could be anything, this is what you get - absolutely anything. From expletives to slang, the words you will find in the data may be a challenge to interpret but the text is the closest way to collect the voice of your customer / employee. The Free Text field is likely to contain long, rambling sentences that can simply be analysed. If you count these fields, you are likely to have one of each entry each. Therefore, simply counting the entries will not provide anything meaningful to your analysis. The value is in
Read more