Open blittle opened 7 years ago
Sounds like fun. The biggest issue I had with this is the copyright on the content.
I had a nice long talk with someone from the church offices and the basic result was we're restricted to consuming the data directly, but not publishing it or derivatives of it.
I had a previous project that converted the data to something more web friendly offline and he was worried that would break some copyright laws.
Hmmm. Sounds messy. I noticed they have a JSON API for all of the content as well:
http://tech.lds.org/glweb/?action=catalog.query&languageid=1&platformid=10&format=json
I wonder if we could get around the "publishing" changes with just CSS
Or is it easier to ask for forgiveness than permission?
It's not too hard to consume the data directly in the browser, this app does just that.
If you add in workers and persistence, a local copy of optimized data can be stored. The step of downloading and converting the data can be done locally in the browser once for a user and saved.
Very true. The only reason the pure JSON api interests me is that I could avoid loading the 2mb sql lite JavaScript implementation. Though if that would loaded once inside a service worker, it might not be that big of a deal.
I wish we could just get the tech team at the church to publish a format more web friendly. We'd probably be willing to do the dev work if that's their main issue.
Tim,
I love the work you have done here. I'd like to adapt it to use service worker cache for sqlite storage. I'd also like to build a crowd-sourced mechanism for annotations. I'm curious if you are interested in helping out? In general I appreciate your prior work in figuring the church's API's.