Problem with Resources with Custom Names
This will take a minute to explain, so please bear with me. Some commentaries in Logos have names that are either identical or extremely similar. I could give many examples, but I simply submit the following screenshot from part of a Passage Guide I ran on Mark 1:1.
Just by looking at those results, I have no idea which link will open open which commentary. Even when there are no duplicates, I sometimes struggle to know which link opens what. I could not tell you what commentary series "A Commentary on the Holy Scriptures: Mark" belongs to unless I actually click the link. Thankfully, Logos 7 allows me to give custom names to resources so I can better identify them. I have renamed the three similarly titled commentaries as:
1. Cambridge Greek Testament: Mark (Plummer)
2.Cambridge Greek Testament: Mark (Maclear)
3. Classic Commentaries on the Greek New Testament: Mark
This allows me quickly see which commentary goes with what set, and it further allows me to know which volume is which when more than one author has written a commentary covering the same biblical book within a commentary set. In Logos 7 this is a perfect solution and works flawlessly.
However, on mobile there are some problems.
The mobile app recognizes that I have renamed the resource when viewed from my library or under the "Book Info" dialog, but the original name that is hard to differentiate from other commentaries still shows up when I run the Passage Guide in the mobile app. Even more problematic than this is the way the mobile app handles highlighting on resources with custom names. I have both Logos 7 and the mobile app set to use "Resource-specific Note Document" for highlights. I want one note document for each resource that I highlight or take notes in. Logos 7 has no problem with this. If I make a highlight in the resource shown in the above screenshot, it will automatically go into a note document called "Classic Commentaries on the Greek New Testament: Mark." If I make a highlight in the exact same resource on mobile, it defaults into a note document called "The Gospel according to St. Mark." See screenshot below.
As a result, my highlights get split into two note documents depending whether I am working from Logos 7 or the mobile app. Even worse, in the case of commentaries with the same generic title, the mobile app will place notes from separate commentaries in the same file because they have the same name.
So far the only workaround I have found is to manually select which note document I want my highlight to appear in every time I want to make highlights in a resource from the mobile app. This becomes tedious, but if I don't do it I will have to spend time cleaning up my notes documents the next time I am on my desktop.
Hopefully this makes sense, and I will be happy to re-explain it if needed. In short, Faithlife please (1) enable the mobile app to use custom names for resources everywhere, not just in some places, and (2) enable the app to automatically create and use note documents whose titles match up with the custom names of resources. Thank you, and apologies for the long post!
Using Build 5.10.2 on Android Android 6.0.1, if it helps.
Comments
-
Hopefully this makes sense
Great explanation
In short, Faithlife please (1) enable the mobile app to use custom names for resources everywhere, not just in some places, and (2) enable the app to automatically create and use note documents whose titles match up with the custom names of resources
For info for developers:
- This works the same on iOS as reported here on Android - so a change to both would be good
- On iOS, notes documents names seem to match custom names
0 -
(2) enable the app to automatically create and use note documents whose titles match up with the custom names of resources.
Hi Matthew,
I've written up a case for this one; it works on iOS but not on Android.
(1) enable the mobile app to use custom names for resources everywhere, not just in some places
This issue is more of a problem since Guide results are served from the web and do not use local custom resource names. I'll enter a suggestion case for this one.
0 -
Thank you Kevin. For what it is worth, I would be willing to wait an extra few seconds in order for Passage Guide results to display custom names. Others may disagree and want the fastest results possible, but taking the long view of things, it is ultimately faster to open the resource I want on the first time than opening possibly multiple resources I do not want just because I am trying to figure out what they are.
0
