As noted in a previous post, there are some obstacles to uploading files to the international Itracks accounts when these files are created by Excel. These obstacles can be overcome, by and large, when the researcher ensures that files to be uploaded are first encoded as UTF-8 or UTF-16.
There are challenges with downloading files from international accounts as well, however. Files don't always open in their target applications, and some don't always display accented characters properly. Indeed, some can't even be uploaded back to Itracks.
There are three types of information that can be downloaded from the Itracks software:
- User files
- Transcripts, and
- Discussion guides.
For user files and discussion guides, the options are CSV files or TXT files. For transcripts, the options are CSV, TXT, RTF, and HTM.
I downloaded a sample file for each option and determined that:
- The RTF and HTM formats of the transcript opened correctly in their respective applications (Word and Firefox)
- User files, TXT. Encoded as UTF-16 by Itracks. Correctly opened by both Notepad and Excel, with accents displaying properly. Can be re-uploaded
- User files, CSV. Encoded as ISO 8859. Opened by Excel, but accented characters do not display and are replaced by a question mark. Cannot be uploaded.
- Discussion guide, TXT. Encoded as UTF-16. Correctly opened by both Notepad and Excel, with accents displaying properly. Can be re-uploaded without further convertsion
- Discussion guide, CSV. Encoded as ISO 8859. Opened by Excel, but accented characters do not display and are replaced by a question mark. Cannot be uploaded.
- Transcripts, TXT. Encoded as UTF-16. Correctly opened by both Notepad and Excel, with accents displaying properly.
- Transcripts, CSV. Encoded as UTF-8. Accented characters rendered as a ? by Excel. Conversion to UTF-16 makes it intelligible in Excel with accents displaying properly.
- CSV files are not useful, as currently implemented. They cannot be opened with the accents displaying correctly in their target applications (Excel). Only the transcript CSV file can be made useful by converting it to UTF-16
- All TXT files are encoded as UTF-16 and all were opened by their target application (Notepad) with the accents displaying properly. Further, even Excel can open these text files directly, with accents displaying correctly.
- Researchers should probably be using TXT files in preference to CSV files, at least for downloading.