Music Store/Spec - Revision history

Dave at 18:38, 9 July 2019

2019-07-09T18:38:16Z

← Older revision		Revision as of 18:38, 9 July 2019
Line 34:		Line 34:
	Optional: For bulk purchase code (credits) customers, they purchase bulk credits from you through an HTTP API, and receive a "bulk purchase (credit) code". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, how many credits are left. If you are totally awesome, you should use the same ID for bulk credit AND subscriptions.		Optional: For bulk purchase code (credits) customers, they purchase bulk credits from you through an HTTP API, and receive a "bulk purchase (credit) code". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, how many credits are left. If you are totally awesome, you should use the same ID for bulk credit AND subscriptions.

	when the user clicks the buy song button, i send an HTTPS request url to your server in one of 3 forms:		when the user clicks the buy song button, i send an HTTPS request url to your server in one of 3 forms:<br>
	1) full credit card credentials of the user plus the song ID		1) full credit card credentials of the user plus the song ID<br>
	2) "bulk purchase (credit) code" credentials plus song ID		2) "bulk purchase (credit) code" credentials plus song ID<br>
			or:<br>
	When the user streams a song, or if you keep the user's credit card details in their account, i send an HTTPS request url to your server in this form:		When the user streams a song, or if you keep the user's credit card details in their account, i send an HTTPS request url to your server in this form:<br>
	3) "subscription/account ID" credentials plus song ID		3) "subscription/account ID" credentials plus song ID

	for 1) i send, within the URL, the user's (buyer's) name, address, email, credit card, my affiliate ID, and song ID, and whatever else you'd require		for 1) i send, within the URL, the user's (buyer's) name, address, email, credit card, my affiliate ID, and song ID, and whatever else you'd require for 2 and 3) i send, within the URL, the code (credit or subscription/account), my affiliate ID, and song ID, and whatever else you'd require
	for 2 and 3) i send, within the URL, the code (credit or subscription/account), my affiliate ID, and song ID, and whatever else you'd require

	upon successful processing of the credit card / bulk purchase (credit) code / subscription / account ID (which is handled by your site), the result URL sent back to me is the actual download link for the purchased song. (for streaming Audio+CDG files, i will encrypt the download as it lands on the hard drive, so it can not be extracted and used) For purchases, simultaneously you will send a receipt directly to the buyer (since you got their email address as part of the purchase request), this receipt would ALSO include the download URL, in case something went wrong. this URL may expire in a set number of days if you wish. Note I require the "Content-Length" http header field on this download. if this is not possible due to some technical reason, then you must include the size of the download within the meta data of the "Music Store.xml" file.		upon successful processing of the credit card / bulk purchase (credit) code / subscription / account ID (which is handled by your site), the result URL sent back to me is the actual download link for the purchased song. (for streaming Audio+CDG files, i will encrypt the download as it lands on the hard drive, so it can not be extracted and used) For purchases, simultaneously you will send a receipt directly to the buyer (since you got their email address as part of the purchase request), this receipt would ALSO include the download URL, in case something went wrong. this URL may expire in a set number of days if you wish. Note I require the "Content-Length" http header field on this download. if this is not possible due to some technical reason, then you must include the size of the download within the meta data of the "Music Store.xml" file.

Dave at 02:22, 12 July 2017

2017-07-12T02:22:20Z

Dave at 19:27, 10 January 2017

2017-01-10T19:27:33Z

Dave at 16:47, 19 April 2016

2016-04-19T16:47:17Z

← Older revision		Revision as of 16:47, 19 April 2016
Line 24:		Line 24:
	it's important that each song have a "date added" field. users will sort by "date added" to see the new additions when they get a new copy of your library index.		it's important that each song have a "date added" field. users will sort by "date added" to see the new additions when they get a new copy of your library index.

	allowing the user to audition (play a sample of) the song is important. in one method, you have a web site where the buyer can see / hear preview samples of your songs (typically 30 seconds or so). Each song should be at a unique url. The previews do NOT play within kJams, but are played directly on your web site. alternately: we ~~can~~ arrange for the ability for kjams to download just part of the song so that it can be auditioned right inside kJams. kJams would handle encrypting the song so that only a portion could be played, even if the whole song is temporarily downloaded (this is more like streaming, as the "download" would immediately expire and not be playable later)		allowing the user to audition (play a sample of) the song is important. ideally: we arrange for the ability for kjams to download just part of the song so that it can be auditioned right inside kJams. kJams would handle encrypting the song so that only a portion could be played, even if the whole song is temporarily downloaded (this is more like streaming, as the "download" would immediately expire and not be playable later). alternately: you have a web site where the buyer can see / hear preview samples of your songs (typically 30 seconds or so). Each song should be at a unique url. The previews do NOT play within kJams, but are played directly on your web site.

	The meta data xml/json file is published to a known URL at your site, optionally zipped for download speed. My software, periodically, checks this for updates. if it is newer than last time (ie: the "Last-Modified" header HTTP header is changed) then i re-download, parse, and display the newly updated store list.		The meta data xml/json file is published to a known URL at your site, optionally zipped for download speed. My software, periodically, checks this for updates. if it is newer than last time (ie: the "Last-Modified" header HTTP header is changed) then i re-download, parse, and display the newly updated store list.

Dave at 22:54, 20 October 2015

2015-10-20T22:54:20Z

Dave at 04:30, 17 September 2014

2014-09-17T04:30:12Z

Dave at 04:18, 17 September 2014

2014-09-17T04:18:47Z

← Older revision		Revision as of 04:18, 17 September 2014
Line 13:		Line 13:
	duration of the song in seconds (this is important)		duration of the song in seconds (this is important)
	media format type (MP3+G, mov, avi, mpg)		media format type (MP3+G, mov, avi, mpg)
	~~url to icon~~ (~~if any~~)		song key(s) (eg: "Key of Gm")
	~~song key~~ (eg: "Key of Gm")
	if it's a duet		if it's a duet
	date added to library		date added to library

Dave at 19:39, 11 October 2012

2012-10-11T19:39:23Z

← Older revision		Revision as of 19:39, 11 October 2012
Line 11:		Line 11:
	a URL (or just the last component) for playing a sample of the song (hosted on your server, typically 15-30 seconds of the song in m4v format)		a URL (or just the last component) for playing a sample of the song (hosted on your server, typically 15-30 seconds of the song in m4v format)
	genre		genre
	duration		duration of the song in seconds (this is important)
	media format type (MP3+G, mov, avi, mpg)		media format type (MP3+G, mov, avi, mpg)
	url to icon (if any)		url to icon (if any)

Dave at 19:38, 11 October 2012

2012-10-11T19:38:42Z

← Older revision		Revision as of 19:38, 11 October 2012
Line 1:		Line 1:
	You have a script that runs over your database periodically, OR whenever you add new tracks. this script exports your entire database as an xml file (the "Music Store.xml" file). The XML file can be in whatever format/style is convenient for you, but there are ~~two~~ formats that are particularly easy for me to accept: excel-export, and plist (used by kJams directly), contact me for more info. It must be encoded in UTF-8, and it includes every bit of meta-data you have for each song eg:<br>		You have a script that runs over your database periodically, OR whenever you add new tracks. this script exports your entire database as an xml or JSON file (the "Music Store.xml" file). The XML file can be in whatever format/style is convenient for you, but there are some formats that are particularly easy for me to accept: excel-export, JSON, and Apple's plist (used by kJams directly), contact me for more info. Plist files can easily be created even on windows, using Python. The file must be encoded in UTF-8, and it includes every bit of meta-data you have for each song eg:<br>
	<pre>		<pre>
	name		name

Dave at 20:53, 26 September 2012

2012-09-26T20:53:05Z

← Older revision		Revision as of 20:53, 26 September 2012
Line 33:		Line 33:
	For stream subscription customers, they purchase a streaming subscription on your web store (or provide HTTP API for it and i'll put a GUI on it), and receive a "subscription ID". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, what tier (if any), when it expires.		For stream subscription customers, they purchase a streaming subscription on your web store (or provide HTTP API for it and i'll put a GUI on it), and receive a "subscription ID". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, what tier (if any), when it expires.

	For bulk purchase code customers, they purchase bulk credits from you on your web site and receive a "bulk purchase (credit) code". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, how many credits are left. If you are totally awesome, you can use the same ID for bulk credit AND subscriptions.		For bulk purchase code customers, they purchase bulk credits from you on your web site (or again you provide an HTTP API) and receive a "bulk purchase (credit) code". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, how many credits are left. If you are totally awesome, you can use the same ID for bulk credit AND subscriptions.

	when the user clicks the buy song button, i send an HTTPS request url to your server in one of 2 forms:		when the user clicks the buy song button, i send an HTTPS request url to your server in one of 2 forms:

← Older revision		Revision as of 02:22, 12 July 2017
Line 56:		Line 56:
	==Summary==		==Summary==
	-> client asks for song list (Music Store.xml) eg:<br>		-> client asks for song list (Music Store.xml) eg:<br>
	~~http~~://karaoke.kjams.com/music_store/kJams.xml		https://karaoke.kjams.com/music_store/kJams.xml
	<- server returns download URL link of xml or zipped xml file of song list including all meta data		<- server returns download URL link of xml or zipped xml file of song list including all meta data

	later:<br>		later:<br>
	-> client requests preview song eg:<br>		-> client requests preview song eg:<br>
	~~http~~://karaoke.kjams.com/music_store/previews/kJ00001.m4v		https://karaoke.kjams.com/music_store/previews/kJ00001.m4v
	<- server responds by serving up the file / page with song preview on it<br>		<- server responds by serving up the file / page with song preview on it<br>
	<br>		<br>
Line 72:		Line 72:
	<- server performs financial transaction / gift code / customer code verification, and succeeds<br>		<- server performs financial transaction / gift code / customer code verification, and succeeds<br>
	<- server responds to client with new unique URL to download or stream song eg:<br>		<- server responds to client with new unique URL to download or stream song eg:<br>
	~~http~~://karaoke.kjams.com/music_store/songs/kJ00001.zip		https://karaoke.kjams.com/music_store/songs/kJ00001.zip
	<- if purchase: server emails user directly with receipt including (optionally expiring) download URL<br>		<- if purchase: server emails user directly with receipt including (optionally expiring) download URL<br>
	-> if purchase: client downloads purchased song and installs into user's library<br>		-> if purchase: client downloads purchased song and installs into user's library<br>
	-> if stream: client downloads song and installs encrypted into temp folder (expiring), ready to play<br>		-> if stream: client downloads song and installs encrypted into temp folder (expiring), ready to play<br>

← Older revision		Revision as of 19:27, 10 January 2017
Line 1:		Line 1:
	You have a script that runs over your database periodically, OR whenever you add new tracks. this script exports your entire database as an xml or JSON file (the "Music Store.xml" file). The XML file can be in whatever format/style is convenient for you, but there are some formats that are particularly easy for me to accept: excel-export, JSON, and Apple's plist (used by kJams directly), contact me for more info. Plist files can easily be created even on windows, using Python. The file ~~must~~ be encoded in UTF-8, and it includes every bit of meta-data you have for each song eg:<br>		You have a script that runs over your database periodically, OR whenever you add new tracks. this script exports your entire database as an xml or JSON file (the "Music Store.xml" file). The XML file can be in whatever format/style is convenient for you, but there are some formats that are particularly easy for me to accept: excel-export, JSON, and Apple's plist (used by kJams directly), contact me for more info. Plist files can easily be created even on windows, using Python. The file MUST be encoded in UTF-8, and it includes every bit of meta-data you have for each song eg:<br>
	<pre>		<pre>
	name		name
Line 22:		Line 22:
	For URLs, you can save space in the xml by only including the last component of the URL, and just tell me what the first part is, or put it in a header section.		For URLs, you can save space in the xml by only including the last component of the URL, and just tell me what the first part is, or put it in a header section.

	~~it's important that~~ each song have a "date added" field. users will sort by "date added" to see the new additions when they get a new copy of your library index.		each song MUST have a "date added" field. users will sort by "date added" to see the new additions when they get a new copy of your library index.

	allowing the user to audition (play a sample of) the song is ~~important~~. ~~ideally:~~ we arrange for the ability for kjams to download just part of the song so that it can be auditioned right inside kJams. kJams would handle encrypting the song so that only a portion could be played, even if the whole song is temporarily downloaded (this is more like streaming, as the "download" would immediately expire and not be playable later). alternately: you have a web site where the buyer can see / hear preview samples of your songs (typically 30 seconds or so). Each song should be at a unique url. The previews do NOT play within kJams, but are played directly on your web site.		allowing the user to audition (play a sample of) the song is also required. we arrange for the ability for kjams to freely download just part of the song so that it can be auditioned right inside kJams. kJams would handle encrypting the song so that only a portion could be played, even though the whole song is temporarily downloaded (this is more like streaming, as the "download" would immediately expire and not be playable later).

	The meta data xml/json file is published to a known URL at your site, ~~optionally~~ zipped for download speed. My software, periodically, checks this for updates. if it is newer than last time (ie: the "Last-Modified" header HTTP header is changed) then i re-download, parse, and display the newly updated store list.		The meta data xml/json file is published to a known URL at your site, zipped for download speed. My software, periodically, checks this for updates. if it is newer than last time (ie: the "Last-Modified" header HTTP header is changed) then i re-download, parse, and display the newly updated store list. it is a requirement that it have a "Last-Modified" that ONLY changes when the catalog is updated, it MUST not update otherwise.

	the user can then search and filter your song store from within kJams.		the user can then search and filter your song store from within kJams.

	For stream subscription customers, ~~they purchase a streaming subscription on your web store (or~~ you provide HTTP API for it and i'll put a GUI on it within kJams), and ~~receive~~ a "subscription ID" or "customer ID". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, what tier (if any), when it expires, how much credit they have, etc.		For stream subscription customers, you provide HTTP API for account creation and for login, and i'll put a GUI on it within kJams. customer receives confirmation email, and API sends back a "subscription ID" or "customer ID". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, what tier (if any), when it expires, and if you provide purchase credits, how much credit they have, etc.

	Optional: For bulk purchase code customers, they purchase bulk credits from you ~~on your web site (or again you provide~~ an HTTP API) and receive a "bulk purchase (credit) code". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, how many credits are left. If you are totally awesome, you ~~can~~ use the same ID for bulk credit AND subscriptions.		Optional: For bulk purchase code (credits) customers, they purchase bulk credits from you through an HTTP API, and receive a "bulk purchase (credit) code". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, how many credits are left. If you are totally awesome, you should use the same ID for bulk credit AND subscriptions.

	when the user clicks the buy song button, i send an HTTPS request url to your server in one of 3 forms:		when the user clicks the buy song button, i send an HTTPS request url to your server in one of 3 forms:
Line 46:		Line 46:
	upon successful processing of the credit card / bulk purchase (credit) code / subscription / account ID (which is handled by your site), the result URL sent back to me is the actual download link for the purchased song. (for streaming Audio+CDG files, i will encrypt the download as it lands on the hard drive, so it can not be extracted and used) For purchases, simultaneously you will send a receipt directly to the buyer (since you got their email address as part of the purchase request), this receipt would ALSO include the download URL, in case something went wrong. this URL may expire in a set number of days if you wish. Note I require the "Content-Length" http header field on this download. if this is not possible due to some technical reason, then you must include the size of the download within the meta data of the "Music Store.xml" file.		upon successful processing of the credit card / bulk purchase (credit) code / subscription / account ID (which is handled by your site), the result URL sent back to me is the actual download link for the purchased song. (for streaming Audio+CDG files, i will encrypt the download as it lands on the hard drive, so it can not be extracted and used) For purchases, simultaneously you will send a receipt directly to the buyer (since you got their email address as part of the purchase request), this receipt would ALSO include the download URL, in case something went wrong. this URL may expire in a set number of days if you wish. Note I require the "Content-Length" http header field on this download. if this is not possible due to some technical reason, then you must include the size of the download within the meta data of the "Music Store.xml" file.

	also, you will keep a record of each song that the user has bought, and upon a special request (keyed from their "subscription / account / user ID", you will provide an XML list of said previously purchased song IDs~~, and~~ if the user re-downloads a previously purchased song, it will not be charged again.		required: also, you will keep a record of each song that the user has bought, and upon a special request (keyed from their "subscription / account / user ID", you will provide an XML list of said previously purchased song IDs. also required: if the user re-downloads any previously purchased song, it will not be charged again.

	you price the songs and/or subscriptions however you wish, and for each song/subscription sold i would simply get an affiliate commission, eg: 30% seems standard, but we can discuss that. you may paypal me quarterly. if you use FreshBooks (and have a paypal business account, and keep a paypal balance) then the "paypal fee" is only 50¢ instead of 3%!		you price the songs and/or subscriptions however you wish, and for each song/subscription sold i would simply get an affiliate commission, eg: 30% seems standard, but we can discuss that. you may paypal me quarterly. if you use FreshBooks (and have a paypal business account, and keep a paypal balance) then the "paypal fee" is only 50¢ instead of 3%! PLEASE do this, it makes things much easier on my end to invoice you.

	i think you'd also want a download link for kJams on your website. users can use the free version to get to your music store. the ONLY limits on the free version is they can't make a playlist with more than 3 songs, can't export more than 10 songs to iPod, and can't rip from CD more than the first 2 songs on any disc. other than that it is fully functional. Note the "playlist size limit" does not affect the actual "Library" playlist, they can add as many songs as they want to that, nor does it affect the size of the music stores. i've got more than 20,000 kJams users that are using the free version (unregistered), i've purposely made it very useful and functional even when used in "Tryout" mode.		i think you'd also want a download link for kJams on your website. users can use the free version to get to your music store. the ONLY limits on the free version is they can't make a playlist with more than 3 songs, can't export more than 10 songs to iPod, and can't rip from CD more than the first 2 songs on any disc. other than that it is fully functional. Note the "playlist size limit" does not affect the actual "Library" playlist, they can add as many songs as they want to that, nor does it affect the size of the music stores. i've got more than 20,000 kJams users that are using the free version (unregistered), i've purposely made it very useful and functional even when used in "Tryout" mode.

	the ~~Tricerasoft, KaraokeLocker~~ and KaraokeCloud (streaming) stores are functioning now. go ahead and download kJams and give it a try, in your 1 click settings, enter 4111111111111111 as your credit card number, make up the rest except do '''use your real email address'''. and you'll be able to test the store (you'll always get a bon jovi song) so you can see just how dead simple it makes purchasing songs. it's impulse purchase at it's finest.		the Karaoke.Net and KaraokeCloud (streaming) stores are functioning now. go ahead and download kJams and give it a try, in your 1 click settings, enter 4111111111111111 as your credit card number, make up the rest except do '''use your real email address'''. and you'll be able to test the store (you'll always get a bon jovi song) so you can see just how dead simple it makes purchasing songs. it's impulse purchase at it's finest.

	==Summary==		==Summary==

← Older revision		Revision as of 22:54, 20 October 2015
Line 24:		Line 24:
	it's important that each song have a "date added" field. users will sort by "date added" to see the new additions when they get a new copy of your library index.		it's important that each song have a "date added" field. users will sort by "date added" to see the new additions when they get a new copy of your library index.

	~~it's~~ important you have a web site where the buyer can see / hear preview samples of your songs (typically 30 seconds or so). Each song should be at a unique url. The previews do NOT play within kJams, but are played directly on your web site. alternately: we can arrange for the ability for kjams to download just part of the song so that it can be auditioned right inside kJams. kJams would handle encrypting the song so that only a portion could be played, even if the whole song is temporarily downloaded (this is more like streaming, as the "download" would immediately expire and not be playable later)		allowing the user to audition (play a sample of) the song is important. in one method, you have a web site where the buyer can see / hear preview samples of your songs (typically 30 seconds or so). Each song should be at a unique url. The previews do NOT play within kJams, but are played directly on your web site. alternately: we can arrange for the ability for kjams to download just part of the song so that it can be auditioned right inside kJams. kJams would handle encrypting the song so that only a portion could be played, even if the whole song is temporarily downloaded (this is more like streaming, as the "download" would immediately expire and not be playable later)

	The meta data xml file is published to a known URL at your site, optionally zipped for download speed. My software, periodically, checks this for updates. if it is newer than last time (ie: the "Last-Modified" header HTTP header is changed) then i re-download, parse, and display the newly updated store list.		The meta data xml/json file is published to a known URL at your site, optionally zipped for download speed. My software, periodically, checks this for updates. if it is newer than last time (ie: the "Last-Modified" header HTTP header is changed) then i re-download, parse, and display the newly updated store list.

	the user can then search and filter your song store from within kJams.		the user can then search and filter your song store from within kJams.

	For stream subscription customers, they purchase a streaming subscription on your web store (or provide HTTP API for it and i'll put a GUI on it), and receive a "subscription ID". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, what tier (if any), when it expires.		For stream subscription customers, they purchase a streaming subscription on your web store (or you provide HTTP API for it and i'll put a GUI on it within kJams), and receive a "subscription ID" or "customer ID". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, what tier (if any), when it expires, how much credit they have, etc.

	Optional: For bulk purchase code customers, they purchase bulk credits from you on your web site (or again you provide an HTTP API) and receive a "bulk purchase (credit) code". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, how many credits are left. If you are totally awesome, you can use the same ID for bulk credit AND subscriptions.		Optional: For bulk purchase code customers, they purchase bulk credits from you on your web site (or again you provide an HTTP API) and receive a "bulk purchase (credit) code". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, how many credits are left. If you are totally awesome, you can use the same ID for bulk credit AND subscriptions.
Line 39:		Line 39:

	When the user streams a song, or if you keep the user's credit card details in their account, i send an HTTPS request url to your server in this form:		When the user streams a song, or if you keep the user's credit card details in their account, i send an HTTPS request url to your server in this form:
	4) "subscription/account ID" credentials plus song ID		3) "subscription/account ID" credentials plus song ID

	for 1) i send, within the URL, the user's (buyer's) name, address, email, credit card, my affiliate ID, and song ID, and whatever else you'd require		for 1) i send, within the URL, the user's (buyer's) name, address, email, credit card, my affiliate ID, and song ID, and whatever else you'd require
Line 46:		Line 46:
	upon successful processing of the credit card / bulk purchase (credit) code / subscription / account ID (which is handled by your site), the result URL sent back to me is the actual download link for the purchased song. (for streaming Audio+CDG files, i will encrypt the download as it lands on the hard drive, so it can not be extracted and used) For purchases, simultaneously you will send a receipt directly to the buyer (since you got their email address as part of the purchase request), this receipt would ALSO include the download URL, in case something went wrong. this URL may expire in a set number of days if you wish. Note I require the "Content-Length" http header field on this download. if this is not possible due to some technical reason, then you must include the size of the download within the meta data of the "Music Store.xml" file.		upon successful processing of the credit card / bulk purchase (credit) code / subscription / account ID (which is handled by your site), the result URL sent back to me is the actual download link for the purchased song. (for streaming Audio+CDG files, i will encrypt the download as it lands on the hard drive, so it can not be extracted and used) For purchases, simultaneously you will send a receipt directly to the buyer (since you got their email address as part of the purchase request), this receipt would ALSO include the download URL, in case something went wrong. this URL may expire in a set number of days if you wish. Note I require the "Content-Length" http header field on this download. if this is not possible due to some technical reason, then you must include the size of the download within the meta data of the "Music Store.xml" file.

	also, you will keep a record of each song that the user has bought, and upon a special request (keyed from their "~~credit card /~~ subscription / account ID", you will provide an XML list of said previously purchased song IDs, and if the user re-downloads a previously purchased song, it will not be charged again.		also, you will keep a record of each song that the user has bought, and upon a special request (keyed from their "subscription / account / user ID", you will provide an XML list of said previously purchased song IDs, and if the user re-downloads a previously purchased song, it will not be charged again.

	you price the songs and/or subscriptions however you wish, and for each song/subscription sold i would simply get an affiliate commission, eg: 30% seems standard, but we can discuss that. you may paypal me quarterly. if you use FreshBooks (and have a paypal business account, and keep a paypal balance) then the "paypal fee" is only 50¢ instead of 3%!		you price the songs and/or subscriptions however you wish, and for each song/subscription sold i would simply get an affiliate commission, eg: 30% seems standard, but we can discuss that. you may paypal me quarterly. if you use FreshBooks (and have a paypal business account, and keep a paypal balance) then the "paypal fee" is only 50¢ instead of 3%!
Line 52:		Line 52:
	i think you'd also want a download link for kJams on your website. users can use the free version to get to your music store. the ONLY limits on the free version is they can't make a playlist with more than 3 songs, can't export more than 10 songs to iPod, and can't rip from CD more than the first 2 songs on any disc. other than that it is fully functional. Note the "playlist size limit" does not affect the actual "Library" playlist, they can add as many songs as they want to that, nor does it affect the size of the music stores. i've got more than 20,000 kJams users that are using the free version (unregistered), i've purposely made it very useful and functional even when used in "Tryout" mode.		i think you'd also want a download link for kJams on your website. users can use the free version to get to your music store. the ONLY limits on the free version is they can't make a playlist with more than 3 songs, can't export more than 10 songs to iPod, and can't rip from CD more than the first 2 songs on any disc. other than that it is fully functional. Note the "playlist size limit" does not affect the actual "Library" playlist, they can add as many songs as they want to that, nor does it affect the size of the music stores. i've got more than 20,000 kJams users that are using the free version (unregistered), i've purposely made it very useful and functional even when used in "Tryout" mode.

	the Tricerasoft, KaraokeLocker and ~~Chartbuster~~ (streaming) stores are functioning now. go ahead and download kJams and give it a try, in your 1 click settings, enter 4111111111111111 as your credit card number, make up the rest except do '''use your real email address'''. and you'll be able to test the store (you'll always get a bon jovi song) so you can see just how dead simple it makes purchasing songs. it's impulse purchase at it's finest.		the Tricerasoft, KaraokeLocker and KaraokeCloud (streaming) stores are functioning now. go ahead and download kJams and give it a try, in your 1 click settings, enter 4111111111111111 as your credit card number, make up the rest except do '''use your real email address'''. and you'll be able to test the store (you'll always get a bon jovi song) so you can see just how dead simple it makes purchasing songs. it's impulse purchase at it's finest.

	==Summary==		==Summary==

← Older revision		Revision as of 04:30, 17 September 2014
Line 24:		Line 24:
	it's important that each song have a "date added" field. users will sort by "date added" to see the new additions when they get a new copy of your library index.		it's important that each song have a "date added" field. users will sort by "date added" to see the new additions when they get a new copy of your library index.

	it's important you have a web site where the buyer can see / hear preview samples of your songs (typically 30 seconds or so). Each song should be at a unique url. The previews do NOT play within kJams, but are played directly on your web site~~<br>~~		it's important you have a web site where the buyer can see / hear preview samples of your songs (typically 30 seconds or so). Each song should be at a unique url. The previews do NOT play within kJams, but are played directly on your web site. alternately: we can arrange for the ability for kjams to download just part of the song so that it can be auditioned right inside kJams. kJams would handle encrypting the song so that only a portion could be played, even if the whole song is temporarily downloaded (this is more like streaming, as the "download" would immediately expire and not be playable later)

	The meta data xml file is published to a known URL at your site, optionally zipped for download speed. My software, periodically, checks this ~~file~~ for updates. if it is newer than last time (ie: the "Last-Modified" header HTTP header is changed) then i re-download, parse, and display the newly updated store list.		The meta data xml file is published to a known URL at your site, optionally zipped for download speed. My software, periodically, checks this for updates. if it is newer than last time (ie: the "Last-Modified" header HTTP header is changed) then i re-download, parse, and display the newly updated store list.

	the user can then search and filter your song store from within kJams.		the user can then search and filter your song store from within kJams.
Line 32:		Line 32:
	For stream subscription customers, they purchase a streaming subscription on your web store (or provide HTTP API for it and i'll put a GUI on it), and receive a "subscription ID". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, what tier (if any), when it expires.		For stream subscription customers, they purchase a streaming subscription on your web store (or provide HTTP API for it and i'll put a GUI on it), and receive a "subscription ID". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, what tier (if any), when it expires.

	For bulk purchase code customers, they purchase bulk credits from you on your web site (or again you provide an HTTP API) and receive a "bulk purchase (credit) code". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, how many credits are left. If you are totally awesome, you can use the same ID for bulk credit AND subscriptions.		Optional: For bulk purchase code customers, they purchase bulk credits from you on your web site (or again you provide an HTTP API) and receive a "bulk purchase (credit) code". You will provide an API such that kJams can send the ID to your server and get back an XML that lists it's attributes such as: whether the ID is valid, how many credits are left. If you are totally awesome, you can use the same ID for bulk credit AND subscriptions.

	when the user clicks the buy song button, i send an HTTPS request url to your server in one of 2 forms:		when the user clicks the buy song button, i send an HTTPS request url to your server in one of 3 forms:
	1) full credit card credentials of the user plus the song ID		1) full credit card credentials of the user plus the song ID
	2) "bulk purchase (credit) code" credentials plus song ID		2) "bulk purchase (credit) code" credentials plus song ID

	~~when~~ the user streams a song, i send an HTTPS request url to your server in this form:		When the user streams a song, or if you keep the user's credit card details in their account, i send an HTTPS request url to your server in this form:
	3) "subscription ID" credentials plus song ID		4) "subscription/account ID" credentials plus song ID

	for 1) i send, within the URL, the user's (buyer's) name, address, email, credit card, my affiliate ID, and song ID, and whatever else you'd require		for 1) i send, within the URL, the user's (buyer's) name, address, email, credit card, my affiliate ID, and song ID, and whatever else you'd require
	for 2 and 3) i send, within the URL, the code (credit or subscription), my affiliate ID, and song ID, and whatever else you'd require		for 2 and 3) i send, within the URL, the code (credit or subscription/account), my affiliate ID, and song ID, and whatever else you'd require

	upon successful processing of the credit card / bulk purchase (credit) code / subscription ID (which is handled by your site), the result URL sent back to me is the actual download link for the purchased song. (for streaming Audio+CDG files, i will encrypt the download as it lands on the hard drive, so it can not be extracted and used) For purchases, simultaneously you will send a receipt to the buyer (since you got their email address as part of the purchase request), this receipt would ALSO include the download URL, in case something went wrong. this URL may expire in a set number of days if you wish. Note I require the "Content-Length" http header field on this download. if this is not possible due to some technical reason, then you must include the size of the download within the meta data of the "Music Store.xml" file.		upon successful processing of the credit card / bulk purchase (credit) code / subscription / account ID (which is handled by your site), the result URL sent back to me is the actual download link for the purchased song. (for streaming Audio+CDG files, i will encrypt the download as it lands on the hard drive, so it can not be extracted and used) For purchases, simultaneously you will send a receipt directly to the buyer (since you got their email address as part of the purchase request), this receipt would ALSO include the download URL, in case something went wrong. this URL may expire in a set number of days if you wish. Note I require the "Content-Length" http header field on this download. if this is not possible due to some technical reason, then you must include the size of the download within the meta data of the "Music Store.xml" file.

	you ~~price~~ the ~~songs~~ and/~~or subscriptions however~~ you ~~wish~~, and ~~for each~~ song~~/subscription sold i would simply get an affiliate commission, eg: 15% to %25~~, ~~we can discuss that. you may cut checks whenever~~ it ~~is fiscally reasonable to do so (eg: when i make more than say $100 or something, or just quarterly or bi-anually or whatever) or just use paypal to pay me (preferred)~~.		also, you will keep a record of each song that the user has bought, and upon a special request (keyed from their "credit card / subscription / account ID", you will provide an XML list of said previously purchased song IDs, and if the user re-downloads a previously purchased song, it will not be charged again.

	i think you'd also want a download link for kJams on your website. users can use the free version to get to your music store. the ONLY ~~limit~~ on the free version is they can't make a playlist with more than 3 songs, can't export more than 10 songs to iPod, and can't rip from CD more than the first 2 songs on any disc. other than that it is fully functional. Note the "~~playlst~~ size limit" does not affect the actual "Library" playlist, they can add as many songs as they want to that, nor does it affect the size of the music stores. i've got more than 20,000 kJams users that are using the free version (unregistered), i've purposely made it very useful and functional even when used in "Tryout" mode.		you price the songs and/or subscriptions however you wish, and for each song/subscription sold i would simply get an affiliate commission, eg: 30% seems standard, but we can discuss that. you may paypal me quarterly. if you use FreshBooks (and have a paypal business account, and keep a paypal balance) then the "paypal fee" is only 50¢ instead of 3%!

			i think you'd also want a download link for kJams on your website. users can use the free version to get to your music store. the ONLY limits on the free version is they can't make a playlist with more than 3 songs, can't export more than 10 songs to iPod, and can't rip from CD more than the first 2 songs on any disc. other than that it is fully functional. Note the "playlist size limit" does not affect the actual "Library" playlist, they can add as many songs as they want to that, nor does it affect the size of the music stores. i've got more than 20,000 kJams users that are using the free version (unregistered), i've purposely made it very useful and functional even when used in "Tryout" mode.

	the Tricerasoft, KaraokeLocker and Chartbuster (streaming) stores are functioning now. go ahead and download kJams and give it a try, in your 1 click settings, enter 4111111111111111 as your credit card number, make up the rest except do '''use your real email address'''. and you'll be able to test the store (you'll always get a bon jovi song) so you can see just how dead simple it makes purchasing songs. it's impulse purchase at it's finest.		the Tricerasoft, KaraokeLocker and Chartbuster (streaming) stores are functioning now. go ahead and download kJams and give it a try, in your 1 click settings, enter 4111111111111111 as your credit card number, make up the rest except do '''use your real email address'''. and you'll be able to test the store (you'll always get a bon jovi song) so you can see just how dead simple it makes purchasing songs. it's impulse purchase at it's finest.