How to manage links in titles ?

[Cletip]

When one discussion ends, another begins x)

I just wanted to know what's in the title of this discussion (because having links in titles can be problematic for various reasons (and I probably don't know them all)).
To get a clearer idea of what I want, I invite you to see this post: 
https://org-roam.discourse.group/t/some-problems-with-links-directly-in-the-title/2901

If you've already seen it, no worries, there just might not be an answer ^^
But if you have never seen it, maybe it's better to answer there (in org-roam discuss) for the benefit of the whole community. Unless it is exclusively about Vulpea.
Anyway, your solution I think will help me a lot ^^.

By the way, my personal solution would be to have titles without links, then add a "link" metadata or something like that, so that the links are well created and that it doesn't bother in any way.

[d12frosted]

@Cletip In short, this is why vulpea provides metadata feature in the first place. Org Mode keywords and property drawers do not support links. When you use Org elements API it treats any links there as regular text. Depending on what exactly you need from these links, there might be workarounds. AFAIK there is no simple general solution, as this decision made by Org Mode maintainers roots deep into code base.

So I use the same solution as you as it was designed specifically for this case 😸

[Cletip]

Ok ok thanks for the technical details :)

Someone answered me on the forum. It refers me to several links, which is about 2 years old. And... you already asked a similar question to have links in the keywords! That's crazy.
in the end, I guess you've already looked at the solutions, and you seem to know what you're doing, even though you put at one point here : 
org-roam/org-roam#1464 (comment)
"Which sucks." xD. You must have thought about it and concluded that it must not be so bad, because you use it for vino ;)

I'll just send you this link: org-roam/org-roam#1868.
If you know this issue, there is nothing to say: you have already thought about it, and you still decided to use metadata in vulpea.
On the other hand, if you didn't know about it, maybe it can change your thinking. I haven't looked at it in detail, but I have the impression that their commit doesn't work x)

Last thing, I thought of another solution. Less elegant I think, but maybe more efficient:
Since metadata can have any name, and "vulpea-select-describe-fn" can take any function, why not replace the #+title with a "title" metadata?
The "vulpea-select-describe-fn" function would become a function that would return the name of the "title" metadata, and that's it. Moreover, if one day org-roam decides to change the method of choosing a title, it would allow to quickly make the conversion (because the title with the links would already be done).
What do you think about it? Would there be any missing functionality related to the keyword #+title ?

[d12frosted]

org-roam/org-roam#1464 (comment)

😹 I didn't remember this conversation haha.

"Which sucks." xD. You must have thought about it and concluded that it must not be so bad, because you use it for vino ;)

Ah, I meant - it sucks that I had to write these functions myself. That's how vulpea-meta was born.

I'll just send you this link: org-roam/org-roam#1868.
If you know this issue, there is nothing to say: you have already thought about it, and you still decided to use metadata in vulpea.

Exactly, because it solves only one thing - org roam backlinks. But since the Org API doesn't consider them links - lots of things don't actually work. For example, I publish part of my private notes to https://barberry.io. If I picked approach presented in org-roam/org-roam#1868, I would have to cover this case in my publishing code as well (either by implementing two routines for dealing with links, or implementing my own routine that doesn't use Org elements API, which is bizarre). So again, it all boils down to use cases :) I prefer to comply with Org language definition as it gives me more freedom.

I have the impression that their commit doesn't work x)
Well. It solves the problem in question - Org Roam wants to support backlinks from property drawers.

Since metadata can have any name, and "vulpea-select-describe-fn" can take any function, why not replace the #+title with a "title" metadata?

🤔 You can do it. As you say, vulpea-select-describe-fn can extract that. Just keep in mind that title keyword is kind of special. This defines title for Org Roam, for exported documents, etc.

Moreover, if one day org-roam decides to change the method of choosing a title, it would allow to quickly make the conversion (

I don't think they will since title is a commonly used way to add title for Org files. IMO Org Roam might provide a configuration that controls extraction of title, so you could implement one that extracts it from meta.

[Cletip]

Ah, I meant - it sucks that I had to write these functions myself. That's how vulpea-meta was born.

Ah oook, sorry for the little misunderstanding x)

Exactly, because it solves only one thing - org roam backlinks. But since the Org API doesn't consider them links - lots of things don't actually work. For example, I publish part of my private notes to https://barberry.io. If I picked approach presented in org-roam/org-roam#1868, I would have to cover this case in my publishing code as well (either by implementing two routines for dealing with links, or implementing my own routine that doesn't use Org elements API, which is bizarre). So again, it all boils down to use cases :) I prefer to comply with Org language definition as it gives me more freedom.

I think that conforming to org-mode is actually the best solution too.

thinking You can do it. As you say, vulpea-select-describe-fn can extract that. Just keep in mind that title keyword is kind of special. This defines title for Org Roam, for exported documents, etc.

Yes, I can. But is it really a good solution ? If yes, why don't you do it for example? (Maybe you never thought about it)
What would be the other problems not to use the keyword "title"? Which comes down to answering: where is the keyword "title" used?

I don't think they will since title is a commonly used way to add title for Org files. IMO Org Roam might provide a configuration that controls extraction of title, so you could implement one that extracts it from meta.

Yes, I see.
But this function would be forced (as I have done elsewhere) to remove the links and pass a simple string.