Skip to end of metadata
Go to start of metadata

OrgSync (v2 api) has a very simple view of events created within OrgSync. A connector is available to consume these events and synchronize them with a Bedework collection.

There are some issues with the api:

  • OrgSync doesn't support the HEAD operation and gives a 500 error. To get the current etag we do an initial GET and discard the remaining response.
  • There is no timezone information in the events.
  • The uid is an internal - short - eventid. Prefixing makes this more acceptable.

Creating an OrgSync subscription

You probably want the incoming events to all be flagged with a specific category or categories. This can be useful for filtering.It makes it easier to include the calendar collections imported by the sync engine. Before carryign ut the folowing steps ensure these categories are created.

As a super user

  1. Switch to the System tab and select "Manage calendars and folders".
  2. Open up "public" and click the "+" on the cals folder.
  3. Set the name - e.g "OrgSync"
  4. Check off categories for filtering
    1. This may not be necessary as your using a specific alias - however
    2. Click on "show/hide categories used for filtering"
    3. Scroll down and select a previously created category or categories
  5. Check off any categories you want applied on input -
    1. Click on "show/hide categories for auto-tagging on input"
    2. Scroll down and select a previously created category or categories
  6. Mark as a subscription
  7. Set the OrgSync URL in the URl field
  8. Put your site OrgSync key in the password field
  9. Select the OrgSync checkbox and probably the "Process Locations and Contacts" and "Process Categories" checkboxes
  10. Select the public only checkbox if that is desired
  11. Set the location key field name for mapping locations
  12. Set the refresh rate in minutes
  13. Save

Mapping Locations

The update process uses a key field set in locations to map the OrgSync locations. The key field value should be an exact copy of what appears in the OrgSync events.

The actual OrgSync location will be stored in an x-property

  • No labels