Song Editing from Service Manager
Sort out Bug 772523
Blueprint information
- Status:
- Not started
- Approver:
- Raoul Snyman
- Priority:
- Undefined
- Drafter:
- Tim Bentley
- Direction:
- Needs approval
- Assignee:
- Tim Bentley
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Sprints
Whiteboard
At present Songs can be edited from the Song plugin or the Service Manager if attached to a song.
Current Situation
When a Song is added to the service Manager the service item knows which song the item belongs to and allows then edit to work. This means that the Song database can be edited from the Song plugin and the Service. If a Service is saved when the service is reloaded the song is reattached to the database to allow editing. This is optional.
Missing Features
There is a requirement to add the ability to edit a song in the service and not effect the song in the database.
There is a requirement to allow a service to be loaded and not added to the database AND allow the song to be edited.
Solution
Allow songs to live in the songs database for the duration of a service. These songs would not be visible to the song search.
Add the songs if, the song currently is not to be added to the database or the song has been tagged as temporary.
Changes
Add temporary flag to database and filter searches to bypass if set.
Remove temporary songs on service reset or OpenLP exit.
Allow Songs in service manager to be tagged as temporary copy (new menu item) . This would trigger a temporary clone being generated.
Amend the song load code from the service manager to bypass the searches and create the song but tag as temporary.
Amend Service load code to tell Song Plugin a Song is a temporary copy.
