The data modelling in a Graph Database is about defining what becomes the nodes and how to connect them, via relations. For example, a text Bible is about 4MB and the Access version around 10MB! The first version was actually written in Access 2000 and even used (the then) brand new ADO (instead of DAO) as the great Microsoft recommended. And even if the data is much larger than can be held in memory, it seems like a custom system will always out-perform an off-the-shelf database solution. While working on that, we became familiarized with the data structures used to represent the Bible, various versions of the Bible, issues with versification mismatches between versions, etc. 3 1 1 3 And God said: 'Let there be light.' In February 2001 it consisted of two or three HTML pages and about five downloadable files. (even today) I don’t think this needs much clarification. 2 1 1 2 Now the earth was unformed and void, and darkness was upon the face of the deep; and the spirit of God hovered over the face of the waters. VerseVIEW 6.5 supports Bible database from Zefania XML Bible. A database file that is less than or equal to 1073741824 bytes in size contains no lock-byte page. To answer these, we made a small exploration into the world of current Graph technologies, toyed around with a couple of databases and tried to model the data we have as graphs. I should also mention the time and money required to make a custom system might make it infeasible. When I started almost everyone asked why put The Bible in a database. 2 And the earth was waste and without form; and it was dark on the face of the deep: and the Spirit of God was moving on the face of the waters. 3 And God said, Let there be light: and there was light. The relational databases have been around for a long time and have greatly influenced our thinking. It includes: So, we have some data we wanted to build a graph with, the next challenge was the actual data modeling. By Subscribing to the newsletter (you can of course unsubscribe anytime) you will be advised from time to time on what has been added to the site. You can subscribe from the main page or the downloads page. We have an alignment project at BCS, as part of the AutographaMT platform, where we built a tool to align the words of the Bible in 12 Indian languages with the original languages- Greek and Hebrew. That's right, some folks make big bucks out selling Bibles. Simply import the BibleDatabase text file as a TAB separated file without any text separators. There may be interesting applications for distributing resources using the Text Fabric file structure and then using (or not using @FoolRunning!) You take The Bible(any version) and put it into a database, you will have a database structure as simple as: Now you find the source data (way to much to list all) and you will have a text file like: Depending on the source (text, html, json, xml, etc.) A database file larger than 1073741824 contains exactly one lock-byte page. Maybe my thinking comes from my distaste of having to “query” for information instead of just accessing data objects in the code. b_kjv.txt for the King James. Developers can download it freely for their development works. For example, a text Bible is about 4MB and the Access version around 10MB! - Customize color schemes, fonts, default start-ups, date format, etc. When we wanted to experiment on Graph database we thought of using the same data. Lastly, please note that although we believe the Copyright information published on this site is accurate, we cannot be held responsible if information is incorrect. The Graph database is a rising trend in technology today. The Bibles on this website do not belong to us. What data would go in it? a database to ingest and use the data in an app. You may want to check out more software, such as Unbound Bible Tools , Logos Bible Software or Computer Bible Study Library , which might be similar to Bible Database. By the way, the same text engine is used in a different [business] application for a multi-user, relational database and works exceptionally well. Parallel Bibles (2 languages only) These sets display TWO Bibles in parallel (your language + English). 1 November 2018 / github / 1 min read Bible databases as XML, JSON, SQL & SQLITE3 Database format for various languages. So Access was tossed out the window in exchange for a simple text format which runs really quickly. CHAPTER - The chapter Number
Seeing data like this being used in apps would be amazing! It is going to be an integral part of the Vachan Engine we are building at BCS, to serve as a smart/intelligent data engine that powers various AI-aided Bible Translation applications.