AWESOME approach! Thank you for sharing this!!
Between this and using Calibre with the md export plugin to convert my ebook translations is going to really amp up my Bible Study!
I’ve updated my Bible by chapter approach to use the Berean Standard Bible (BSB) version. As of April, 2023, the BSB is openly licensed. This makes it so much easier to work with, especially when it comes to incorporating it into wiki style works which may be republished online. No need to worry about using too much Scripture like you would have to with most versions.
This simple script downloads the BSB and converts it into markdown files for Obsidian. Each chapter has it’s own file, e.g. “Genesis 1.md” and a “Bible.md” index file is also created for navigation. It will output all files into a subdirectory called BSB. The script was written and tested on Mac, it should work just as well on Linux.
Script: bsb_to_obsidian.sh
1 Like
This script created a BSB directory with a Bible.md file in it on my Manjaro Linux Desktop. Afterward, the following three lines kept repeating endlessly.
Outside of the BSB directory I found …
bsb.txt - appears to contain entire contents of the BSB.
bsb-utf8.txt - also appears to contain entire contenst of the BSB.
./bsb-to-obsidian.sh: line 30: $book_file: ambiguous redirect
./bsb-to-obsidian.sh: line 33: $book_file: ambiguous redirect
./bsb-to-obsidian.sh: line 34: $book_file: ambiguous redirect
THANK YOU for sharing, though! Awesome idea - just wished it worked on Linux.
@MichaelM, I know I’m replying to a post that’s two years old, but I’d love a copy of the zip file you mentioned in Feb '21. I speak German, so that’s no problem to me.
Question especially for those of you who are using one file per chapter or one file per verse: is your Bible (and commentary) its own vault, or is this part of your main vault?
I have only one vault where everything is: My Bible (chapters per file), my daily notes and everything else.
Some reasons:
- I can link all files to a specific passage in the Bible.
- I can see which file links to which chapter (as backlinks).
- I can use the Bible Linker, which works perfectly for me.
1 Like
Sorry for the delay in response, I think it may have been that the $book_file variable wasn’t being quoted properly. I made an update to the script to quote it on those 3 lines, you want to give it another try? bsb_to_obsidian.sh · GitHub
If that doesn’t work, then it could be that Linux doesn’t like the way I’m creating in the variable on line 28?
1 Like
I am curious if anyone is familiar with Jonathan Edwards’ note-taking system and if there are any successful attempts with this system using Obsidian. Dr. Matthew Everhard has made numerous videos about Jonathan Edwards’ note-taking system:
2 Likes
Thank you for sharing! After watchting some of these videos, I decided to sort my notes according to the following system:
- T001, T002, T003 … for notes on theology
- I001, I002, I003 … for illustrations
… and some categories more. For each category I will create a list where I add new entrys manually.
I will also link the entries to the specific bible passage and I want to write it in the margin of my bible. In the margins of my bible i already have hashtags of special topics and smaler notes.
In this post I explain the structure of my Bible notes
I’m not sure I see the point of placing the whole Bible into Obsidian. The likelihood that anyone will have notes on every verse in their lifetime is highly unlikely. And you’re adding a huge amount of text into your vault.
Also, it is so easy to link to passages in Bible apps better suited for reading the text.
I insert only the passage I’m currently studying. This also reduces the noise in the vault and allows it to grow organically allowing me to see what I’ve actually studied.
I’m not using Edward’s system but build my own “Zettelkasten-like” system for note-taking including my Bible notes. I know that it’s very tedious and I’m not saying it’s for everyone. But I like that I have an unambiguous ID for every note that I can then reference in my print Bible.
Here is an example of my “Zettelkasten” vault (it’s a sub-vault within my main vault):
Anyone more experienced willing to do this for a number of Bible translations and then just share them? That way the rest of us (who know nothing of code) could use it! I’d be especially interested in a Greek (NA28) and Hebrew version.
Your system is very interesting. How do you deal with notes that refer to several Bible texts (e.g. “List of images for the church in the NT”)?
That sounds very good. I think the biggest problem with sharing Bibles like this is the copyright issue. If someone would do this work with copyright free versions (for the Greek Bible), I would be really happy (something like the Berean Study Bible GitHub - gapmiss/berean-study-bible-with-strongs: Markdown-based Berean Study Bible with Strongs Hebrew & Greek definitions, created for the Obsidian knowledge-base application.)
1 Like
I use the BHS (Hebrew OT) and LXX (Greek OT) from this repo: GitHub - AnthropologieBiblique/MarkdownTexts: A collection of markdown texts for exegesis and theological research
I’m intermittently working on importing and formatting the SBLGNT for my vault. It has a pretty generous license: GitHub - LogosBible/SBLGNT: Source files for the SBL Greek New Testament.
For lists I just make a note with the relevant verses. Here are two examples, one with bible verses that speak on assurance of salvation and the other is just an ongoing list I just started with Paul’s prayers for the churches:
As you can see these too have their unique IDs so that they can be referenced in the vault and in my print bible. And then I just reference the note in my running commentary note.
In Public Domain is the Byzantine Text (NT) (GitHub - byztxt/byzantine-majority-text: Byzantine Majority Greek New Testament text edited by Robinson and Pierpont, with morphological parsing tags and Strong's numbers).
nice solution
1 Like
I have something for SBLGNT and the MT, not really in shareable state unfortunately yet