WHAT DO YOU RECOMMEND
When we import a CSV,
- ask if we want to put them in a existing collection
- ask if we want to create object as a existing type
- in this case, if this type already has a property with the same name of the columns from CSV : use this relation!
REAL WORLD USE CASES
CSV import is still very basic, and at the moment it’s best not to use it at all.
(I tried…)
Case study: I’m importing a database of bottles, with specific data (name, origin, characteristics, etc.).
The aim is to have an equivalent collection in Anytype.
If I import my CSV :
- it will create page objects: rarely the right choice for CSV!
- the relationships will all be textual and, as you can’t change the type, you’ll have to throw them out.
Conclusion: delete everything.
Now, if I create a “bottle” type in Anytype, with relations that have the same name, when I import the CSV I’ll have to tell Anytype to save the lines as “bottles”.
Ideally, I’d even like to be able to map the columns of my CSV to Anytype relations, but that’s more complex.
RECOMMENDED ALTERNATIVES
Propose to map CSV columns to AT relation
Or let the user change the type of relation