<p>
Raoul,
</p>
<p>
I have been working on and off on an import tool for CCLI's SongSelect. My tool is currently PHP based, utilizing curl to grab data from their web site.
</p>
<p>
I spoke with the VP of IT at CCLI a few weeks ago to verify that I was not breaking any rules by trying to grab such data. In short, I am not. CCLI has an understanding with the publishers that any CHURCH may use any tool they wish to access and retrieve data from the SongSelect database. The problem with the agreement between CCLI and the publishers is that CCLI is forbidden at the moment to assist developers in retrieving that data. Basically, they can tell us that we can get the data, but not how.
</p>
<p>
The thing to keep in mind is that they only allow the import of CCLI information from the church holding the CCLI license. You can't obviously distribute a program with CCLI songs within it. Nor can you develop a program that hosts CCLI songs for access by churches.
</p>
<p>
In openlp's case, it would be fine with them to write a program that will take a user's CCLI username, password and then import songs to their openlp installation.
</p>
<p>
At any rate, you would be most welcome to the bit of jibberish I have begun scripting to import items from CCLI. I have by no means completed it, but have a handle on a portion of it. I have written it in PHP for a project that I and another guy are working on called "openworship". We are hoping to build a program similar in scope to planningcenteronline.com and other ministry planning tools and tying it into openlp (as that is what my church is currently using). We also have some of the basics already in place to work with OpenSong. Anyways, you can email me at landersk (at) gmail (dot) com if you would like.
</p>
<p>
Thanks,
Kevin L.
PS - CCLI is hoping to work out a deal with the publishers within a year or so to develop an API. At the moment, of course, they are not allowed to do so.
</p>