A couple of existing tickets and ideas for new features depend on Harmony being able to process relationships between release/recording and artist/label/etc:
We should implement all of these as part of a flexible, structured relationship system.
Each relationship would have a target (ResolvableEntity?), a target type and a rel type at least.
They would be stored as a new property of HarmonyRelease or HarmonyTrack, probably even inside a yet to be defined HarmonyWork representation.
We will display these relationships alongside the text-based HarmonyRelease.credits for the time being.
In the future there might be a way to seed the MB release relationship editor with this data, depending on MBS-13616 (or a potentially a userscript hack).
A couple of existing tickets and ideas for new features depend on Harmony being able to process relationships between release/recording and artist/label/etc:
We should implement all of these as part of a flexible, structured relationship system.
Each relationship would have a target (
ResolvableEntity?), a target type and a rel type at least.They would be stored as a new property of
HarmonyReleaseorHarmonyTrack, probably even inside a yet to be definedHarmonyWorkrepresentation.We will display these relationships alongside the text-based
HarmonyRelease.creditsfor the time being.In the future there might be a way to seed the MB release relationship editor with this data, depending on MBS-13616 (or a potentially a userscript hack).