This is a project to experiment with supporting user comments on Calisphere, by piloting a service on a single collection.
Project overview / goals
Tasks
What? | Who? |
---|---|
Explore and familiarize ourselves more deeply with Disqus features and interface | Sherri, Eric |
Resolve various policy issues:
| Sherri, Eric |
Review terms of service for any other gotchas. See https://help.disqus.com/customer/portal/articles/466260-terms-of-service | Sherri, Brian |
Collaborate on customization options, policies, and other set-up. See https://help.disqus.com/customer/en/portal/articles/1264625-getting-started | Sherri, Eric |
Test it out somewhere (e.g. oac-dev) and start playing around with it. Note: https://help.disqus.com/customer/en/portal/articles/1053796-best-practices-for-staging-development-and-preview-sites. | Brian, Sherri, Eric |
Test the policy documents / project "risks" and maybe a light implementation with an SF community focus group | JJ |
Develop general protocol for moderating comments - how do we anticipate doing this? See https://help.disqus.com/customer/portal/articles/466238
| Sherri, Eric, UCR curators (tech services, etc.) |
Add mechanism on Calisphere side to add javascript to only selected collections, and add Disqus code to Klein when ready | Brian / Mark / Amy |
Begin moderating live comments | Sherri, Eric, UCR curators |
Do a call for participants among the fan community, and perhaps send out a survey or do some quickie UX testing or something? Do they think it’s worthwhile? Is it worth upgrading to Pro? | Sherri, Eric, UCR curators |
Document issues, refine policies, and evaluate the service and its model for production use by all contributors. This should include some preservation planning / exit strategy for the comments generated. | Eric, UCR curators, and CDL implementation team |