Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

year-quarter time format #562

Closed
akariv opened this issue Jan 10, 2018 · 2 comments
Closed

year-quarter time format #562

akariv opened this issue Jan 10, 2018 · 2 comments

Comments

@akariv
Copy link
Member

akariv commented Jan 10, 2018

Add a new datatype for denoting yearly quarters (which apparently is quite a common thing).

Proposed name: yearquarter (following the existing yearmonth)

Formatting:

  • default format yyyy-Qq, e.g.: 2015-Q1, 2013-Q4
  • format parameter:
    Same as in date, with these extensions:
    - %q should be used to indicate a numeric quarter number (between 1 and 4)
    - %Q should be used to indicate a quarter number in Roman numerals (case insensitive, between I and IV)

cc: @zelima

@Stephen-Gates
Copy link
Contributor

Should be clear in spec that Q1 = 1 Jan to 31 Mar, etc.

@rufuspollock
Copy link
Contributor

I thought about this when I introduced yearmonth and year #105 - how often do quarters show up and do they need their own type? This is a classic "feature" vs "complexity" trade-off and i'd like more data before we made a decision.

Re @Stephen-Gates we should at least be clear how people can translate / interpret this stuff now.

@roll roll added this to the v2 milestone Jan 3, 2024
@roll roll removed this from the v2 milestone Jan 3, 2024
@frictionlessdata frictionlessdata locked and limited conversation to collaborators Oct 21, 2024
@roll roll converted this issue into discussion #1001 Oct 21, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
Status: Done
Development

No branches or pull requests

4 participants