Welcome to LOSCOPe: Life Cycle of Scores in Opera Productions
This project is a documentation of information transfer between tasks and stages in an opera production regarding musical notation. The flow shown here is based on data collected from interviewing and observing opera professionals at the Deutsche Oper Berlin. LOSCOPe is meant to help understand the complexity of the opera production process and to help identify potential areas for software and hardware improvements.
How to read LOSCOPe
Each node can be a Trade, a Task, a Challenge, a Solution, or a Document State.
The Inspector on the left side gives you information about the node you clicked.
You can also choose from a list of nodes of the same category to be highlighted in the flow diagram.
Document States are paired within their respective Task as Document Transformations: State Before Task → State After Task. This means the goal of the task is to change the state of a document. A Task may result in different transformations.
Use the Filter Button in the upper right corner to filter for Trades, Tasks and to show all connections between the tasks.
Incoming Document State: The path from the previous task which matches the "after" state with the "before" state of the given task.
Outgoing Document State: The path to the next task which has the current "after" state as a receiving state. The connection is only shown, if the target trade is listed as "Reference Trade" in the data.
On the bottom right side, you can find hints to the meaning of the nodes and also return to this help page.