Skip to:
Content
Pages
Categories
Search
Top
Bottom

Enterprise Use @Cisco: Automatically bring in events from other systems

  • Hello,

    A couple years back I wrote a little tool for my group that post a Twitter-like stream of activity from my coworkers. Instead of getting my colleagues to log in to a new system and create content, I created a bunch of modules that scraped activity from the ticketing system, the wiki, and a couple of mailing lists, correlated them to users, and sent them in to the system. So, when you look at say, Joe’s profile, it goes something like:

    From opened ticket 37 “How do I post to my blog?”
    Joe responded to ticket 37 “How do I post to my blog?”
    Joe edited the I Like Blogs wiki page.
    Joe resolved ticket 37 “How do I post to my blog?”
    Joe posted to group-announce “Quick advice on how to post to blogs.”
    Sally posted to blog “Blogging is wonderful!”

    So, what I would seek to do with BuddyPress is to create and maintain several users based on LDAP, and create modules (plugins?) which pull data in from other systems and post events to user profiles. Is this approach consistent with the philosophy of BuddyPress or would aggregation be a weird concept?

    From what I can tell from buddypress.org, individual users can enable individual plugins: what I would want is site-wide modules that users could then opt-out of, but if they never even log in, I’d prefer the system make some intelligent reporting as to what they were up to: providing value to other users. Are there any setups already doing this?

    Thank you in advance for any guidance on this issue.

  • The topic ‘Enterprise Use @Cisco: Automatically bring in events from other systems’ is closed to new replies.
Skip to toolbar