I am having to do it the cut & past way.
If you are in the UK you cant use the ccli website to import from songselect database. CCli dont apear to approve of, or recognise Openlp & were verbally ignorant of it asking 'is it an american prog?'
Quite frankly I feel this level of ignorance & 'attitude' is apalling from an organisation that takes so much money from us.
If anyone knows how to import the 10,000 song database that is in the Song-select program please tell us!
I have used the CCLI database extensively over the last few years.
The CCLI database is made for the benefit of songwriters and the royalty companies -- not us.
That is why the CCLI database remains closed.
That is why song lyrics in each and every song is so poorly organized -- chorus first always????? how stupid. Pre-chorus? Never exisited until last year. Marked as Misc. Bridge? Marked as Misc. Chorus 2? Marked as Misc most of the time.
In short, even if you COULD automatically import the entire CCLI database, EACH and EVERY SONG would have to be manually corrected.
For now, I'll continue doing it the old-fashioned way: cut-and-paste-and-fixing-it.
Sorry, welcome to CCLI Reality Class 101.
P.S. Some commercial lyric projection software are able to link to CCLI so that once you find a song you can import it easily into your software -- i.e. automatic cut-and-paste. However, the problem with ehse commerical packages is that they normally don't EXPORT songs, meaning you aren't able to SHARE you song database with others.
P.S. Some commercial lyric projection software are able to link to CCLI
so that once you find a song you can import it easily into your
software -- i.e. automatic cut-and-paste. However, the problem with
ehse commerical packages is that they normally don't EXPORT songs,
meaning you aren't able to SHARE you song database with others.
Can you tell us which commercial programs? I'd like to see if I can intercept their HTTP requests and perhaps figure out what they're doing. Perhaps we can then reverse engineer it, although how legal that is might determine whether or not we implement it.
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.
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.
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.
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.
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.
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.
One such "off the shelf" program that imports ccli information is EasyWorship. You can download a demo from their website: http://www.easyworship.com/downloads.php
Re: ccli
Re: ccli
I have used the CCLI database extensively over the last few years.
The CCLI database is made for the benefit of songwriters and the royalty companies -- not us.
That is why the CCLI database remains closed.
That is why song lyrics in each and every song is so poorly organized -- chorus first always????? how stupid. Pre-chorus? Never exisited until last year. Marked as Misc. Bridge? Marked as Misc. Chorus 2? Marked as Misc most of the time.
In short, even if you COULD automatically import the entire CCLI database, EACH and EVERY SONG would have to be manually corrected.
For now, I'll continue doing it the old-fashioned way: cut-and-paste-and-fixing-it.
Sorry, welcome to CCLI Reality Class 101.
P.S. Some commercial lyric projection software are able to link to CCLI so that once you find a song you can import it easily into your software -- i.e. automatic cut-and-paste. However, the problem with ehse commerical packages is that they normally don't EXPORT songs, meaning you aren't able to SHARE you song database with others.
Re: ccli
Can you tell us which commercial programs? I'd like to see if I can intercept their HTTP requests and perhaps figure out what they're doing. Perhaps we can then reverse engineer it, although how legal that is might determine whether or not we implement it.
Re: ccli
Raoul,
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.
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.
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.
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.
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.
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.
Re: ccli
Ah yes, I remember having a quick look at the openworship site, although at that stage there wasn't much there (why not use Python, rather than PHP?).
Thanks for that information, it's very helpful. I'd definitely be keen on taking a look at that script of yours.
Re: ccli