Updating a speaker name should update all speakers with that name

[philmcmahon]

Is your feature request related to a problem? Please describe.
Currently, updating a speaker name just updates that block.

Describe the solution you'd like
I'd like it to update every occurence of that speaker name in the document - so every instance of 'Speaker 0' can become 'Hugh Dennis'

Additional context
We're hoping to plug the output of this tool into the frontend of our website at some point, it would be good to avoid people having to do find+place tidy up later. I've had a go at implementing this here without success yet (the UI doesn't update) but thought I'd check in before spending more time on it to find out if this is a feature you'd welcome?

[pietrop]

Thanks @philmcmahon, yes this would be a good feature to add.
@scentless-apprentice was also interested in this.

There's two things/features to consider in this context

1. Is the one you mentioned, of being able to batch change all speakers. You would have to work out
   • if there are any edge cases to be mindful of where you wouldn't want this to happen
   • If it's an option given to the users
   • if it's something that only happens when the user changes the "default" speaker label
2. The other was suggested by @scentless-apprentice, which is when you click on a speaker label, it could also have an autocomplete dropbdown of the speakers that have already been used. (This is also useful for when the speaker identification, is either not present or has failed)

These might either be two separate features, or integrated to be part of the same solution, depending on the approach taken, but thought I'd connect you in the interest of non duplicating work 😄

Had a quick scan through your branch, there's a chance you might need to force a re-render (forceRenderDecorator) let me know if that doesn't work tho.

[bevand10]

My view is that you offer the following initially:

• Capture the name change.
• Then ask the user “You’re about to replace ‘Speaker0’ with ‘Dave Bevan’. Set the dialog buttons to ‘Cancel’, ‘Yes, replace all 27 occurrences’ and ‘Yes, but just this instance.’

If n==1 then you’d only need to prompt ‘Cancel’ & ‘Yes’.

That way you are being clear about the impact of a bulk change.

Thoughts?

[pietrop]

👋 @philmcmahon just following up to see if there was any progress on this? or whether you might have any questions?

[philmcmahon]

Hi @pietrop , thanks for reminding me about this! I got a halfway thing working where it would replace all matching names but ran out of time in our hack week to get a modal working to check if that's what the user wanted to do.

Realisitcally the next time I'll get a chance to work on this is 10/11 June, so if it's needed more urgently here's what I did so far: master...philmcmahon:update-all-speakers - in case it's useful!

[pietrop]

👋 @philmcmahon I am picking this up here #208 but let me know if you had made any progress on this in the meanwhile

[philmcmahon]

Ok great, sorry no I haven't and sorry to drop this!

…

On Mon, 7 Oct 2019 at 15:06, Pietro ***@***.***> wrote: 👋 @philmcmahon <https://github.com/philmcmahon> I am picking this up here #208 <#208> but let me know if you had made any progress on this in the meanwhile — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#141?email_source=notifications&email_token=AA3QQG2LNRUKBZNGXNAUR6LQNM65PA5CNFSM4HET2YB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAQOYOA#issuecomment-539028536>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA3QQG5VQCHEECPBQHOKPRLQNM65PANCNFSM4HET2YBQ> .

[philmcmahon]

On the off chance that it's useful this is what I did - it updates all names by default master...philmcmahon:update-all-speakers

[pietrop]

thanks @philmcmahon 🙌 I've been basing this PR on it #208 and adding the option to cascade the chances to all speakers or just current tone.

Now trying to figure out how to re-render the component after the changes 🤔