Closed jmrauen closed 6 months ago
@lishid hoping for your input on this, maybe I can just update the importer to nest the assets for each markdown file in a folder in Bear/assets
?
Sorry for the late reply!
Hmmm based on what I've seen from the other importers, we should probably deduplicate the files by using the internal obsidian function that finds a filename that is available (it adds a number at the end). Trouble is, we'll need to go back and update the links to those files.
Seeing this same issue. I know have hundreds of notes linking to the wrong images. What's the function that finds a unique available name?
The importer anyways modifies the asset path in the markdown. Some kind of unique identifier (like a hash of the note's file name) referring to the note could be added here.
I noticed a lot of my images where the same one. Frequently this was the first import with a file named ”image.png” which Bear seems to use a lot.
If you export Bear to markdown (instead of using the backup format) you get a lot of these:
I think it's pretty serious that an official importer plugin as such profound data loss. The main reason I discovered is because I'm pretty paranoid about the reliability of Obsidian from previous experiences so I doubled checked, but I reckon less technically inclined people might just follow official Obsidian documentation and get severely burned.
Still happening today. Why was this closed?
In bear each textbundle has an own folder for images. But in the import each file will be put in the same assets-folder. So when I have more notes with an image e.g. "untitled.jpg", only one image of them will appear in each note!
Please rename an existing filename e.g. untitled123.jpg and not skip the import. Thanks:)