Oh nice, thanks for sharing.
Generally this makes sense and if we integrate this into Picard we can directly include the label rels in the original request. Currently I don't think this feature has much priority as we are working on larger refactorings for Picard 3, but the feature makes sense. Hence I also suggested a plugin, because this gives an immediate solution. But if someone wants to work on a patch for Picard I'd be happy to have this reviewed and merged.
My suggestion would be to store the broadcast date in metadata as something like "~broadcast_date" (in scripting it would then be available as "%broadcast_date%", as I don't think there is a commonly used tag field for this. But making it available to scripting gives the flexibility to use the field as the user prefers.
Oh nice, thanks for sharing.
Generally this makes sense and if we integrate this into Picard we can directly include the label rels in the original request. Currently I don't think this feature has much priority as we are working on larger refactorings for Picard 3, but the feature makes sense. Hence I also suggested a plugin, because this gives an immediate solution. But if someone wants to work on a patch for Picard I'd be happy to have this reviewed and merged.
My suggestion would be to store the broadcast date in metadata as something like "~broadcast_date" (in scripting it would then be available as "%broadcast_date%", as I don't think there is a commonly used tag field for this. But making it available to scripting gives the flexibility to use the field as the user prefers.