UiTdatabank (BE clients only)

The UiTdatabank updater makes it possible to directly transfer your events from the website to the UiTdatabank and UitinVlaanderen.be

About UiTdatabank

 

 

1. UiTdatabank This is the main section where you can export events manually to the UiTdatabank.



• At the top of the screen a message appears if your connection is not yet configured. Contact our support portal to get your connection configured. When your connection is properly configured, you can start exporting directly. You no longer need to log in to UiTdatabank to start importing.
• You can use the toggle to switch between exporting to the UiTdatabank test environment or live environment. For testing, always use the test environment first. Verify the export was successful at https://test.uitdatabank.be/
• Select “debug” to see an overview of all events that are eligible for export.
• If you want to export only one production, enter the production ID that is displayed in the debug screen for any production in the field “production ID” and select “Export”
• The view comes with a log that informs you which productions were exported successfully and reports possible issues.

2. UiTdatabank keyword  The UiTdatabank keyword is also known as "labels" or "trefwoorden" in UiTdatabank. These keywords are labels you can link to your events. It is possible to add new labels yourself in this module.
1. After you have configured all labels you want to use, you can assign these labels to productions in the Production module of your CMS. The label "ook voor kinderen" is validated by publiq. If you don't have the rights to use this label, the importer shows this in an error message.

3. Uitdatabank theme & type Themes and types are specific characteristics used by UiTdatabank. Each theme and type has its own Cdb cat id that needs to be added in order to be recognized by the UiTdatabank. 

UiTdatabank organisatie

• Organisatie ID* (required) = Your own UiTID as it is known at publiq. This is a long string of about 32 characters, which will be sent from CultureSuite to UiTdatabank with every event. It is connected to your UiTID account. CultureSuite will obtain this ID from publiq, based on the UiTID email address you provide.

• Default location id = The default location ID will be sent with each event as long as no other specific location has been assigned via the location module (see "assigning locations" below). You can find this ID in UiTdatabank.be in the URL behind "/place/" when you select the location page:

• Telefoonnummer kassa = This phone number will be shown next to the "tickets" button on Uitinvlaanderen.be and is a required field.

Assigning labels, types and themes to Events

Assigning Locations

• If all events are in your own location, you can enter your default locationID in the UiTdatabank organisatie module. All events will be exported to this location.

• If you also use other locations, you can add new locations in the Locations module in the Event Metadata menu. Make sure to link your Halls to these locations in the Halls | Settings & Background Image module. Each location has its own LocationID. If the location already exists in UiTdatabank, the ID should be entered in the field "UiTdatabankID" (See point 2. above to find the locationID in UiTdatabank), so all events will be exported using the same, already available location.If the location is not yet present in UiTdatabank, a new location can be created during the update, and the new UiTdatabankID will automatically be added to that location in the CMS during the update process. A new location in UiTdatabank requires a name, street, postal code, city and country. If any of these fields are empty in the location in the CMS, the location will not be created in UiTdatabank and the event export will be skipped.

• Any event that is not connected to a location will be exported to the default location (see point 2. above).

• Any event that is connected to a location without UiTdatabankID or without the required address fields will be skipped.

Other features for UitDatabank

Excluding events from update to UiTdatabank

To exclude an event you can select the "Exclude from export" property in the "Events" module:You can also exclude events in a specific location by leaving the required fields of the location empty and in doing so, preventing the export.

UiTdatabank event ID

Each production, after a successful update, will obtain a unique UiTdatabank ID. This ID is stored within all events of a production in the Peppered dashboard and is used to update all events of the existing production every time a new update is started. Events without this ID have not yet been successfully updated to UiTdatabank.

How to Exclude Events from exporting to UiTdatabank

How to Troubleshoot Events not exporting to UiTdatabank

• No UiTdatabank type has been selected for the Production

• Has the Exclude from export (legacy) option been selected in the Event?

• Title is too long. Title and Subtitle cannot be longer than 90 characters combined

• Use of more than one UiTdatabank type within one Production: you can only have one!

• Missing copyright info image data. Make sure to fill out the credits in Peppered.

• Missing end time and end date. We will automatically use the Start Date if not completed.

• When it seems you are not allowed to set the status "ook voor kinderen", you probably do not have the rights for it. You can check this yourself in publiq.