-
internal twitter-like system in Alfresco Share?
Posted on April 28th, 2009 4 commentsI’m an active twitter user since march & and I’m currently working on a Share customization project (intranet knowledge portal).
Now, I’m wondering if it is a nice idea to add sth. like a internal twitter system to Share. Alfresco’s Activity Feed is a nice approach to track each activity, but in a system with more than hundred members of a site this feed gets very chattering. So, my basic idea:
- reuse twitter syntax (@, DM, RT & #)
- # –> automatically tag the message
- twitter user-dashlet (like BeTwittered Google Gadget)
- site-dashlet: last messages of site members
- action link in DocLib, wiki etc. “recommed via twitter”:
- opens dialog to write twitter message
- autocompletion for user names typing @ or DM
- automatically add shortened link to content - decide if each member follows all other site members or reuse twitter-like follow mechanism
- tbc
So…what do you think about this?
4 responses to “internal twitter-like system in Alfresco Share?”
-
Florian April 28th, 2009 at 17:54
Hi Jan,
Optaros has done a part of your idea with their user status dashlet: http://labs.optaros.com/2009/02/19/enterprise-collaboration-alfresco-share-screencast-part-two
They only display one message/status per user though. They planned to release the share components as open source but they don’t seem to be available yet.
I am wondering if one could implement parts of the official twitter api as webscripts and use those as backend. Then you could switch the provider to the official twitter if needed: http://apiwiki.twitter.com/Twitter-API-Documentation
Florian.
-
yub, Jeff points me to his screencast via twitter some hours ago.
-
Our plans (and designs) anticipate filtering options on activities, so a user can tune what they see – usual issue of time & resource to implement
A twitter-like component in Share would be great – especially if it can switch to Twitter as the provider behind the UI as suggested.
Paul.
-
filtering activities sounds nice.
Implementing a twitter-dashlet in Share shouldn’t be a tricky task. But supporting twitter API internally seems to be more complex.
Leave a reply
