Aware - Survey Ingestion FAQ

This article provides information on uploading and analyzing open-ended survey data in Aware, including CSV formatting requirements, field definitions, and steps for utilizing the data for custom reporting and insights.

 

Aware's platform enables the ingestion of open-ended response survey data from any provider, facilitating the extraction of meaningful insights through Aware's proprietary enrichments and modeling techniques. Users simply need to adhere to the CSV format specified by Aware for uploading their data. Once uploaded, this dataset can be utilized for Custom Reporting purposes.

 

Survey Ingestion FAQ

 

Aware's platform enables the ingestion of open-ended responses survey data from any provider, facilitating the extraction of meaningful insights through Aware's proprietary enrichments and modeling techniques. Users simply need to adhere to the CSV format specified by Aware for uploading their data. Once uploaded, the dataset can be utilized for Custom Reporting purposes.

 

How do I upload my Survey data into Aware?

  • Within Aware's System Settings or within the Data Upload modules, users will have the ability to upload Survey data via CSV (Ph 1) to their Aware environment.

Where can I interact with my Survey data?

  • Users will be able to run custom (Audience or Topic) Reports on their uploaded Survey to gather insights on this dataset.

How is Survey data normalized in Aware?

  • When a platform is created, it is treated the same way a platform from a collaboration tool is treated. The platform for a survey could be equal to a platform, e.g. Qualtrics or Glint, and each survey as a CSV can be nested under its respective platform.

Editing a Platform Name

  • This can be done on the integrations tab: select your platform and click edit.

Anonymous Surveys

  • For anonymous surveys, Author Type should be anonymous, and Author Name can be left blank.
CSV Column Header ContentObject Property
Author Type AuthorType
Author Name DisplayName
Author Email Email
Survey Name GroupName
Survey ID GroupTag
Survey Question SubgroupName
Response Content
Survey Date Created

 

File Formatting

  • Survey data files must adhere to RFC4180 CSV format, with a few exceptions
    • Header row is required
    • We accept LF or CRLF as record terminators (Unix and Windows line ending semantics)
    • Field quotes for escaping purposes (RFC4180 Section 2.7) must be standard ASCII quotes (hex 22, dec 34)
  • Survey data files must be encoded as UTF-8
    • UTF-8 is an extension of the ASCII encoding. So, technically, ASCII encoded files will work as well. ASCII encoded files are basically UTF-8 files without any extended characters.
  • All fields defined below must be present, any additional fields will be ignored
  • Field names are not case sensitive
  • Max survey size is 64 MB

 

Field Definitions

The following provides a list of fields in a survey response

Field Name Description Type Max Length Format Rules
Author Type

Indicates the type of author for this survey response.

  • "User" - If the response is associated.
  • "Anonymous" - If the response is not associated with an email address.
Enum N/A

User|Anonymous

Not case sensitive

Author Name Name of the response author. If the user type is Anonymous as Author Name. String 255 Must not be blank unless Author type is set to Anonymous
Author Email Email address associated with Author. If the user type is Anonymous then this field is set to Anonymous as Author Email. String 255

Must be a valid format email address consisting of a "user"@"domain"

Must not be blank unless Author Type is set to Anonymous

Survey Name Name of the survey. Recommended to be unique to this survey. This is what the survey will be searched by within Custom Reporting. String 255 Must not be blank
Survey ID Internal ID which must be unique to this survey. String 255 Must be alpha numeric with no extended characters
Survey Date Date which the survey data will be recorded in the system. Survey Date cannot be cannot be in the future. Date N/A

Must adhere to ISO 8601 which contains at least a date specificity:

  • Date (YYYY-MM-DD or YYYYYMMDD)
  • Date with Time
  • Date with time and offset
Questions Text of the question this response is for. String 255 Must not be blank
Response Author's verbatim response text. String 8192 May be blank
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.