You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the creation of mappings it is useful to be able to assign comments. For example, for comments from the WebDewey Deutsch that have led to a mapping decision.
The text was updated successfully, but these errors were encountered:
As far as I can see, this should already be supported by jskos-server because it doesn't restrict the motivation property of annotations. However, there are related issues that could be addressed:
indicate existing comments in mapping table (e.g. with a colored speech bubble)
edit form to add or delete a comment (also to modify?)
A plain comment is not enough nevertheless. What's the typical workflow?
Some comments are additional explanation to a mapping
Some comments are questions or remarks to change, add, improve... something related to the mapping. These comments should be removed after the issue has been resolved.
For the second use case comments are like GitHub issues or word processor edit suggestions, so the workflow is
mapping is commented by person A
comment is deleted ("resolved") by person B
Who should be allowed to delete/resolve comments? Any of:
For the creation of mappings it is useful to be able to assign comments. For example, for comments from the WebDewey Deutsch that have led to a mapping decision.
The text was updated successfully, but these errors were encountered: