<p>Just want to log this before I forget about it. I realise everyone's busy with the imminent and exciting release of OpenLP 2.0 :-)</p><p>It would be helpful for us to have multiple song databases. The user should be able to import new songs into a given group, delete a whole group of songs, and move songs between groups. Each song only belongs to one group. It doesn't have to be separate database files, although this seems like a relatively straightforward way of doing it, with some added benefits.</p><p>The main use case is when we import a bunch of songs that need tweaking (or substantially correcting) before use. I would like to bulk import these songs into the "untested" group. That would make it clear that they are not to be used without checking them over. When they have been checked they can be moved to the "verified" group, indicating that they can be put up on the screen without risk of embarrassment.</p><p>A related scenario is when I use OpenLP at home. I'm very keen not to introduce duplicates and I certainly don't want to have untested songs in the main database. We share our database via Dropbox. If I'm adding new songs for the next service, I need to put them in the shared song database, but if I'm just testing a new importer, I don't want them to be shared and I want to be able to delete them all if anything goes wrong.</p><p>I never understood why some other church presentation software allowed you to have multiple song libraries, but now I see at least two reasons. First, it increases the safety of the database by making it less likely that someone will accidentally dump junk into it or delete a load of files. Second, it helps organise file imports of different qualities. This is still a major issue for us: there is no way to import all the songs from our previous software (SundayPlus) without checking them all individually to remove duplicates, embarrassing typos, and author info in the wrong places (this is a problem with our files, not with OpenLP).</p>