manifold
manifold copied to clipboard
ManifoldScholar
Create an author dashboard the returns project-level analytics
Feature Description
Reveal to backend users project-level analytics along the following lines:
- Number of texts, resources, added to a project over a customizable span of time.
- Which texts are getting annotated/highlighted/shared the most over x time.
- Which resources are getting annotated.
- Which tags people are sorting against the most.
- What the top searches are within a project.
- Average view time for each text or resource over x time.
- User info for those exploring projects and texts in terms of browser, operating system, platform (mobile or desktop) location, etc.
- Tracking referrals of where users are coming from into projects and texts.
These would serve to buoy other surfacing mecahnism already built into the platform (i.e., the Notepad dropdown) as well as features under consideration (e.g., #831).
Why is this feature important? Who does it help?
This gives both authors and publishers quantifiable information about user engagement with their projects to better understand what's working and, for those who are working iteratively, a means to respond to real-world use and adapt in constructive ways to enhance impact and involvment.
User Stories
As a publisher or author I am curious to better understand how, where, and for how long readers are engaging with my projects. Where are they coming from? Are they on mobile or desktop? What are they looking at, and for how long? Did all the engagement (highlights, annotations, sharing) occur all in a short span, or has there been consistent engagement?
Design Notes
We presently have an Activity pane on the backend dashboard that reports basic stats on the instance as a whole by way of Google Analytics. We also have an Activity sidebar nested within projects, but that speaks specifically to the Activity blade on the project homepage and the project-level events (project creation, new texts added, new resource added, and tweets). My sense is that the project-level Activity sidebar should remain as is, and instead we change the instance pane to read as Analytics and then add an Analytics sidebar on the project level.
Development Notes
It is possible that mutiple strategies may be required to serve all this information. Per our Slack discussion, Ahoy and Google Anaytlics seem like worthy starting points.
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!
I feel like we've taken analytics as far as we want to for now. Closing this.