[Typo3-typo3org] Groupware solution helping instrument

Daniel Hinderink [TYPO3] daniel at typo3.org
Thu May 19 14:48:08 CEST 2005


>> I wanted to get back to this, for a while now:
>> 
>>> But anyway, finaly we do not want to get rid of Exchange, but see the
>>> benefit of a webbased integrated solution with single-signon, so we
>>> combine
>>> both. There still is a LOT of work, and concept grows every day, for sure
>>> faster then development of it ;)
>> 
>> I have been always very reluctant to making any kind of CRM, Groupware or
>> PIM functionality as a webbased app. I just don't think it works for the
>> users. This functionality was often associated with the
>> ProjectManager-Extension, but that is a misconception of how projects work
>> in practice. There the users need full integration with desk-top tools and
>> intranet project hubs are serving a different purpose than primary
>> information and planning.
>> They also expect personal information to be local/client-side, they want
>> to
>> use it when they are offline and they want it to be quicker than even an
>> intranet can be.
> 
> Yes you are right. At least for the standard user. For me web makes sense in
> a few cases:
> - As soon as you have communication between different companies, it's worth
> it, as there is no other alternative.
> - As soon as you have people working on different places, where it might not
> be the most easy way to have VPN ready.
> - And finaly: For any sort of application you deploy in no time ;)

I think the key to sell this to customers is not so much about remote
locations and such, but about monitoring, documentation and auditing of
processes. Such team hubs are great for archiving documents, showing project
plans and status reports. I don't think team hubs are suitable as an
operative tool for the team members, except for archiving and documentation.

That's of course a very good reason to build such an array of functions, it
is just that they should always aim at providing post-factum overview.


>> However, I think a perfect situation would be a server, that deploys
>> functions as portlets, that can be either in the portal on the
>> intranet/webbased, or tied into a rich client Eclipse-style. That would
>> require parts of the data to be replicated on the local box and synched
>> when
>> connected (much like notes), but I am convinced that there is no other way
>> to bridge the gap between the "personal"-requirements of Groupware and the
>> webbased alternative.
> 
> Notes is a very good example for that, especialy because synchronisation
> works VERY well, not like exchange and outlook. Domino server can also offer
> webbased access if you include that in your development as well. We used
> Domino / Notes for some time, and it had some great benefits. But finally we
> found it to be not as comfortable as Exchange/Outlook in some cases. It
> might have been possible to get notes doing those things, but that would
> mean a lot of custom development.
> 
> The drawback in this case again is, that clients would not have access to
> that straight away.

I am not in favour of Notes, it was just an example of a software that does
synching well. I still believe the way to go are rich clients composed of
plugins, such as portlets, that can be online, or client-based.

 
>> After all i have never seen any one use an online calender, let alone a
>> mail-app instead of a local PIM, but only additionally.
> 
> PIM?

Personal Information Manager (Outlook and such)

>> The quicker way, would be to simply use the intranet to display data from
>> a
>> groupwware server like Exchange, but MS already does that with Sharepoint
>> and there is not a chance in beating them in the field of integration.
> 
> Yes, and that does not only mean local mailboxes and subfolders, but also
> public folders and other things like CRM. For an intranet solution this is
> for sure the quicker way. At least until you have web based applications you
> can not easily integrate.
>
>
>> There are some projects going in the first direction, like Haystack from
>> Harvard and also Workplaces by IBM.
>> 
>> Anyway, i wonder which concept will in the end manage to break down the
>> barrier between personal information management and team-organisation.
> 
> There have been a few companies trying to connect workstation based
> applications. One of them is Kubi Software. They have this kubi client,
> which can be set up on top of Outlook and Notes. They communicate with each
> other and they do not belong on a central server like exchange. You can add
> individual workspaces for different projects. Another approach has been
> groove, which seems interesting, but I didn't like it that much. For those
> things, you need special software, licenses etc., which will be a problem if
> you commincate with clients this way.
> 
> For this reason I do not see a different way than web based if you
> communicate between companies. Like an extranet for clients.

It's just not about groupware, that is what I am trying to say. It is about
project documentation.

> Wrong? Other ideas?

I think it's essential to concentrate on DMS-connectivity, the sooner the
better. The other bit worth looking at is creating a client interface to
some TYPO3 extensions (like your blog plans) or using the python bridge of
OO, or Karstens WebDAV stuff...

>> Another interesting attempt, would be to build an SyncML-Server into such
>> a
>> T3-based hub, here is something to play with:
>> http://nicolas.bougues.net/syncml/
>> Horde has a SyncML-PHP class as well.
> 
> That's very limited in it features it seems. This would only be an option
> for local mailboxes, but I might be wrong...

It's interested for synching calendar data, todos, adresses and such, not
for mails and it's supported by most handhelds, like phones and such.

Cheers

Daniel


> 
> 
> _______________________________________________
> Typo3-team-typo3org mailing list
> Typo3-team-typo3org at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-typo3org

-- 
Vice-Chairman
TYPO3 Association
http://association.typo3.org







More information about the TYPO3-team-typo3org mailing list