ManifoldScholar / manifold

Transforming scholarly publications into living digital works.
http://manifoldapp.org
GNU General Public License v3.0
239 stars 30 forks source link

Ability to turn off annotations on a project #2215

Open krosemichael opened 5 years ago

krosemichael commented 5 years ago

Feature Description

A faculty member at the graduate center filled this request out and asked me to post it on her behalf.

It would be great if administrators were able to offer more granular options on annotation, commenting feature e.g. be able to turn off global commenting/ annotation, but retain private functionality.

Why is this feature important? Who does it help?

For editors with essay collections, not all authors might be open or consent to their work receiving feedback or being interacted with in this way. It would allow more essay collections, particularly scholarly in nature, to be included on Manifold if we could respect author boundaries in this way.

For writers/ authors who have been asked to contribute to an essay collection but did not expect this feature to be part of the digital platform and do not wish their work to be interacted with in this way, especially as many professionals feel obligated to respond to annotation, and puts pressure on them to do so even if editor does not mandate it.

For readers who are accessing the text from different points e.g. via a cultural institution, school, other city, public annotation directs their eye level to certain sentences without them being able to explore it for themselves. Does not help reader or writer.

User Stories

Design Notes

Development Notes

zdavis commented 4 years ago

Thank you for taking the time to open this feature request. The Manifold team reviewed this issue during our bi-weekly meeting and the consensus is that this feature makes sense and is in keeping with our overall vision for the platform. Moreover, we see this request as a viable candidate for development under our current available funding. We’re adding an “accepted” label to this request to indicate that it’s within scope and possibly within budget.

The next step is for us to estimate the work involved with this and add it to our feature backlog. Our acceptance of the issue is not a promise that it will be implemented. We will balance this request against the other accepted requests and do our best to implement it within our current available funding.

This was an automated message, but please don't hesitate to reply. Our team watches these issues closely and will respond as soon as we're able to!