Base QR-code on Shortdoi instead of DOI

[Matherion]

This is an amazing package, thanks! I currently do this manually for slides, so this is awesome!!!

When doing it manually, I always first obtain the short DOI at https://shortdoi.org (also possible with the crossref API using e.g https://shortdoi.org/SOME_DOI_HERE?format=json), and then use that to create the DOI. That also allows including the URL human-readbly, e.g. doi.org/bh99), allowing people to quickly scribble down the shortdoi as unique identifier for the paper.

So I thought I'd, well, drop, this suggestion here as you might like to include that, too :-)

[nucleic-acid]

Hi, thanks for the feedback and the idea. I haven't thought about shortDOI in that context, but it is an intriguing idea.

I have two questions regarding your idea:

• would the short doi also be included in the text?
• should the drop_name function access the short doi on the fly as an option like e.g. shortDOI = TRUE?

Honestly, I think this feature would take more time to properly implement&test than I have right now. I will definitely keep the issue open but cannot give an estimate on when this might make it into a release.

For the time being I would recommend using e.g. Zotero as reference manager in combination with the DOI manager plugin which allows automatically obtaining shortDOIs and I think also allows for 'swapping' long/short DOIs for export. Thus you could supply the short DOIs to namedropR already now.

[VictorVenema]

I like the idea of also having a short URL. That helps people writing notes, as opposed to making photos (that would be me, e.g., I like making notes as it helps me remember stuff and at several meetings I know making photos is not allowed).

When I put short URLs on my own slides, I tend to use something that is easy to remember. If the short DOIs are really just 4 characters that would fit, if they are longer, it would be easier for the audience to use some term or name that describes the paper. My latest paper would, e.g., be bit.ly/venema22 or name.drop/benchmarking. I guess that is harder to automate, but I normally do not cite a huge number of papers in a talk, so some manual intervention to suggest a good short URL would be fine from my perspective.

[Matherion]

Yeah, they're always 4 or 5 (maybe 6 sometimes?) characters. Those aren't easy to remember, of course, but only few people have the skills to create bit.ly URLs. But, it was just an idea. Whenever I have a need for this, I'll then probably prioritize this highly enough to have a go at creating the functionality, and then I'll happily submit a merge/pull request (never clear on whether those are the same just GitLab vs GitHub lingo, or different things :-)). Just wanted to share the idea already :-)