Documentation for ref.ly links?
I was inspired by @Jason Stone (Logos)'s recent video with @Mark Ward where Mark explained how he uses Raycast to produce personalised shortcuts to make him more productive in Logos. As I'm a Windows user, using Raycast isn't an option in the short term, so I've been doing some experimenting using Autohotkey to do this myself in Windows 11.
The approach basically involves using ref.ly links to open resources, guides, etc. I've worked out how to pass a reference to the shortcut and open the link, but I am having some difficulty with Bibles, so I have a couple of questions. I have looked at the ref.ly website but it doesn't give me any further information.
- I use the Anglicised NIV as my top Bible so that I get proper spelling, but I can't find a way of specifying this in the ref.ly link. I know I can get the NIV by passing ";NIV" at the end of the URL but I can't find the string to append for the Anglicised NIV. Just passing "https://ref.ly" plus the reference normally opens the top Bible to the appropriate place, but when I append "Jn3.16" it opens a Personal Book that I use as a marker for prioritisation because it's prioritised more highly than any Bible. I'd therefore like to be able to force a particular version (and yes, I know I could recompile the Personal Book without the reference).
- As I want to create shortcuts to open a number of Bibles, is there a list somewhere of what I need to append for each version, please? I can probably make good guesses for most of those I regularly use, but would prefer just to be able to pick them off from a list.
I also recognise that this isn't necessarily supported by Logos, but I do use Autohotkey for things like autocorrect as well, so am not particularly worried by this. If I get it working properly, I will probably post the script and some instructions here.
Best Answers
-
Hey Greg, I think that the easiest thing to do is to use the share tool to get example links for what you want. For example, Genesis 1:12 in the NIVUK is
https://ref.ly/Ge1.12;anglniv2011
You can also scroll down to Resource ID on the product page. For example,gives the product ID LLS:ANGLNIV2011.
The closest thing to a single list is the spreadsheet that @Mark Barnes (Logos) shared a while back which compares the different subscriptions. The first column has the resource IDs for the different interlinears. You can see the resource ID in the middle. For example, RVI:NLTOT (the reverse interlinear for the Hebrew NLT), you would append ;NLT to your refly link.
This might be nice, if the translations you want happen to be included in a subscription.
Using Logos as a pastor, seminary professor, and Tyndale author
1 -
0
Comments
-
Thank you for tuning into that interview of mine with @Mark Ward, @GregW!
Sr. Community Manager at Logos.
1 -
Hey Greg, I think that the easiest thing to do is to use the share tool to get example links for what you want. For example, Genesis 1:12 in the NIVUK is
https://ref.ly/Ge1.12;anglniv2011
You can also scroll down to Resource ID on the product page. For example,gives the product ID LLS:ANGLNIV2011.
The closest thing to a single list is the spreadsheet that @Mark Barnes (Logos) shared a while back which compares the different subscriptions. The first column has the resource IDs for the different interlinears. You can see the resource ID in the middle. For example, RVI:NLTOT (the reverse interlinear for the Hebrew NLT), you would append ;NLT to your refly link.
This might be nice, if the translations you want happen to be included in a subscription.
Using Logos as a pastor, seminary professor, and Tyndale author
1 -
Thank you very much @Justin Gatlin - that worked. I think the problem was that, because the anglniv2011 is my top Bible, it doesn't specify a version in the ref.ly link that is produced, and I didn't want to have to mess around with priorities to work it out.
1 -
0
-
That makes sense. I did not think about checking whether prioritization affected the link format.
Using Logos as a pastor, seminary professor, and Tyndale author
0
