search

ManifoldScholar / manifold

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

Allow notifications of annotations and highlights on a chapter-by-chapter basis #2337

Open mkgold opened 5 years ago

mkgold commented 5 years ago

Feature Description

For edited collections, especially, where a publication consists of chapters authored by different authors, it would be ideal if the authors of each chapter had the possibility of being notified whenever someone annotated or highlighted a chapter. Right now, it is only possible to subscribe to notifications for an entire project; in a book like Debates in the Digital Humanities, with over 45 chapters, that means that if authors want to be notified of comments on their chapters, they will also be notified of comments on the other 44 chapters

Why is this feature important? Who does it help?

this would improve conversations in the margins of a text overall, as it would allow authors to more closely monitor comments on their texts. Upon receiving notifications, they could respond, thereby increasing interaction with Manifold texts.

User Stories

A scholar writes a single chapter in a larger collection. This scholar wants to subscribe to notifications only for her chapter, not for others written by other people.

Design Notes

Development Notes

zdavis commented 4 years ago

This could build on the OER work we're doing for CUNY. We would add a setting to notifications that allowed people to be notified when someone commented or annotated something in the user's collection.

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!