Organize Highlighting - by translation or by book or other method?

Page 1 of 1 (8 items)
This post has 7 Replies | 0 Followers

Posts 163
Michael | Forum Activity | Posted: Sat, Jan 2 2016 2:38 PM

I'm approaching a year of using Logos and have run across an issue that I didn't know was an issue until today.  Organizing highlights in notes files.  I didn't realize that Logos puts all the highlights into a single file by default.  I created a highlighting palette with shortcut keys that I really like using.  Unfortunately I've been using this palette for everything, so now I have all the highlights in a single file for multiple resources.

I fear the file is getting too large and may become cumbersome down the road, so now I'm looking at my options for splitting it up.  I know we can only move one note at at time, so I'm not asking about how to move the notes, rather I'd like to get some input on how some of you have decided to separate highlights in your Bibles specifically across books and translations.

Option 1:  Use separate palettes for each translation.  Any downside in the note file getting too large even though it's for each translation (by resource option).  Right now I mainly highlight in ESV and sometimes in NIV.  I have NASB and NKJV open for parallel reading as well.  So I'm not sure if this is a great method or not to have separate highlights by translation.

Option 2:  Use separate palettes for each book of the bible.  Is this too much?  Is it cumbersome to make 66 palettes that may or may not be used across translations?

Other options?

I'm open to ideas on how I can best manage highlighting to optimize organization and performance in Logos.

Thanks!

Posts 196
Stephen Terlizzi | Forum Activity | Replied: Sat, Jan 2 2016 2:47 PM

Today I have found out that I have a similar problem.

I have been using Logos and highlighting for about two years. Within my Highlighter Pens document, I have thousands and thousands of highlights.  For example, from the Summa Theologica, I have 3,400 highlights...JPII TOB 1,803...RSVCE 1,760...CCC 1,347...and others with hundreds of highlights.  In my top 10 resources alone I probably have more than 11,000 highlights.

Is there a way to open the Highlight Pens document and using the Quotes view to highlight an entire resource and drag it into a new document?

Thanks for your help!


Agape,

Steve

Posts 27673
Forum MVP
JT (alabama24) | Forum Activity | Replied: Sat, Jan 2 2016 2:57 PM

Hi guys! I only have a second as I am taking a short break from driving... So the short answer (for now): The best approach, in my opinion, is resource specific note documents. There would be ONE note document for each resource (I.e bible, book, journal, etc.). The bad news: you would have to manually move previous notes to the new documents one at a time. Also, the method for controlling this behavior is (shockingly) different on desktop vs. mobile. The good news is that once you set it up, you can forget about it. The only additional thing I do is to have a limited number of thematic documents, but the method described above fits most all of my highlighting. 

OSX & iOS | Logs |  Install

Posts 3185
Whyndell Grizzard | Forum Activity | Replied: Sat, Jan 2 2016 3:51 PM

My (new) method, becuse I hadto adjust to the way notes and highlighting works:

1) I created a different pallet for ESV, NASB and Net- my 3 English ranslations, I also have in Multiple resources a Greek and Hebrew version chosen- this way I hilite in the original and it shows in the English version as well- except for NET which has no morpholgy.

2) Whenever I study a book, say "unseen Realm" I create a pallet for it nad use it for the book and referenced bible verses, this is working out very well- it means when I turn off the highlighting for Unseen realm all the markup disappears from the book as well as the bible verses.

Posts 21914
Forum MVP
Graham Criddle | Forum Activity | Replied: Sat, Jan 2 2016 11:11 PM

Michael:
Option 1:  Use separate palettes for each translation.  Any downside in the note file getting too large even though it's for each translation (by resource option).  Right now I mainly highlight in ESV and sometimes in NIV.  I have NASB and NKJV open for parallel reading as well.  So I'm not sure if this is a great method or not to have separate highlights by translation.

There is no need to have a separate palette per translation. 

If you set the palette to use a "resource-specific notesfile" then highlights for each Bible translation will be stored in a unique notesfile. This is, in my opinion, the best approach for most scenarios.

Michael:
Option 2:  Use separate palettes for each book of the bible.  Is this too much?  Is it cumbersome to make 66 palettes that may or may not be used across translations?

This would be really difficult to manage and use. It would make using shortcut keys virtually impossible which, I expect, would make highlighting more difficult. So I wouldn't go down this route unless you are expecting to be producing a really large amount of highlights per translation.

If you are doing a lot of highlighting and you do want separate notes files per biblical book then one approach (still using a single palette) would be to set the palette to a "biblical book specifics notes file"" at the start of a highlighting session which would cause all highlights to go into a specific document. Then you would need to remember to change this linkage when you moved into another biblical book.

Posts 163
Michael | Forum Activity | Replied: Sun, Jan 3 2016 9:39 AM

Graham Criddle:

Michael:
Option 1:  Use separate palettes for each translation.  Any downside in the note file getting too large even though it's for each translation (by resource option).  Right now I mainly highlight in ESV and sometimes in NIV.  I have NASB and NKJV open for parallel reading as well.  So I'm not sure if this is a great method or not to have separate highlights by translation.

There is no need to have a separate palette per translation. 

If you set the palette to use a "resource-specific notesfile" then highlights for each Bible translation will be stored in a unique notesfile. This is, in my opinion, the best approach for most scenarios.

Michael:
Option 2:  Use separate palettes for each book of the bible.  Is this too much?  Is it cumbersome to make 66 palettes that may or may not be used across translations?

This would be really difficult to manage and use. It would make using shortcut keys virtually impossible which, I expect, would make highlighting more difficult. So I wouldn't go down this route unless you are expecting to be producing a really large amount of highlights per translation.

If you are doing a lot of highlighting and you do want separate notes files per biblical book then one approach (still using a single palette) would be to set the palette to a "biblical book specifics notes file"" at the start of a highlighting session which would cause all highlights to go into a specific document. Then you would need to remember to change this linkage when you moved into another biblical book.

Thanks everyone for the replies.  I set my custom palette to save into resource specific files now and will see how this goes.  It seems like the right choice to keep things simple while separating my notes into small enough files to be manageable.  I also use shortcut keys a lot so this method will preserve the ability to use them.

I hope Faithlife eventually makes it easier to move multiple notes from one file to another instead of one at a time.

Posts 27673
Forum MVP
JT (alabama24) | Forum Activity | Replied: Sun, Jan 3 2016 10:32 AM

Michael:
I hope Faithlife eventually makes it easier to move multiple notes from one file to another instead of one at a time.

+1

OSX & iOS | Logs |  Install

Posts 196
Stephen Terlizzi | Forum Activity | Replied: Sun, Jan 3 2016 10:41 AM

alabama24:

Michael:
I hope Faithlife eventually makes it easier to move multiple notes from one file to another instead of one at a time.

+1

+1

Page 1 of 1 (8 items) | RSS