S6. Reviewing others' annotations

[hkir-dev]

Epic:

Description

User: Lead scientist on the same project with scientists from Use Case 1 #98 .
Use Case: Annotations are in good shape for AIT99, and I want to review, comment, or dispute them.
What I have:

• AIT99 in the appropriate format
• TDT installed correctly on my computer (see Use Case 2 S2. Setting up TDT for annotation of AIT99 #99 )

What I need to know:

• Specifically what file do I need to perform this task? Is this the same as for Use Case 3 S3. Annotation of cell sets in AIT99 using TDT #100 ?
• How do I comment on or dispute an existing annotation? How do a approve, or add support for an existing annotation? Support comments on annotations. #113
• (How) can we make these comments private to the team (e.g., for internal review) or public (e.g., to allow public commentary on our cell sets)?

Tasks

• Support review of someone else's annotation cellannotation/cell-annotation-schema#100
• Support comments on annotations. #113
• Task3

[dosumis]

• (How) can we make these comments private to the team (e.g., for internal review) or public (e.g., to allow public commentary on our cell sets)?

Under current plans all comments will be visible to anyone with access. We could potentially add a field that indicates comments should be deleted on public release + programatic support for deleting. As public visibility is outside of the control of TDT (it is controlled via GitHub) deleting would have to be part of some SOP for public release. Alternatively, we could just encourage anyone preparing a release to manually review all comments to decide if they should be deleted or released to the public. Note - in either case, comments will remain in the history (Git forgets nothing unless your do really radical things to rewrite git history - something I strongly recommend against).