By the way : Collection is "masculin" word in French : You should translate it by "Nouvelle collection" not "Nouveau collection"...
Your idea is quite good: group everything in the same database. Collection could be used to separate the destinations.
The setlist mechanisms should be the same for collections, and it would be necessary to be able to export or save (backup) only one collection. It seems simpler to me to create a "profile." It's the most logical method: at startup, it's a choice. Perhaps with the option of changing along the way, but with more problems.
I think a "Change Profile" menu would really be a good solution. There's little point in mixing scores between profiles.
Currently, in "paper" mode, they are separate folders. Some scores are duplicated, but it's rare for them to remain identical between music groups.
One time your profiles is "Musical director" next time "Player"
Two jobs two profiles
and : PLEASE, IF ONLY ONE PROFILE EXIST : no question, dont add complity for musicians
Your idea is quite good: group everything in the same database. Collection could be used to separate the destinations.
The setlist mechanisms should be the same for collections, and it would be necessary to be able to export or save (backup) only one collection. It seems simpler to me to create a "profile." It's the most logical method: at startup, it's a choice. Perhaps with the option of changing along the way, but with more problems.
I think a "Change Profile" menu would really be a good solution. There's little point in mixing scores between profiles.
Currently, in "paper" mode, they are separate folders. Some scores are duplicated, but it's rare for them to remain identical between music groups.
One time your profiles is "Musical director" next time "Player"
Two jobs two profiles
and : PLEASE, IF ONLY ONE PROFILE EXIST : no question, dont add complity for musicians