[request] Bradley: Please expose the 'traits' column in collections
Comments
-
Mark Barnes said:Kolen Cheung said:
Sadly, people keep digressing in a db-writing-phobia without really answering if in principle it can be done or not.
Start a new thread asking that question, and I will answer that question (and repeat all the reasons I and others have given elsewhere why it's not a good idea).
No, because I don’t think I have digressed, and I don’t think there will be anything new coming from there.
People here are too hostile to ideas like this, which is unnessary. I heard you about that being not supported and no one hear I ain’t asking for permission because I don’t need any. I just need to know if that is in principle doable. If not, I won’t even waste time trying to start working on it. Else I still might not start it because the time cost might not worth it if the problem Im trying to solve is too small. But I like to gather ideas in my brain first so when problems arise there’s a possible direction to go for.
0 -
Kolen Cheung said:
I just need to know if that is in principle doable.
Of course its doable in principle. Nobody would bother giving you all the reasons not to do it if it was technically impossible anyway. But again, if you haven't understood that from everything that everyone has already said, then you don't have the ability or the knowledge to pull it off without breaking everything, probably irreparably.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
I said repeated not breaking anything is not the point. The point is there’s a well controlled way to contain any problems in a sandboxed VM with snapshot for fast prototyping.
But thanks for letting me know it is doable in principle. That would save me time. I start peeking into the db last weekend. But this is not a high priority item for me. One of my higher priority item is define certain format that can be compiled to PBB docx. This has been on my mind for years but some recent new info got me existed to revived this idea. I got digressed however.
edit: there’s also a very different way of looking at problem solving here. One view is that someone first know much about the db first and gradually accessed if a certain thing is doable. Those thinks without such knowledge first one can’t even start thinking about the next step. I however like to access what that ability (knowing the db well) will enable me to do certain things. Now if any of them becomes my goal I’ll spent my time doing it else won’t even spend time looking into it.
0 -
Kolen Cheung said:
The point is there’s a well controlled way to contain any problems in a sandboxed VM with snapshot for fast prototyping.
A sandboxed VM that never syncs to your Logos account is the only way to contain any problems.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark Barnes said:
For example, the data in the traits column would allow us to create collections of:
- All our reverse interlinears
- All the morphologically tagged resources (which a specific morphology)
- All the resources used in the Illustrations section of the SSG.
- All the resources that have spoken audio
Dreaming of a Faithlife supported exposure for interlinear(s):
- Interlinear
- Reverse
- Bible Book range
An interlinear change since this thread began 5 years ago is Logos 8 Basic including free access to many Reverse Interlinear resources.
Also would appreciate a column showing Morphological tagging in resource that ideally matches Morph Search choices. One change since this thread began is the removal of one Greek Morphology (transitioned to Logos Greek Morphology). Work around for personal tagging is searching all resources for word(s) that frequently occur: e.g. the definite article.
Like idea of a Library column that shows which resource(s) have their own audio recording (while dreaming of a Hebrew Bible Read Aloud for Lexham Hebrew Morphology)
Keep Smiling [:)]
0 -
Mark Barnes said:Kolen Cheung said:
The point is there’s a well controlled way to contain any problems in a sandboxed VM with snapshot for fast prototyping.
A sandboxed VM that never syncs to your Logos account is the only way to contain any problems.
I disagree but let’s agree to disagree.
And even that is not all that limiting. I really tried to keep my cloud interaction minimal.
Even if one is imposing that requirement (never sync back once modified) to themselves, they can always use snapshot to help. When there’s an update one want to sync, revert back to unmodified status and update and then run an automated script to the desired result again.
0 -
-
I uses the trait from the resource metadata API to create search query string by title search. The collection rules are dumped in https://github.com/logos-extras/logos-meta-dump.
From
collection_rules_all.ymlI created a bunch of example public collections started with “Collection—”And from
collection_rules_traits.ymlI created a bunch of example public collections started with “Trait—”, which is of interest in this thread. Examples are:- Collection Nested—Audio
- Trait—media-type:audio
- Trait—audio-target
- Trait—audio-source
- Trait—has-reverse-interlinear
Note that it is not perfect because it is limited by the features Logos currently offered and specifically uses a title search. E.g. ‘Trait—has-reverse-interlinear’ includes “中文聖經和合本修訂版（上帝版．繁體）” for example, although its reverse interlinear feature is still in pre-pub. Not to mention some license that one might not own while owning a title with that name (e.g. one might not own the reverse interlinear license or an audio license.)
Moreover, title search has some bug (in another thread) and not exact (e.g. different resource of the same title, or one has a longer title including the other might be included as well.)
But right now, it is the best way one can create collection rules based on trait. For example, if you want to have an OR match on different traits, you can create 3 collections with those trait individually and then apply an OR-collection search, as an example in “Collection Nested—Audio” above.
Also note that the performance is not great since it is not performing an exact search. But again it is the only way given the current feature available right now. If you own cared resources you own, then you can "collapse" that search by performing a library search and save that result as a collection and it will be collapsed into a collection with "add this resource" only, as noted by Mark from another thread.
0 -
Consider mentioning your support for this project in Logos 9 Wishlist
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0
said: