Add comment nodes to more node types

[ecurrano]

New feature: write private notes as you are doing research that would never make it into the public sphere.

The user is responsible for making sure that anything you write in here that should go public also gets entered in the relevant node.

Example: you are working on describing an OTU and have private notes to help you make it through the entire description and the workflow process, but you do not want to share these notes with the public.

[ecurrano]

Claire brought this up at our Senior Personnel issue. Andrew, Dori, and Ellen all think this is a great idea!

[clairecleveland]

@aazaff @NoisyFlowers

Question: If we implement projects vs access groups, could we include a field called Private Notes where appropriate? Set up this field to be like the notes/comments fields that get deleted whenever something goes public. When people click "Change to Public" provide a warning of all aspects of the records that will be lost by going Public. Train folks hard up front on how/when to use those fields.

[aazaff]

This is quite an old issue. I have put the question label on it just because I want to confirm that it still fits with our current design.

[ecurrano]

This issue might pertain to how we implement comments. Write now, we only have Synonym as a comment type, but we do also want users to be able to comment about nodes more generally. Would we allow Comments to be assigned to Groups?

We have notes fields in all of our more complex nodes, and so you can type in whatever you want there and then delete before making the node public. I've been doing this as I've been entering data, and think it is effective.

[aazaff]

Based on Ellen's answer, I have re-classified this issue as a core-feature issue of expanding the number of nodes where comments are allowed. It looks like we did not already have an issue for it specifically.