Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Contacts and Stories are imported into Makerble using csv files.

Types of content

The image below shows a Contact Profile page.

  • the red box shows content that is created by importing a Contact

  • the purple box shows content that is created by importing a Story with a tagged contact (where in this case, the tagged contact is Abigail Holmes - which is why the stories appear on her Timeline)

CSV file formatting requirements

  • Remove any paragraph breaks from the cells in the spreadsheet

  • Remove all empty columns from the spreadsheet. (It is fine for a column to have a header - i.e. title but to not have any information below that; but there cannot be any columns that are completely empty)

  • Remove all empty rows from the spreadsheet

  • Check that the spreadsheet contains no more than 800 rows - if it does, create multiple spreadsheets as they will be imported separately

Instructions for preparing CSV files to import Contacts

  • Each person you work with will exist in Makerble as a Contact. The format of the CSV is as follows:

  • Rows: Each person you work with should exist as one row in the spreadsheet. 

  • Columns: The columns in the spreadsheet will be matched to the fields on Makerble. Therefore, you must ensure that the column titles of your spreadsheet are identical to the names of the fields described in your Blueprints in the Fields per Form tab.

  • Unique Identifier Column: The Unique Identifier code for each Contact is important as it enables us to easily attach survey responses and attendance data to that person when we are importing stories. We recommend that you use a Unique Identifier for each contact.

  • Contacts can into a specific project or into the organisation as a whole. 

    • If you have contacts that are part of multiple projects, they should be imported contacts into the organisation as a whole and then you can subsequently assign them to their corresponding projects using the Bulk Assign page: Bulk assign contacts to a project   

    • If each of your contacts only appear in a single project, you can import them directly into that project

If you are importing contacts into the organisation:

  • supply a spreadsheet with a list of the contacts

  • Contacts are imported in batches of 800 at a time so if you have more than 800 contacts, create multiple spreadsheets, with each one holding no more than 800 rows

If you are importing contacts into individual projects:

  • Supply a set of spreadsheets; one for each project however note that if any contacts appear in multiple projects, duplicate contacts will be created for them which you will need to merge once they are imported.

  • Each spreadsheet should contain a list of the contacts.

  • Contacts are imported in batches of 800 at a time so if you have more than 800 contacts, create multiple spreadsheets, with each one holding no more than 800 rows. 

Instructions for preparing CSV files to import Stories

Stories which are Case notes and session attendance

When it comes to importing Session Attendance, create one csv file per project. There should be columns as follows:

  • Unique Identifier Code for the Contact who attended the session

  • Date attended: this is date of the session

  • A column called "Attendee" in which there is a value of "1" in that row

  • If your team records progress at the end of a session using a Scale, you can have a column for each of those scales. In the example csv file there are examples of scales for Behaviour and Confidence

  • Additional Notes: If you capture additional notes at the end of a session about how it went, you can have a column for that

  • Logged by User: Include the email address of the user that this particular story should be attributed to, i.e. the member of staff that logged this originally.

    • This is so that the story can be attributed to them on your Makerble platform.

    • This column is not mandatory, if you leave it blank, the stories will be attributed to the admin user within your account. 

Stories which are Survey Responses

When it comes to importing Survey Responses, create one csv file per type of survey per project. This is because the survey response stories will be imported into a single project at a time and linked to a specific Survey. (i.e. there should be one CSV file per Survey Campaign)

There should be columns as follows:

  • Contact's Unique Identifier Code: this is the unique identifying code that relates to each person you work with. 

  • Date survey was completed

  • A column for each question in the survey

Therefore if someone completed the same survey twice, e.g. at the start of a programme and then at the end, there will be two rows for that contact in the CSV file. The Date survey was completed column will differentiate the responses.

Sample files

Here are the download links to the sample csv files:

Next steps

  • No labels