I have a dim memory of doing something like this for a client a few years ago. If you look at the contents of the User_Query table (object ‘usq’) you should be able to work out how the scoreboard hangs together.
I don’t have a live example in front of me right now, but for a role-based scoreboard one of the foreign keys in the User_Query table contains the role identifier. Using that and the label field you should be able to work through the ‘parent’ links to identify both your generic node and the nodes that have it as ‘parent’ . With patience and a certain amount of scripting (e.g. using ‘pdm_perl’) I’m sure you can work out how to create a ‘pdm_load’ file that adds the new records to a different role’s tree with the correct ‘parent’ relationships.
Take a backup of the User_Query table with pdm_extract before you start ☺. If it all goes pear-shaped (as my early attempts did) you can take a fresh copy of User_Query, use that in a ‘pdm_load –r’ to delete the whole thing, then re-load your backup copy.
On your second question: to reset an analyst’s scoreboard to the new default, you can delete the User_Query entries that belong to that analyst. Again, the analyst’s UUID will be in one of the foreign keys of the User_Query table. Next time the analyst logs on s/he will see the role scoreboard. That of course will also clear their scoreboard customisations.
Hope that helps!
Regards,
James