Q: How to recognise Obsidian's internal link format - [[Wikilink]]

[sklages]

I actually stumbled across TrilliumNext by chance and have to say that I really, really like the software (as a long-term Obsidian user).

Now I have imported my complete Obsidian Markdown tree for testing (and to explore the possibilities that TrilliumNext offers).

I have a lot of notes that contain [[wikilinks]], a la ![[Pasted image 20250324091524.png]], where Pasted image 20250324091524.png is located in a separate folder Attachments.

Any idea how to get TrilliumNext to recognise these links and display the images in my note/text?

Any other hints to take into account when switching fron Obsidian to TrilliumNext.

best regards,
Sven

[eliandoran]

@sklages , would it be possible for you to provide a subset of your notes that don't have any personally identifiabile information? That way I can look into importing from Obsidian.

We don't have support for wikilinks in the Markdown import since it's a non-standard format.

[sklages]

@eliandoran - I could replace all wikilinks in my Markdown documents with "correct" Markdown URLs, [TEXT](URL).

I have:

Notebook/
         Attachments/
                     1234.jpg


         Device/
                T800/
                     dev_desc

In note dev_desc I put [Model 1234]("/Attachment/1234.jpg"). Using the "note path", [Model 1234](#root/KoYzTcYomd5O/oKTTDVct5Hzh/ajOuLM60C4B7).

Both did not work.

I read the FAQ, and as my mobile device is Macbook/MacOS, I am a bit concerned. I see some glitches, e.g. some occasional freezes for some seconds, some lagging, TOCs on the right side without function when clicking on of the entries (these should be clickable ) etc ..

Ironically I am working most of my life and most of the time with linux, but my "documentation+communication device" is currently MacOS ..

[eliandoran]

In note dev_desc I put Model 1234.

The path needs to be relative, not absolute. Relative to dev_devs, it would be ../../Attachments/1234.jpg. I don't think you need the " character, it might actually cause issues.

Using the "note path", Model 1234.

Not sure, how did you obtain the note path at import time?

I read the FAQ, and as my mobile device is Macbook/MacOS, I am a bit concerned.

That would be zadam's FAQ. On our side we consider macOS a first-class platform and we plan to support it

I see some glitches, e.g. some occasional freezes for some seconds, some lagging

Feel free to report them. Trilium is most efficient when you have many smaller notes, maybe the lag comes from really big notes?

TOCs on the right side without function when clicking on of the entries (these should be clickable ) etc ..

If it's italic text, then most likely the reason is #1555 .

[sklages]

In note dev_desc I put Model 1234.

The path needs to be relative, not absolute. Relative to dev_devs, it would be ../../Attachments/1234.jpg. I don't think you need the " character, it might actually cause issues.

Yes. And whitespace in image name is an issue. Obsidian tends to name pasted image data like "Pasted image 20250324092454.png" .. using relative path and removing whitespace makes import work perfectly.

Using the "note path", Model 1234.

Not sure, how did you obtain the note path at import time?

I didn't. Just used the right mouse button after importing... quite wrong, as I now know

I read the FAQ, and as my mobile device is Macbook/MacOS, I am a bit concerned.

That would be zadam's FAQ. On our side we consider macOS a first-class platform and we plan to support it

.. you are right. I didn't read well, sorry.

I see some glitches, e.g. some occasional freezes for some seconds, some lagging

Feel free to report them. Trilium is most efficient when you have many smaller notes, maybe the lag comes from really big notes?

I will do. @eliandoran - What is your definition of "big"? My notes (single MD document) are between 3000 and 12000 characters in size. Some are larger (up to 25000 characters). Some of them with CSV content (as "code boxes"). As I write also some software docs, some of the notes contain a few images.
For "optimal" performance I'd be interested in what "big" or even "good size" really is :-)

TOCs on the right side without function when clicking on of the entries (these should be clickable ) etc ..

If it's italic text, then most likely the reason is #1555 .

Hmm, after importing again (with the corrected MD links), TOCs are working now. So, no issue anymore.

-- Thanks for your helpful support.

[eliandoran]

I will do. @eliandoran - What is your definition of "big"? My notes (single MD document) are between 3000 and 12000 characters in size. Some are larger (up to 25000 characters). Some of them with CSV content (as "code boxes"). As I write also some software docs, some of the notes contain a few images.
For "optimal" performance I'd be interested in what "big" or even "good size" really is :-)

Big is relative and performance is relative to your device. What I can tell tho, is that really large documents tend to get a bit slower due to the way the table of contents is calculated and highlights.

If you feel there's a performance issue, drop me a sample and I can have a look.

[Nriver]

Try this https://github.com/Nriver/trilium-py?tab=readme-ov-file#import-from-obsidian

[sklages]

Looks interesting (in general), thanks!