Audio will show up too at some point, probably at http://www.bibletechconference.com/speakers.

As i’ve told a few of my colleagues since: giving the talk helped convince me even more strongly that Biblical Events will be a really important database for Bible study. Looking forward to getting it all put together.

(I did one two years ago that compares the Gospel descriptions of the different events of Holy Week, though it’s somewhat visually-challenged: Blogos post here).

No adoption = no value: you have to plan for adoption. Rogers Bell Curve: perceived utility and ease-of-use matter a lot, which comes back to design. Tip: establish a glossary. “It’s really hard to sit behind someone using your software and not tell them what to do”. “Ideas are cheap, but they still feel like my heart.” “Analytics is the one area I’ve neglected most.” Everything BIG started small. Progressive disclosure: give people a slow introduction to features, don’t overwhelm them up front.

Some interesting sites for augmented reality:

• stickybits: attach comments to physical objects with barcodes.
• Greengoose.com: temperature/sound/vibration sensors. Instrumentation of everything.
• GE smart grid
• Layar: find people who tweeted nearby, wikipedia articles. You can create your own.

BibleReader 5 is their application: showed it on iPad. Originally used EverNote for note synchronization, but wasn’t a good fit. Resource Guide is a new additional to pull in everything in their library that relates to the passage you’re reading. Other library integration around lexicon entries.

Be ready when people sign up to volunteer. Some volunteers act as management, but more it’s clear communication. For internationalization, each language has a lead who makes sure the translations are getting done, that enough people are active, and that the translations are accurate.

Managing all the volunteers used to consume 40% of his week: now they’ve broken it down.

They use HighRise HQ for managing volunteers (37 signals). [also Google Groups, Wave, BaseCamp, Skype conversations]

• Where do they come from? Somebody volunteered, we said yes and posted about it, and now we get 10-15 signups a day! All over the world (but English is required).
• How much do they work? Minimum is 5 hours, all the way up to essentially full-time. Use MyGengo for managing volunteers.
• Why did you start recruiting volunteers? We’re part of a church, so it was natural.
• Do you vett them before they get involved? Yes, similar to our hiring process for staff.
• How do you handle legalities? Hard problem: we choose wisely who we allow on the team. They sign an agreement that code they write for YouVersion belongs to YouVersion, and that they won’t steal their thunder. [comment: in our non-profit, we can't even have interns because of legalities.]
• What about quality of work? Quality is a result of passion, not skill. We have a culture of excellence and don’t accept mediocre work.
• How do you keep them engaged in projects? Need to not see them as “free label”: let them work on what they’re passionate about and make sure they’re working on things that are meaningful.
• What don’t you let them do? Volunteers don’t create the vision.

Scott is @scottmagdalein on Twitter.

• create an environment for studying the Bible
• maintain feature set of bible.lifeway.com
• raise awareness of the HCSB
• sampling strategy for HCSB study notes

Bad timing: started with Silverlight, then moved to HTML 4 (with a little flash). “We get more compliments over how we presented our Strong’s data … ” Development from features to community and awareness. Using MSB.to for URL shortening. Windows Phone 7 is more valuable because of its connection to Xbox (in response to a tweet from @BobPritchett). My Notes tab is coming soon.

Questions:

• Feedback mechanisms? “we consider our feedback link our most important feature”
• Other feedback channels?

Aaron is @linne on Twitter.

They’ve combining the videos with personal testimonies in services: one initial result was very highly ranked on YouTube. Also making videos of picture books: http://scripturestories.lds.org.

Using the Bible Knowledgebase for Information Integration

In 2009 I reported on the Bible Knowledgebase (BK), a machine-readable collection of semantically-organized data about people, places, and things in the Bible. This talk will describe how the BK now functions as an essential information resource for Logos, tying together information across the software. In addition, I’ll discuss the continued work on the data over the last two years, including:

• building a database of Biblical Events
• adding unnamed entities to the database
• coordinating information about these entities with the Logos Controlled Vocabulary

I’ll also present prototypes for visualizing BK data to enhance discovery and exploration in the Biblical text.

I’ll be live-blogging a few talks during the day to give a quick-take on the subject for those who can’t be here. You can also follow on Twitter via #BibleTech.

To recap some of the features:

• Colored blocks are grouped together by pericope so the presentation is organized by the events, rather than the order of texts themselves. The size of the block indicates how many words are associated with the pericope, and the colors indicate which Gospel provided the material. This helps you immediately see things like the fact that all four Gospels provide quite a bit of detail about the triumphal entry, though only Luke includes Jesus’ sorrow over Jerusalem.
• The blocks are grouped by day, through the chronology is uncertain in several places, so this is an approximation at best.
• Clicking on the pericope title takes you to the Composite Gospel page (though apparently some of the indexes are off). Clicking on the colored block takes you to source text at bible.logos.com (and a tooltip indicates the reference). As i recall, i couldn’t figure out a way to use RefTagger to actually display the text more directly in a popup.

Some of the talks i liked best this year:

• I was already interested in Pinax before hearing James Tauber’s talk on Using Django and Pinax for Collaborative Linguistics: now i’m itching to get started!
• Stephen Smith had a nice analysis of the most frequently tweeted Bible passages (though the evidence of vast swaths of Scripture that get very little attention was perhaps a bit depressing).
• Neil Rees showed Concordance Builder, a program that lets you use a Swahili concordance to bootstrap one for Welsh (or any other pair of languages) with no linguistic knowledge. Building on the Paratext tool, it leverages the verse indexes along with approximate string matching and statistical glossing (technical paper by J D Riding) to produce results that are about 90-95% correct out of the book. This can reduce concordance development to a matter of weeks rather than years.
• There were several talks related to semantics in addition to mine: Randall Tan talked about more automated methods and fleshed them out relative to the higher-level structure of Galatians, and Andi Wu gave what looked like a really interesting presentation on semantic search based on syntax and cross-language correspondence (alas, i missed it).
• Weston Ruter talked about APIs they’re developing at OpenScriptures.org (and brought in the Linked Data idea). Logos also unveiled their new API for Biblia.

I felt my talks went well and i got some good feedback. My slides are now posted (if you wrote down URLs at the conference, i didn’t get them quite right but here they’re correct):

• Annotating Linguistic Reference in the New Testament (http://www.semanticbible.com/other/talks/2010/BibleTech-NTReferents/BibleTech-NTReferents.html)
• A Controlled Vocabulary for Biblical Studies (http://www.semanticbible.com/other/talks/2010/BibleTech-LCV/BibleTech-LCV.html) — this is what we internally call the Logos Controlled Vocabulary (LCV).

(As with some previous talks, i did my presentation with Slidy (previous post): i feel like it’s going a little more smoothly each time.)