Scratchpad:Service Songs

Notes regarding interaction of songs in a loaded service file with the song manager.

Suggestions for usage in v2. Open for discussion!


 * If editing a song in the song manager, and that song is also in the current service, update the service version too.
 * If editing a song in the service manager, provide a checkbox to also update the song manager version too. Providing the checkbox will allow someone to make changes to the service song only, that way one off changes can be made, e.g. a different verse order. In V1, editing a song in the service will also always update the song manager
 * When reloading the service, automatically load missing songs into the Song Manager. Do a match on Title and Author. Although not foolproof, anything more sophisticated could cause problems, especially if two separate databases are in use (one at Church and one at Home for example).
 * If a service song matches on Title/Author, but differs elsewhere (e.g. lyrics) then ask the user whether to update the song manager. Perhaps show the songs side by side. Provide "Yes to all" "No to all" options too. V1 always blindly overwrites the song manager with the service song. This can cause problems if loading an old service file, or a service file created from an old database, e.g. at home where corrections haven't been made
 * When saving the service, export the full song XML into the service zip file. This will ensure all required information is present when reloading.