Introduction

UiTdatabank

1. UiTdatabank This is the main section where you can update events manually to the UiTdatabank. If you want to update your events to the UiTdatabank, click the Login button, Log in to the UiTdatabank with your organisation credentials and then click the button Update in the Dashboard to updste all events. See the chapter Testmodus or "debug" modus  for more information about testing events and updating single events.

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. After you have configured all labels you want to use, you can assign these labels to productions in the production module of your dashboard. 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.  Documentation from publiq about themes Documentation from publiq about types

UiTdatabank organisatie

Organisatie id (required)

Default location id

Telefoonnummer kassa

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 Peppered 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 Peppered, 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

• Logging in The UiTdatabank updater does not require you to login. That will be arranged by a token Peppered obtains from publiq. This token will be connected to your own UiTdatabank account in the administration of publiq. You can update straight away!

• 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.

• Images The first image in a media gallery will be updated to UiTdatabank. Once an image is sent, it will not be updated again. If you want to change the image, delete the image in the UiTdatabank first.

• Copyright of an image Every image needs a mention of the copyright owner to avoid copyright infringements. You can use the "credits" field next to a photo to do so. All event photos without copyright mention will trigger a warning after an update.

• Title of an event The title and subtitle (artist) in Peppered dashboard are combined to form the title in the UiTdatabank.In Peppered:Moments musicaux (Title)Keiko Shichijo (subtitle)In UiTdatabank:Moments musicaux - Keiko Shichijo

• Production types The updater supports Peppered production types "Default", "Movie" and "Long term".Make sure you add the correct UiTdatabank type to each production.

• Prices A default price will be updated (per rank, if the event has multiple ranks) to UiTdatabank.Peppered identifies the default price as any regular price that is at the top of the list in the price type module (you can change the order of price types by drag & drop). Conditional prices (for bundles and discount codes) will not be updated to UiTdatabank.

• UiTpas When your organization participates in UiTpas, the UiTpas prices will be automatically calculated by UiTdatabank. This will be checked based on your OrganisatieID (See "The UiTdatabank menu" above).

• Description fields  The content of your events can be spread over multiple content fields on the website. You can choose which of these fields need to be combined for the content you want to update to UiTdatabank. Choose one or combine multiple fields:
• tagline
• teaser
• description part 1
• website sidenote to description part 1
• description part 2
• programme
• credits

• Option: use external sales URL when filled in This option, when active, will update the "ticket" button on UiTdatabank with the external sales URL that is filled in in the Peppered dashboard for an event. Ticket buttons on UiTdatabank will no longer link to your website, but directly to the website of the external ticket provider. The option is disabled by default, so UiTdatabank events link to events on your own website, even when such an events has an external sales URL on your website.

• Testmodus or "debug" modus The updater also has a "debug" button. When using this button a test update will be prepared in the Peppered dashboard, informing you which events are available to be updated. It will also show you if any data is missing: The "update" link underneath each event enables you to update only that event to UiTdatabank.

How to Export Productions to UiTdatabank

• Green = will export

• Orange = this is a warning, should try to resolve event will sync

• Red = Production will not Sync. Fix what is mentioned in the warning. See list below for common issues.

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.

Technical settings (Peppered will configure for you)

• UiTdatabank API version 3 > APIv3.

• UiTdatabank Consumer key (this key will be provided to Peppered by publiq).

• UiTdatabank V3 host provider base URI (address of the updater).

• UiTdatabank V3 JWT provider base URI (address of the login).

• UiTdatabank V3 long-lived JWT (the token used for login, as provided to Peppered by publiq).