Workflow assignment messaging

[srallen]

Gravity Spy has a hardcoded message for when a volunteer is assigned a new workflow:

Right now, this is Gravity Spy specific and is the same message between each 'level'. I'm less certain of the utility to allow projects to customize this message versus us coming up with good generic language and I think specifics on the workflows should rather go into the tutorials and task help. It's possible there may be a good reason I'm not thinking of to allow customization of the message here, though, so I'm opening this issue as as placeholder for this. If so, I'm unsure if we should support a single message (maybe on the project resource?) or a message per workflow.

[camallen]

There are configuration JSON fields on both the Project and the Workflow resources that would suffice for adding a single language string for this use case.

However if the project volunteers require the strings to be presented in translated languages then we will have to add a special field ('promotion_message' perhaps) to an existing resource and ensure that it is set to be a translated field

panoptes/app/models/workflow.rb

Lines 72 to 74 in 28affa5

	def self.translatable_attributes
	%i(display_name strings)
	end

The resources we can support are either

• Workflow (supports more granular messages as progression through the workflows)
• Project (supports on generic message across all workflows)

Once we have the new field we can add it to the list of strings to be translated for that resource. Thus this resource & associated translations are fetched to the client when wiring up the classifier and when a user receives a promotion message while classifying we can show the translated 'promotion' message in the UI.

The above assume there will be only 1 (2 max) messages ('promotion') per resource for translation, if there are more then we can support that but it will be a more complex json structure (similar to workflow tasks) and worth revisiting the ideas here.

[srallen]

I'd prefer to avoid the complexity, so I'd like to first have a strong case made if we should allow customization at all before work begins on this piece.