BUG: FSD in {Collection} is broken
The Facilitate Serendipitous Discovery (FSD) command is undocumented (in Help file), but it's been revealed by Logos employees numerous times and is documented in the wiki in this page: https://wiki.logos.com/Desktop_Commands
You're supposed to be able to add "in {Collection}" to the end of the command to have Logos open to a random location in a random resource within that collection. But this variation does not work. It doesn't even recognize FSD as Facilitate Serendipitous Discovery if you add a collection parameter to it.
If you type in the full command name with the parameter, at least it recognizes the Facilitate Serendipitous Discovery command, but choosing it will not restrict the FSD command to that collection.
It opened to a random place in a book that is not in my Prayers collection.
Comments
-
You're supposed to be able to add "in {Collection}" to the end of the command to have Logos open to a random location in a random resource within that collection. But this variation does not work. It doesn't even recognize FSD as Facilitate Serendipitous Discovery if you add a collection parameter to it.
That's strange - it is working for me
I wonder if there is some strange conflict with the word Prayers. What happens when you try this on other collections?
0 -
It's working for me too, even if I create a Collection called "Prayers" and use that. Can you double check the name of that collection in the Collections tool?
Andrew Batishko | Logos software developer
0 -
0
-
I have never seen this before. Can someone explain to me how this works and what the benefits are? Thank you very much.
0 -
-
I only have 3 collections to test.
FSD Works: Journals and typeBible (both collections)
FSD noWork: Commentaries (another collection)
But trying again, Journals now doesn't work
But, trying again, Journals does work, with more suggestions (like GaoLu above). So does Commentaries!
Who knows.
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
It's working for me too, even if I create a Collection called "Prayers" and use that. Can you double check the name of that collection in the Collections tool?
Aha! That was the problem. My Prayers collection is called Prayer Anthologies.
0