Good Morning:
I had responded to a variety of expressions of interests in this thread in the General forum with an Excel file containing pericope headings and verse ranges (with subsequent corrections) that I had made several years ago. I also created a .docx with headings and bible milestones. It was suggested that I post them here also, in case someone finds them helpful.
7774.Pericopes PB.docx
2450.Pericopes.xls
No longer actively posting. Please remind T-Bone to take his meds.
Good job...thanks!
Ed B
Thanks! What a great tool.
Robert this is great! I would love to convert this into a blank Bible (a page of notes for each pericope)! My plan is to use the insert text box feature in personal books to insert a text box about 100 lines long after each pericope (this should be relatively easy using the "find and replace" tool in Word. The problem is that I don't understand the code language used on the wiki page. Does anyone understand this? I toyed around with it but it looks like I might need a unique designation for each text box which I don't know how to create other than typing each one individually. If some one could use this info to create a Blank Bible Personal book out of this I would be grateful!
Goodreads | Letterboxd | Blog
Hi Liam:
That sounds like a great idea. I think I know the way to implement it. Since Excel is where the list resides and it handles lists easily, I'll use Excel to populate the Word document. I've done some similar things at work to produce budget documents where Excel queries and formats the tabular data and Word is used for the verbiage.
I think this will be a lot of fun to do. Just letting you know that I am working on it.
Robert that's awesome! Thank you! I think the doc might be one that I will use daily!
Try this out.
5554.Pericope Notebook.docx
Robert this is excellent! Thanks a ton!
Hello Robert - this is a wonderful resource! As a Bible teacher, I want to memorize the significance of each of these pericopes through personal Bible study.
I am new to Logos, however, and need your help, if possible. I learned how to import / build a personal book, but I can't figure out how to edit your list of pericopes, such that when I import it as a PB, I can use it as part of a Logos reading plan. When I use the docx version, since it has a header for each Scripture reference, the Bible Reading Plan thinks they are separate items. I've tried a few things, but can't seem to find a way to make each pericope stand on its own,. For example, January 1 = Genesis 1.1-2.3. January 2 = Genesis 2.4-25; January 3 = Genesis 3:1-24, etc, etc, etc.
Any ideas or help you may be able to offer would be greatly appreciated. I think you have 2,022 separate pericopes, and "I think" Logos Bible Reading Plans can only create a list of up to 1,500 separate readings.... so one work around would be to create an Old Testament reading list and a New Testament reading list.Thanks!
This is great - thank you!
Hi Christopher:
Try this:
If started tomorrow, the plan terminates in January of 2022.
5857.Pericope Notebook Passage list.txt
Matthew Godwin: thank you!
You're welcome!
Hello Robert - Your instructions worked perfectly. Thank you so much! Greatly appreciated, sir!
Just noticed the list is missing the last pericope in Revelation. Revelation 22:7-21.
Liam:Just noticed the list is missing the last pericope in Revelation. Revelation 22:7-21.
Dr. Erasmus: call your office!
Here's it is fixed. If someone has already made the list, it's easy to add the last range manually. I think you can edit the reading plan to "recalculate" it.
5875.Pericope Notebook Passage list.txt
Robert are these fit to every Bible or just the English?
Hi Sascha:
The pericope headings and boundaries in the Notebook PB are "borrowed" from the NIV. Each page has a pericope heading, the verse range, and a space for notes. The passage citations, of course, will pop up (on mouse-over) in your preferred bible, but it will only be the first few verses. I'm not sure if that answers your question. The Passage List text file could be used in any number of ways with any bible, barring versification issues.
Perhaps you could expand on your question or your specific idea or needs and we can work from there.
I did another pericope-related PB found here: https://community.logos.com/forums/t/126999.aspx . It uses dynamic text, so it will be in whatever language bible you have in Logos, but it has a different purpose than the PB here (no notes). It's not the prettiest thing in the world, but the Excel file I provided with it might be valuable for some projects.
Hi Robert
thanks for answer. I created a German Bible Template and would like to put the Pericopes in, but I don't know if they are sync together with yours at least I have to translate the Headings ;-)
In the Passage Analyse Tool I could choose the Luther Pericope, with German Header but I cant't find a List. Gues I have to do it by myself
2273.Bible.docx
Sascha:
If you do a Basic search for Heading Text in your bible, using the * wildcard, it should get you all the pericope headings and the starting point of the boundary for the pericope. There will probably be a few hits at the beginning from the front material of your bible, but the rest will likely be pericope headings. You can Print/Export one page at a time. Use the Send To a New Document - Microsoft Excel option. Gather the individual exports into a single Excel sheet.
You can assume the other boundary of the pericope is one verse behind the next beginning boundary. That isn't always true but it is ~99% of the time. The rest you will probably notice over time and correct them as you go. When I did this with the NRSV, some of the minor prophets' first verse wasn't within a pericope boundary and Sirach 30 had a heading not marked as a heading, since it is found in the text. Things will likely be different in bible you use, but these are the kinds of things to look out for.
If you use this method, you'll probably have to export around 30 pages of results. (Maybe someone else will provide us an easier method.) Here's what one page looks like from the ESV:
Thanks Robert :-)