Type in your suggestion - new feature or improvement idea

More date format options in account organization details

6 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)

We’ll send you updates on this idea

AdminTeam Support (Customer support, Wild Apricot by Personify) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
  • klm commented  ·   ·  Flag as inappropriate

    I would really appreciate being able to show the day of the week being an option.

  • Randall Rensch commented  ·   ·  Flag as inappropriate

    My suggested list included "3/12/10 (shortest US order; the traditional UK order is already an option)"

    The US order, too, is already on the list. This version just omits leading zeros.

    Additional wish: Enable Wishlist contributors to edit their posts, at least for, say, half an hour after posting. (That is the policy of some CMS systems.)

  • Randall Rensch commented  ·   ·  Flag as inappropriate

    Although I see this has received only 2 votes in a year, it is a significant need (see examples below). I suppose the low vote count is because most WA admins are not familiar with setting the date format, as it's usually done only once, when the account is opened.

    To illustrate, the current options are limited to:
    03 Dec 2010
    Friday, December 03, 2010
    Fri, December 03, 2010
    December 03, 2010
    03 December 2010
    3 Dec 2010

    Maybe this list seemed long and varied enough to satisfy a Russian programmer in 2010, and the needs of actual users since then are a forgotten issue?

    My main concerns are brevity and including the day of week.

    An example of Why this need is critical: Our meetings are usually on Wednesday. Next week's meeting will be on Monday. On our calendar and in our email, our admin naively used only the macro for the date. And of course NOBODY noticed that the date is a Monday.

    And in general, it is important, because people can instantly relate to and remember "the event is Thursday" whereas "the event is March 14" they would have to look up.

    Suggested additions to this list:

    Fri Dec 3, 2010 (short and clear to all nationalities)
    Fri Dec 3 2010 (shorter still; my choice for international readers)
    3/12/10 (shortest US order; the traditional UK order is already an option)
    Fri 3/12/10 (shortest with day of week)
    Fri 12/3/10 (for the UK etc.)
    Dec 3 2010 (after all, you have 3 Dec 2010)
    Dec 3 2010 (Fri) (for good measure, but my preference is to put day first)
    All current options but without leading zero(s). (Leading zeros (I've learned by Googling) are a standard mainly in post-Soviet states. Needlessly formal and lengthy elsewhere outside of programming circles.)

    And one more option, although I'm not sure I would make it sitewide. In ordinary emails and calendar descriptions, it is seldom necessary to include the year. To humans, if I say an event is next Friday, Dec 3, I don't have to say 2010. Maybe there could be an option to omit the year if the date is within, say, the next three months? But that would require significant system programming, testing, etc.

    And including ordinal versions (Dec 3rd, 2010) and clarification of 12 pm as being midnight or noon would be a step too far.

    But adding these other clearer, shorter options seems a no-brainer.

  • Randall Rensch commented  ·   ·  Flag as inappropriate

    It's good that you provide many alternatives for default date formatting, but you left out one of the most valuable: Full information in shortest form, namely:

    Fri Dec 3, 2010

    Would you please add it? Also note that I have omitted the leading zero. Including the day is very helpful to making the date memorable ("Oh, next Friday"), but "Fri, December 03, 2010" is attractive only to a computer.

    I would even go so far as suggest that 99% of the time, we don't need to show the year, either, but I don't know how you would make that optional in a default, and I haven't surveyed all our situations where it occurs.

Feedback and Knowledge Base