Hi Kevin Boyle I created a ticket with Telligent asking if we could have it added or if there was a reason it is not an option.  We'll see what their response is.

Hi Kevin Boyle  I thought I posted their response asking for some more information but I think I may have closed my browser or my computer rebooted, etc., etc., etc.  Anyway, sorry I didn't get back to this sooner but this is their response:

Hi Chris,

I'm not familiar with this date standard. Would it be possible to list the advantages of using this over what is already available on the community side please. I appreciate and ISO industry standard representation of date/time would be one of them but I would be interested in the idiosyncrasies of what the other benefits would be. Any use cases being community specific would be helpful. Based on that I'm sure I can raise a feature request to include in a future version.

Kevin, if you can answer that I will let them know and see what they say.

Thanks!

cseamons said:

Kevin, if you can answer that I will let them know and see what they say.

Hi Chris,

Look at the first sentence in my OP for that answer.

I can't believe that whoever it is who replied has never heard that ISO standard.

There may be (are) many different regional standards. There is only one international standard. That was the standard the Community adopted. I'm not aware that anyone made a conscious decision to change. That option just disappeared with the transition to Telligent! 

Thanks Kevin Boyle I have noted your response from the OP in the ticket.  From his initial reply it sounds like it would be a feature request for a future version.  :-\

cseamons,

Any update on the ticket you opened?

Hi Kevin Boyle  They closed the ticket 9 months ago so as far as they are concerned there is no update.  This is what they indicated before closing the case, (which I was OK with since there was nothing to keep the ticket open for):

"Ok thanks for the feedback I'll raise a feature request for this. Feature requests, if accepted, can take some time to be implemented into a future version."

Do you want me to open another ticket and ask if a feature request has been put in place?

Kevin Boyle said:

The ISO 8601 date format was the default date format for the Community on the Khoros platform. It is the international standard and mandates that the month and day be specified using two digits.

Certainly there are a lot of more important items with which we need to be concerned so, at this point, it's not worth wasting time pursuing this. I'll leave it to you if you want to follow up. I was curious what had become of this. Now I'm curious if they actually did raise a feature request or if that was their way of telling you to stop bothering them.

Kevin, would today's date be shown as '2022-02-25' (yyyy-mm-dd) in this format?  Currently there is a date format that is close, 2022-2-25, the one noted with the red dot above in the image.

Would that be sufficient to use for now or should I leave it?

cseamons said:

Kevin, would today's date be shown as '2022-02-25' (yyyy-mm-dd) in this format? 

Yes.

cseamons said:

Currently there is a date format that is close, 2022-2-25, the one noted with the red dot above in the image.

Would that be sufficient to use for now or should I leave it?

That is what I use but dates don't align when viewing a list of them. Also, if you look at the standard there are ways to enter partial dates.

The Khoros platform allowed a specific date format to be used throughout the whole community but, really, you should see if Micro Focus has standardised on a specific date format. There isn't much point having the community standardise on one format then learning that Micro Focus already has a corporate standard that is different.

Using the example that you reference, when I see a date shown as 6-1-2003 or 6/1/2003 there is no way to know if it is D/M/Y or M/D/Y. We have to remember that Micro Focus is an international enterprise and that there are various date formats used in different geographic locations. The objective is to ensure there is no confusion when specifying a date. The ISO standard accomplishes that.

That was my intent when I made the suggestion.

Hi Kevin.  I did a little digging and it appears we do not really have (or adhere to) a corporate standard although in our brand guide it says to use this format in most cases:

Month DD YYYY

So I guess that basically leaves us where we are but I agree that the ISO standard would be best and not sure with Telligent doesn't use it as they are an international company.