Be humble in the language and feedback you give, ask don't tell.
Consider using positive language as opposed to neutral when offering feedback. This is to avoid the negative bias that can occur with neutral language appearing negative.
Offer suggestions on how to improve code e.g. simplification or expanding clarity.
Ensure you give reasons for the changes you are proposing.
This is because a lot of metadata can contain descriptions i.e. series information that while useful is better output in other places.
Therefore for RIS and SchemaOrg better to just write out the ones we find for Abstract types
Purpose
To fix a bug
closes: datacite/datacite#1294
Approach
Add new abstract_description dynamic attribute
Open Questions and Pre-Merge TODOs
N/A
Learning
N/A
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Reviewer, please remember our guidelines: