How Do I Import My Existing Collection?
Quotemarks supports importing comma-separated value (CSV) files. Many applications use CSV because it is simple and human-readable. This simplicity is deceiving as there are different variations of CSV which can make working with them more challenging. Fortunately, Quotemarks has a mechanism to help manage these differences.
Quotemarks provides two methods for importing CSV. This article is covers the second method.
The first is its native, "lossless" method: A specialized Tabular Data Package that allows for data restore without loss of metadata (such as when a quotation was added to your collection). Although you may modify your CSV file to match the format it expects, this option is ideal for when you want to restore data from a past Quotemarks backup which is already in this format.
The second method is simplest for importing CSV originating from another application such as the legacy app Quotebook. In comparison to the first lossless method, this method is potentially "lossy" as only select columns are supported for importing.
Importing from CSV
By default, Quotemark supports CSV formatted the way Quotebook exports. If you modified your data, or if it comes from another application like a spreadsheet, you can either match your CSV file to the default, or change the import settings by way of the CSV dialect. There's nofoolproof way to detect this so read through this guide and double check your work during and after import.
When importing CSV Quotemarks expects at least one column. At the very least there needs to be quote text. This column must be assigned, and additional supported columns may be assigned. Quotemarks doesn't support all columns that other apps used (such as ratings), and not all columns are presently importable.
|Date Added||Yes||Date format must be
|Source (aka URL)||Yes||Intended to be a URL although in previous versions this was any text that described the origin of a quote|
|Tag(s)||Yes||For multiple tags, value must be formatted as a JSON array, e.g.
CSV Dialect and Encoding Requirements
Quotemark addresses the issue of different applications having different encodings by requiring a CSV dialect declaration. Special care should be taken here. For example, if you have modified the CSV with another application the encoding may have changed. The CSV Dialect specification describes these properties in more detail.
Common problems to look out for are the line terminator (toggle between CRLF and LF), quote character, whether double quotes are employed, and whether the first row is a header instead of an entry.
The default expectation is a UTF-8 file with:
- Line Terminator:
\r\n(CRLF line endings)
- Quote Character:
- Double Quote:
- Escape Character:
- Null Sequence:
- Skip Initial Space:
- Comment Char: Not supported
- Case Sensitive Header: Unused
Help, I'm Still Having Trouble
If you are having problems and need assistance with this please email me using the email provided on the Quotemarks website.