|
|
## How Do I Import My Existing Collection?
|
|
|
Quotemarks supports importing [comma-separated value](https://en.wikipedia.org/wiki/Comma-separated_values) (CSV) files. Many applications use CSV because it is simple and human-readable. However, there are different variations of CSV.
|
|
|
Quotemarks supports importing [comma-separated value](https://en.wikipedia.org/wiki/Comma-separated_values) (CSV) files. Many applications use CSV because it is simple and human-readable. And although there are different variations of CSV which can make working with them more challenging, Quotemarks has a mechanism for working with these differences.
|
|
|
|
|
|
Quotemarks provides two methods for importing CSV. The first is its native method: A [specialized tabular data package](About-the-Backup-Format) that allows for data restore without backups. This is best if you want to restore data from a past Quotemarks backup. (Although you may [modify your CSV data to match its structure](https://gitlab.com/quotemarks/quotemarks-ios/wikis/Manually-Importing-CSV)).
|
|
|
Quotemarks provides two methods for importing CSV. The first is its native method: A [specialized tabular data package](About-the-Backup-Format) that allows for data restore without loss of metadata. Although you may [modify your CSV file to match the format it expects](https://gitlab.com/quotemarks/quotemarks-ios/wikis/Manually-Importing-CSV)), this option is best if you want to restore data from a past Quotemarks backup which is already in this format.
|
|
|
|
|
|
If you have CSV from another application the simplest method may be to import your CSV directly. Quotemarks now supports importing CSV originating from the legacy app Quotebook. If you modified your CSV, or if it comes from another application like a spreadsheet, you can match your CSV file to Quotebook-formatted CSV.
|
|
|
If you have CSV from another application the simplest method may be to import your CSV directly. Quotemarks now supports importing CSV originating from the legacy app Quotebook. Be aware that the amount of information it imports is presently limited to author and quote. If you modified your CSV, or if it comes from another application like a spreadsheet, you can match your CSV file to Quotebook-formatted CSV.
|
|
|
|
|
|
### Importing from Legacy Quotebook-formatted CSV
|
|
|
You'll need to ensure your CSV is aligned in the way that Quotemarks expects. Current, Quotemark supports the CSV formatted the way Quotebook exports. First you'll need to modify your CSV so that it contains, and second you'll need to ensure your CSV file uses a particular dialect.
|
|
|
You'll need to ensure your CSV is aligned in the way that Quotemarks expects. Currently, Quotemark supports the CSV formatted the way Quotebook exports. First you'll need to modify your CSV so that it contains the fields in the expected ordering, and second you'll need to ensure your CSV file uses a particular dialect.
|
|
|
|
|
|
#### Column Ordering
|
|
|
When importing CSV Quotemarks expects at least two columns. The first needs to be the quotation with author to its immediate left. The rest of the fields, like tag, rating, date/time, and source notes are presently ignored.
|
|
|
|
|
|
#### Encoding Requirements
|
|
|
As there are different encoding variations of CSV, Quotemark addresses this by requiring a CSV dialect. If you have modified the CSV with another application your encoding may have changed. To solve this, we expect a certain CSV dialect as explained in the [CSV Dialect specification](https://frictionlessdata.io/specs/csv-dialect/). Our expectation is:
|
|
|
As there are different encoding variations of CSV, Quotemark addresses this by requiring a CSV dialect. If you have modified the CSV with another application your encoding may have changed. To solve this, Quotemarks expect a certain CSV dialect as explained in the [CSV Dialect specification](https://frictionlessdata.io/specs/csv-dialect/). Our expectation is:
|
|
|
|
|
|
* Delimiter: `,`
|
|
|
* Line Terminator: `\r\n`
|
... | ... | @@ -25,5 +25,7 @@ As there are different encoding variations of CSV, Quotemark addresses this by r |
|
|
* Comment Char: Not supported
|
|
|
* Case Sensitive Header: Unused
|
|
|
|
|
|
#### I'm Having Trouble
|
|
|
If converting your CSV to this dialect is challenging, you may alternatively [manually create a data package](https://gitlab.com/quotemarks/quotemarks-ios/wikis/Manually-Importing-CSV) where you may declare the dialect you wish to use.
|
|
|
|
|
|
#### Help, I'm Still Having Trouble
|
|
|
If you are having problems and need assistance with this please email me. |
|
|
\ No newline at end of file |