This page contains the setup guide and reference information for the Coasis integrations.
Prerequisites
An active Coasis account with a list of events (ensure you have access, especially if you are not the owner)
Setup guide
Step 1: Set up the Coasis integration in Swapcard
Sign in to your Swapcard account.
Navigate to your Event page within the Communities section.
In the left navigation bar, go to Event Builder, then select Integrations.
On the integration selection page, choose Coasis from the list of integrations.
To activate the integration, you will need the next parameters:
Event ID : The Event ID on the Coasis end.
User Name
Password
Install Name
API key (supplied by Coasis)
Select your event for integration - The integration displays all events your account has access to, including upcoming and past events.
Your Coasis event has been successfully linked with your Swapcard event.
You have the flexibility to adjust your integration settings according to the specific data requirements. It's crucial to highlight that the synchronization will only begin when you manually start the integration process and finish the necessary mapping.
Supported sync modes
The Coasis integration supports the following sync modes :
Feature | Supported? |
Yes |
Supported streams
This integration is supporting the following Coasis streams
Coasis documentation is accessible here.
Capturing deleted records
The Coasis integration does NOT capture deletions for records in the getAllPresentations or getAllSessions or
getPerson streams.
When a record is deleted on Coasis, it needs to be MANUALY deleted on Swapcard accordingly.
Object Mappings(Custom)
The Coasis integration provides a list of available custom fields for mapping people, which is generated from getPerson, and also a list of available custom fields for mapping sessions, which is generated from getAllSessions and getAllPresentations.
Stream Dependencies
In the context of integration functionalities, records are automatically linked with their corresponding records within Swapcard. For instance, if People are associated with Sessions on Coasis, the integration will replicate these dependencies within Swapcard.
People → Sessions
The Coasis Events integration automatically establishes a connection between People from Coasis and their corresponding Sessions from Coasis.
This integration utilizes the author.id field from the Person & Id field from the Sessions stream as the primary identifier.
The Id field of Sessions serves as the primary identifier for uniquely linking records. These linked records are stored within the Client Id field on the Sessions record on the Swapcard side.
Streams supporting fields
Presentations as Sessions
Presentation Fields | Label | Type |
ABSTRACT | Abstract | string |
ACTIVITY | Activity | string |
ADDITIONAL_FIELDS | Addition Fields | string |
AUTHORS | Authors | string |
END | End | string |
ID | Id | string |
POSTER_BOARD_NUMBER | Poster Board Number | string |
PRESENTATION_NUMBER | Presentation Number | string |
PRESENTER_KEY | Presenter Key | string |
SESSION_ID | Session Id | string |
START | Start | string |
TITLE | Title | string |
Sessions
Session Fields | Label | Type |
COLOR | Color | string |
DURATION | Duration | string |
END | End | string |
ID | Id | string |
KEY | Key | string |
LAST_UPDATED | Last Updated | string |
LOCATION | Location | string |
NUMBER | Number | string |
ON_DEMAND | On Demand | string |
START | Start | string |
STATUS | Status | string |
TITLE | Title | string |
TYPE | Type | string |
TYPE_KEY | Type Key | string |
AIM | Aim | string |
OBJECTIVE1 | Objective 1 | string |
OBJECTIVE2 | Objective 2 | string |
OBJECTIVE3 | Objective 3 | string |
MOBILE_APP_TAGS | Mobile App Tags | string |
DESCRIPTION | Description | string |
TARGET_AUDIENCE | Target Audience | string |
People
People Fields | Label | Type |
ADDITIONAL_FIELDS | Additional Fields | string |
ADDRESS1 | Address 1 | string |
ADDRESS2 | Address 2 | string |
ADDRESS3 | Address 3 | string |
ADDRESS4 | Address 4 | string |
BIOGRAPHY | Biography | string |
CAREER_STAGE | Career Stage | string |
CITY | City | string |
COUNTRY_ISO_2 | Country ISO 2 | string |
CREATED | CREATED | string |
DEGREE | DEGREE | string |
DEPARTMENT | DEPARTMENT | string |
EMAIL_ADDRESS | Email Address | string |
FAX | Fax | string |
FIRST_NAME | First Name | string |
GENDER | Gender | string |
GENERATION | Generation | string |
INSTITUTION | Institution | string |
INSTITUTION2 | Institution 2 | string |
KEY | Key | string |
LAST_NAME | Last Name | string |
LAST_UPDATED | Last Updated | string |
MEMBER_SPECIFICATION | Member Specification | string |
MEMBER_STATUS | Member Status | string |
MEMBER_TYPE | Member Type | string |
MIDDLE_NAME | Middle Name | string |
MIDDLE_NAME2 | Middle Name 2 | string |
MIDDLE_NAME3 | Middle Name 3 | string |
MOBILE | Mobile | string |
PHONE | Phone | string |
SALUTATION | Situation | string |
STATE | State | string |
ZIP | Zip | string |
Limitations & Troubleshooting
Connector limitations
Maintenance
The Coasis API is a private source API, which adds complexity to maintenance and may lead to stability issues. Despite these challenges, Swapcard offers a connector to facilitate seamless integration.
Incremental Sync
Integration with Cadium is subject to limitations imposed by the provider's API when it comes to incremental updates. The synchronization frequency is strictly limited to 1 hours
Changelog
Version | Date | Subject |
0.0.9 | 2023-03-28 | Maintenance |
Enhancement
Please be aware that any enhancements to this integration, which encompass any requirements not covered by the existing integration state, will be subject to custom development processes and associated costs.