Incorporating into a Web App

amoore

Disclaimer: I've not dug into the OLP code as of yet.
I'm working on creating a web app which would allow for management of church members, team members, service planning, etc. (Planning Center-esque but lighter and more modular--and self-programmed because I'm a glutton for punishment, I'm sure). I would like to add a feature where an OpenLP service could be created on a computer and uploaded to the site. Then, other users would be able to 1) download the service and open on their computers (that's the easy part) and 2) see the songs and scripture listing in the website itself without downloading to their computer...I don't need the full text of the songs or the videos, etc...just a listing. Is that possible to pull out of the service file using a php, javascript, etc backend?

joe

For someone who can code (which ain't me) it seems easy enough:

unzip the file, and parse service_data.osj
Extract all titles like <title>R\u00fcckenwind</title> (beware of unicode signs: "\u00fc" = "ü")
list them on the webpage. Done.

I cannot see the usability gain compared to the services synchronized with Dropbox and opening them directly with OpenLP. Log into a web interface → choose a service → download it → open the downloaded file with OpenLP seems a bit long-winded to me, but your needs are others than mine, so: go ahead :-)

jlgtx

When you pull data from the service file, you should also be able to generate a list of CCLI numbers, or at least song/author info, for easy weekly reporting. If you store band resources (lead sheets, piano/vocal scores, ChordPro files, etc.) according to CCLI and/or song/author, you could also automatically generate a "resource pack" for the musicians based on the OpenLP file.