Glossary

A-Z glossary of PageSeeder concepts

Date and time

Correctly understanding where the date and time are sourced and applied is important for getting the most out of PageSeeder. The orderly processing of edits or comments is critical to efficient collaboration but it isn't always straightforward with globally distributed group members.

The purpose of this topic is to help developers find more specific information about how PageSeeder processes date and time and provide some direction where the date and time are outside the control of the system.

ISO format

Date and time in the system are represented using ISO 8601 extended format.

More specifically, PageSeeder will only use of the representations below:

FormatExampleAccuracy
DateYYYY-MM-DD2016-04-21Day
Timehh:mm:ss09:21:38Second
DatetimeYYYY-MM-DDThh:mm:ss2016-04-21T09:21:38Second

Timezone

Dates and times will often be followed by a timezone designator in the form ±hh:mm. When the timezone is included, PageSeeder includes both the hour and minute components representing the offset from UTC in the local time of the server.

For example, if the PageSeeder is located in Sydney, the datetime above would be represented as 2016-04-21T09:21:38+10:00.

Exceptions

Possible exceptions are dates created by external applications such as email clients or third party developers, dates in PageSeeder content or information inherited from the host operating system.

End users

Format

Since ISO 8601 is primarily an interchange format, dates and times are not particularly user friendly. PageSeeder will therefore format dates and times for end-users in a more readable format.

For example, 2016-04-21T09:21:38 will be displayed as "21 April 2016 at 9:21:38AM".

Note

The accuracy displayed to end users may differ from the accuracy in the system. Generally, the accuracy decreases for events in the distant past of future.

Local time in user interface

In order to display dates and times which are meaningful to end users, the timezone is adjusted based on the offset from UTC of their local timezone as advertised by the browser. 

In other words, a user located in New York will see dates and times in PageSeeder in the Eastern Daylight Time (EDT) so the date above would then be 2016-04-20T19:21:38-04:00 or "20 April 2016 at 7:21:38PM".

The local offset in minutes is stored in the ps.timezone cookie.

Server time in emails

Since PageSeeder does not keep track of users' location, dates and times in emails are always displayed in the server time.

The server should be set to the timezone of where most end users are located.

Potential issues

When the server date and time are not properly coordinated with external applications, developers may see issues relating to when:

  • comments or tasks are created or updated,
  • document edits have been made or versioned,
  • incidents have been logged.

Because problems like these are a potential source of support issues, it is recommended that some effort be made to create a policy before development starts.

Created on , last edited on