Chilling Effects

From SeltzerWiki
Revision as of 22:29, 11 January 2010 by 128.138.64.41 (talk) (Data dump: conversation with Blake)
Jump to navigation Jump to search

Chilling Effects Teamspace

We have some resources for Chilling Effects development. What should we do and how should we prioritize? Please add your ideas to the mix.

  • Nov. 13 -- add ideas over next few weeks. Next steps, circulate among other Chill participants, prioritize, and turn into an RFP/Statement of Work.

Major categories

  • Design
  • Functionality (for public viewers, for admins)
  • Data manipulation


Data dump

Ideas from WS Nov. 12 email:

  1. . current workflow automation -- can we make data entry more efficient and standardize entries better for data analysis?
  2. . interactivity -- where might we make the site more dynamic for users?
  3. . aggregation -- perhaps incorporate news feeds from related sites, including CMLP.
  4. . security -- let's get the admin interface into SSL; make sure entries are being properly sanitized.
  5. . despam -- lots of spam notices lately. can we set up more effective filters without driving away real contributors?

Ideas from Nov. 13 telephone call:

  1. - update the look and feel, give the site a consistent branding:
  2. - -photographic illustration of weather reports would add interest (cf. legalhistoryblog.blogspot.com)
  3. - -possibly replace weather icons with photos of actual storm clouds, sunny weather, etc.?
  4. - make the site more responsive from the admin side, speed repetitive entry
  5. - fix the ordering of questions in drop-downs (WS will change default ordering to by-category)
  6. - create more group FAQs (like 745, 746) to make rapid annotation easier
  7. - a re-editing of the FAQs to eliminate redundancy and consolidate topics would also speed entry
  8. - add a (re)captcha to the notice-entry form
  9. - possible bulk-update feature
  10. - a bulk-delete feature might also be useful for clearly spammy notices
  11. - following a deletion, a link to return to the list of notices to be edited (http://www.chillingeffects.org/admin/notice.cgi) would help (I do this now with a bookmark--I find I don't tend to use the links to the Notice Wizard Interface or the Notice Approval Wizard following a deletion)
  12. - user testing
  13. - make search-by-field more prominent
  14. - add aggregated real-time news, perhaps in place of "related" boxes
  15. - interactive or real-time data-visualizations (think about what type of data might be interesting to watch) ticker, graphs, changing display, Google mapping
  16. - -Might be interesting to track, in a generic way, which principals are sending the most DMCA notices (member of the MPAA vs. RIAA? Does our data tend to reveal the activity of notorious IP trolls like Monster Cable?
  17. - -Maybe offer permalinks to Weather Reports and enable some sharing apps (Twitter, Facebook) to facilitate users passing reports on (cf. www.techdirt.com)
  18. - data manipulation tools, e.g. to standardize "sender" fields


Ideas for which F.U.FAQ's Should be Grouped for Auto-adding (and which are redundant):

- COPYRIGHT: 8, 9, 10 (these are duplicated by 447, 448, 450), 449, 736 (duplicated by 814), 885 (this one doesn't show up on the drop down, but I found it helpful), 262

- TRADEMARK: 51, 52, 53, 56, 255, 262, 344 (when dilution is mentioned)

- DERIVATIVE WORK: Copyright F.U.FAQ's plus 377, 378, 379, 381 (I like this cluster as a series of contrasting examples, but it might be better to write up a single FAQ that addresses the standard for what kinds of works fall under the (c)-owner's exclusive right)

- DEFAMATION: 89 (duplicated by 436), 262, 323, 326, 327, 341, 409, 410

  • Conversation with Blake, 1/11
  1. Chilling Effects front page mock-up: http://images.chillingeffects.org/blake-redesign.jpg
  2. Fit key information on one screen, not below-the-fold
  3. optimize for first-time visitors as well as repeat
  4. CE branding - 50 degrees is too warm!
  5. graphics: clinic logos instead of names (repeated), rss and twitter badges
  6. break the "guide" into help text links where needed
  7. use slugs to identify what "weather reports" and news feeds are. e.g. "Expert commentary from CE contributors", "New from around the web"
  8. indent subtopic menus better
  9. find better breadcrumb indicator
  10. delete / deemphasize "topic maintained by"
  11. Update the likely entry points (esp from Google searches) for first-timers, emphasize the "compare" on int'l pages.

Resources

Our past design choices: https://cyber.law.harvard.edu/team/wiki/Tech:_Design_Resources

as well as developer resources: https://cyber.law.harvard.edu/team/wiki/Tech:_Development_Consulting

Sites whose design we like

  • Ars Technica
  • Techdirt
  • Legal History Blog