| Table of Contents |
|---|
Both Users and Events can be created and edited in bulk through CSV upload. To create and edit events choose a data type of events from the new import screen.
...
The import behaviour selection determines the action you wish to perform when uploading the populated CSV.
...
Behaviour | Description |
|---|---|
Search for existing data, create new records which do not exist, do not update existing data | risr/advance will use the data in the uploaded CSV to attempt to search for events which may already exist. If existing data is found these events will NOT be updated. Any rows which do not match existing data WILL be created as new events. |
Search for existing data, create new records which do not exist, update existing data | risr/advance will use the data in the uploaded CSV to attempt to search for events which may already exist. If existing data is found these events WILL be updated with the information within the uploaded CSV. Any rows which do not match existing data WILL be created as new events. |
Search for existing data, do not create new records, update existing data | risr/advance will use the data in the uploaded CSV to attempt to search for events which may already exist. If existing data is found these events WILL be updated with the information within the uploaded CSV. Any rows which do not match existing data will NOT be created. |
Create all records in the file, do not check for existing data | All rows in the uploaded CSV will be created as new events. |
After selecting the type of event you wish to create, and the chosen import behaviour it is then possible to upload the source CSV file.
| Note |
|---|
Only CSV file types files with a maximum size of 10Mb can be uploaded. Please ensure your file is converted to this format in order to upload. |
...
Once the CSV is successfully uploaded the page will update to allow you to choose to which event fields the CSV data should map.
...
| Note |
|---|
The format required for uploading dates is YYYY-MM-DD |
Events containing files
When the event type chosen for import contains a file field it is possible to attach files to the events through the CSV import process. If a file field is detected within the selected event type there is an additional zip file upload area.
...
This zip file should contain all of the files which you wish to attach to the events that are specified in the source CSV. The filenames of each file should be specified in a column within the source CSV.
| Expand | ||
|---|---|---|
| ||
Desired outcome Process  Ensure the source CSV contains a column which references the filename of the file you wish to attach to each event.  |
| Note |
|---|
A single zip file should be uploaded which contains all of the files you wish to attach to the events. Only zip files with a maximum size of 100Mb can be uploaded. |
Email notifications
Email notifications can be enabled or disabled for the chosen import. Please note this setting only applies when creating single-section events, and dictates whether the timeline owner receives the event completed email notification. All subsequent email notifications will be triggered in the normal manner through the workflow where appropriate and cannot be controlled .
...
Choose import to run this task for real and mock run to perform a test of the import behaviour.
...