Difference between revisions of "Retain GroupWise"
| Line 1: | Line 1: | ||
| + | ==GroupWise Item Date Handling== | ||
| + | This information was received from a Novell GroupWise agent developer: | ||
| + | Internally the field for startDate is BEGIN_SECS. All items have a BEGIN_SECS field. In Cornell, we will expose that field on all items as <begins>. | ||
| + | |||
| + | There are three fields dealing with when the item was created / delivered: | ||
| + | * created | ||
| + | * delivered | ||
| + | * begins | ||
| + | |||
| + | On non calendar items, created and begins should be the same value (they might be off by a few seconds). Created and delivered have a bigger chance of being off by a few seconds. | ||
| + | |||
| + | Some items don't have a internal stored value for delivered. In that case we will return first BEGIN_SECS as delivered otherwise we will use created. | ||
| + | |||
| + | In the case of delivered, you don't know what value it represents. It would be safer to use created as the alternate of startDate. | ||
Revision as of 13:51, 2 June 2015
GroupWise Item Date Handling
This information was received from a Novell GroupWise agent developer:
Internally the field for startDate is BEGIN_SECS. All items have a BEGIN_SECS field. In Cornell, we will expose that field on all items as <begins>.
There are three fields dealing with when the item was created / delivered:
- created
- delivered
- begins
On non calendar items, created and begins should be the same value (they might be off by a few seconds). Created and delivered have a bigger chance of being off by a few seconds.
Some items don't have a internal stored value for delivered. In that case we will return first BEGIN_SECS as delivered otherwise we will use created.
In the case of delivered, you don't know what value it represents. It would be safer to use created as the alternate of startDate.
