Yarle to construct full tag path from visual hierarchy

[grantx2016]

There are essentially two main ways that tag hierarchies can be implemented in Evernote:

Method A: "Visual"

• level-1-tag
  • level-2-tag
    • level-3-tag

Method B: "Full Tag Path"

level-1-tag level-1-tag/level-2-tag level-1-tag/level-2-tag/level3-tag

Yarle only reproduces a tag hierarchy that works with Obsidian if the tag hierarchy is via Method B. If a Method A hierarchy is given to Yarle it produces the following flat tag structure, which is not desired:

#level-1-tag #level-2-tag #level-3-tag

I believe most users will have a tag hierarchy implemented via Method A so it would save a lot of work if Yarle could construct the full path tag structure as required by Obsidian i.e.

level-1-tag level-1-tag/level-2-tag level-1-tag/level-2-tag/level3-tag

I do not know if this is feasible but it sure would be a huge benefit if Yarle could do this. The alternative is to manually convert the tag hierarchy in Evernote from Method A to Method B which is likely to take a long time.

[akosbalasko]

Hi @grantx2016 !

Could you please share an example enex file in where tags are stored using Method A ? Thanks a lot!

[grantx2016]

Hi @akosbalasko,

You can download my test data at: https://apps.sttrutt.com/files/sharing/LN7kAvUdm. Refer to Test Note 5 which is for testing the tags.

If you are interested, Test Note 00 shows as summary of my migration testing so far, and indicates which tests are currently failing. The specific details of the failure are written up in the associated note. The failures aren't necessarily do to issues with Yarle but rather issues I have to resolve one way or another, so that I can migrate out of Evernote. The more that Yarle can do to assist with those issues, the easier the migration will be, and the less post migration clean up I will have to do (either manually or via scripting). Let me know if you have any questions about those other failures. I will raise separate issues later.

Thanks again for your work on this. Hopefully this feedback will help put a few more knots in the rope you have dropped down to us. 😀

Cheers.

[akosbalasko]

Hi @grantx2016 ! Thank you for these tests, I really appreciate them! I checked the nested tags and I don't see anything in the enex note that looks like a nesting structure of the tags, just simple tags: <tag>level-2</tag><tag>Filterize-done</tag><tag>test data</tag><tag>Yarle-backlog</tag><tag>level-3. So I don't think that Yarle, or any converter is able to reproduce the nesting structure at all. I'm sorry.

[grantx2016]

Hi @akosbalasko,

You will see that I attached a small screenshot from Evernote in Note 5 showing the nesting. The way Evernote tagging works is that simple tags are visually nested (Method A) without needing to include the path to the parent tags (like in Method B). However, some users implemented an alternative tagging naming convention to include the path through the parent tags (Method B).

The visual nesting information must exist somewhere in Evernote in order for it to render the tag hierarchy like the screenshot that I attached. If it was possible to access that information, then the tags set up via Method A might be able to be converted into the format of Method B, and then Yarle could migrate them normally. I really don't know what the Evernote API offers to assist (Evernote Dev is, unfortunately, not my thing) but it would be a HUGE positive for Yarle to be able do this tag conversion from Method A to Method B.

[akosbalasko]

Sure sure, the problem is that tags are managed globally within Evernote and the list of the tags are not exported as a hierarchy into a note. To proof this, I imported your enex to my Evernote and it recognized the tags added in a hierarchy, new level-1 level-2 level-3 tags were added among my tags, but without organized into the hierarchy:

It may happen that Evernote API allows us to get the hierarchy (I think it should at least :) ), and it would have another benefit namely we should not export enex anymore, just connect yarle with EN, pick the notebook, and that's all. So it may open the gates to many other possibilities.

Currently I work on a different big-thing, but when it is released I think this way could be the next one!

Thank you for raising this up!

[grantx2016]

Imagine that ... connect via the API and suck all my notes out and into Obsidian, with everything intact. That would be awesome.

Knowing Evernote, they would find a way to break it and stop the exodus. 😂

[akosbalasko]

:D Sure, I'm sorry Akos, but your dev key is not valid anymore. :D