I’m so impressed with the ongoing work to AnyType. It keeps getting better! I really wish I could come back to using it and so I’m begging, as a strong supporter and early paying member (even though I cannot use it) please please please prioritize fixing the data loss problems, which includes copy/paste and export of properties/relations as well as truncated link names.
These problems present a significant barrier to adoption not just in my own experience but others have mentioned these in the forum and bug reports.
ISSUE/RECOMMENDATION
Relations/properties and their associated data cannot be copied/pasted nor can they be exported to markdown/YAML. This means that data we store in AnyType cannot be preserved or transported outside of AnyType, which realistically results in data loss. Additionally, the truncation of link names from object to object means that we lose data every time those are exported to markdown (or copy/pasted into an e-mail for example). A markdown file that is missing the full title of a linked page is not useful. A markdown file that omits all of the relation/property data I’ve stored is not a reliable or accurate way of preserving and accessing my data down the road.
At the moment, using AnyType implies accepting data loss (I’m ignoring the potential of API work or protobuf possibilities because these are not solutions for the common user that needs straightforward interface functionality built-in).
HOW IT COULD BE DONE
We really need all information fully exported to markdown/YAML from the existing export user interface. The Space export interface currently implies that it will do this but it does not.
USE CASES
In every day use, these issues make it so that I cannot copy text from things I’ve put in AnyType and paste it into other applications such as e-mail, word-processor, web pages, etc.
In the case about ensuring I’m able to preserve my data, it’s 100% critical that I can export all information from AnyType, which necessarily includes relation/property data.
ADDITIONAL CONTEXT
It’s not currently safe to rely on AnyType without this ability. I already experienced one severe problem that led me to decide to stop relying on AnyType because I couldn’t get my data out during my little catastrophe. Solving these data loss problems would make all the difference in the world. Here are some of the bug reports and forum posts that I’ve noted. I’m pasting them here, in a well-meaning effort to try and keep awareness around this issue.
- Copy/paste of content in an object does not include its relations or their values
- Relations are not exported; Need full round-tripping
- How is the state of the markdown exportation? Concern about future-proof
- Export relations data in Markdown as YAML frontmatter
- Read / write YAML front matter when importing / exporting
- Concerns about the current, allegedly severe limitations of the export function?
- Don't truncated title text from objects linked in a page
- Backlink to an object and the title cutoff
- Option to disable link ellipsizing / show full link text
- Inline link title not always fully visible
- CSV / Excel Export
- Bookmarks in markdown export useless (no URL)
- Object does not contain relations when exported as md
Thank you for your consideration.