TagTeam: Difference between revisions

From Berkman Klein Google Summer of Code Wiki
Jump to navigation Jump to search
No edit summary
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=About TagTeam=
TagTeam is a versatile, open-source social-tagging platform and feed aggregator. It's like a supercharged cross between Delicious and Google Reader, specifically designed to support tag-based research projects.  
Please see the [https://github.com/berkmancenter/taghub github repository], which should do a pretty good job articulating what TagTeam does. A live demo is [http://dev7.berkmancenter.org here].


==Loosely Defined Ideas==
TagTeam research projects are called hubs. A hub can support tagging of any online resources. It can subscribe to RSS feeds from any source, including other tagging platforms. It can publish its own RSS feeds, one for each tag, one for any boolean combination of tags, one for each search, and one for any combination of other TagTeam feeds. All records in TagTeam created by tagging or by subscribing to external feeds are stored locally for deduping, back-up, export, modification, and searching. Finally, if they wish, TagTeam hub owners may modify any tags in their hub, retroactively and prospectively, in order make a controlled transition from a folksonomy of user-defined tags to a standard vocabulary or ontology.
* Create more "importers" allowing for tagged item sets to be imported from many sources - Pinterest? Zotero?
* Create a set of bookmarklets and a chrome extension to make feed auto-discovery easier.
* Integrate the [https://github.com/plataformatec/devise Devise] authentication with facebook, twitter, google, etc.
* Leverage the extremely flexible [https://github.com/be9/acl9 acl9 authorization layer] to make TagTeam a truly social system - allowing Hub owners to delegate management of certain parts of their Hub to collaborators. There is a A LOT of room for growth here, in ways we've not conceived of.
* Create a [http://twitterfall.com/ twitterfall-like] frontend for items emitted by TagTeam - or some other slick and useful visualizations.
* Build in automated citation parsing for the bookmarklet.
* Create a sweet web UI for reading feed items - keyboard shortcuts? full screen? font controls? The reading UI has always been a lower priority relative to just getting the technical underpinnings working.


==Strictly Defined Ideas==
More info: http://cyber.law.harvard.edu/hoap/Intro_to_TagTeam, http://tagteam.harvard.edu/
* Improve the json / rss / atom / xml API - specifically around the creation and management of ActiveRecord objects.
* Create a [http://jquerymobile.com/ jQuery mobile app] that uses the improved API to create a super-fast UI for browsing Hubs, remixed feeds, and other parts of the TagTeam data.
* Expose more of the [http://sunspot.github.com/ sunspot-provided] search power through a sweet ajax-y boolean/precedence focused search interface.


==You tell us!==
Github repo: https://github.com/berkmancenter/tagteam/
Imagine you have an app that can aggregate and remix data from disparate sources, including:
* delicious and other social tagging services,
* Wordpress, blogger, tumblr,
* mediawiki,
* twitter
and serve it up in multiple formats after a TagTeam Hub owner has filtered and modified the tags on each item.  You've also got information about changes and tagging frequencies for all the inputs and remixed feeds. What sort of interesting metrics, apps, or visualizations can you think up?


Mentor: [mailto:djcp@cyber.law.harvard.edu djcp@cyber.law.harvard.edu]
=== Ideal candidate criteria ===


General Questions: [mailto:berkmancenterharvard@gmail.com berkmancenterharvard@gmail.com]
TagTeam is interested in candidates with experience in Ruby on Rails, Apache Solr, and Bootstrap 3. For this project, we're looking for a creative programmer to implement new TagTeam features and improve its power and usability. We have a considerable list of high, medium, and low priority enhancements in mind. While we'd naturally like to check off the high-priority features first, we'd encourage our GSoC intern to look at the full list and pick out feature ideas that meet his/her interests, and help give them shape and life, regardless where those ideas stand on our priority list. We'd also encourage our GSoC intern to play with TagTeam and come up with new enhancement ideas, especially ideas that might be implemented in the same summer.  
 
Example sub-projects include:
 
*Fine-tuning the search syntax
*Adding a statistics package on usage data
*Modifying the front end to support user authentication
*Improving TagTeam's speed and stability

Latest revision as of 13:35, 20 February 2015

TagTeam is a versatile, open-source social-tagging platform and feed aggregator. It's like a supercharged cross between Delicious and Google Reader, specifically designed to support tag-based research projects.

TagTeam research projects are called hubs. A hub can support tagging of any online resources. It can subscribe to RSS feeds from any source, including other tagging platforms. It can publish its own RSS feeds, one for each tag, one for any boolean combination of tags, one for each search, and one for any combination of other TagTeam feeds. All records in TagTeam created by tagging or by subscribing to external feeds are stored locally for deduping, back-up, export, modification, and searching. Finally, if they wish, TagTeam hub owners may modify any tags in their hub, retroactively and prospectively, in order make a controlled transition from a folksonomy of user-defined tags to a standard vocabulary or ontology.

More info: http://cyber.law.harvard.edu/hoap/Intro_to_TagTeam, http://tagteam.harvard.edu/

Github repo: https://github.com/berkmancenter/tagteam/

Ideal candidate criteria

TagTeam is interested in candidates with experience in Ruby on Rails, Apache Solr, and Bootstrap 3. For this project, we're looking for a creative programmer to implement new TagTeam features and improve its power and usability. We have a considerable list of high, medium, and low priority enhancements in mind. While we'd naturally like to check off the high-priority features first, we'd encourage our GSoC intern to look at the full list and pick out feature ideas that meet his/her interests, and help give them shape and life, regardless where those ideas stand on our priority list. We'd also encourage our GSoC intern to play with TagTeam and come up with new enhancement ideas, especially ideas that might be implemented in the same summer.

Example sub-projects include:

  • Fine-tuning the search syntax
  • Adding a statistics package on usage data
  • Modifying the front end to support user authentication
  • Improving TagTeam's speed and stability
Retrieved from "http://cyber.harvard.edu/gsoc/?title=TagTeam&oldid=370"