From: Adam S. <ad...@pe...> - 2001-09-21 18:08:54
|
> Adam, I'd love to hear your ideas about this. I was planning on making > something to scrape the phonelist off our company intranet and make > homepages for people on my PersonalWiki. ramble alert ... well i hate to say it but i don't really have any good ones either. i have my personal wiki (www.spack.org) where i store bits and it works *brilliantly* for geek related stuff. i can stuff articles in there, technical docs etc. it's way better saving emails or text files cause it's inherantly hypertext and searchable and yet i keep all the advantages of text caue it is text on the server (i don't use a sql backend). but i want to take it to the next step. i want to move my palm pilot contact database to it. my plan had been to stuff everything via ldiff into an ldap server adn then find or write a php web frontend to it, but the idea of being able to manipulate this data via a wiki is great, but contact details are inherantly private and structured, i don't want to put my mom's email or phone number up for anyone so it has to be private and starts to deviate meaningfully (imho) from what wiki is all about. so maybe each user would have a personal data subwiki, where they could clutter up the wiki name space as much as they like. with a bit of tweaking international phone numbers (or email addresses) would make good unique page identifiers, and ldap plugin could fairly trivially grab info from an ldap server, format it, maybe even load it into text boxes so it can be changed in a structured mannor via the wiki. hell, maybe you could even create another export function (like the rss/rdf that we've been talking about) for ldiff for export to a palm pilot or ldap database. even better maybe i can sync "my wiki" (or my section of the wiki) with my palm pilot ... and i'd actually start using it for somethign other then off site backups of my contact database again :) what i'm wrestling with is "what is a wiki" and what is it that i want to keep, and what i'm willing to sacrifice for greater functionality. would there be anything gained by embedding a webmail (say squirrelmail which is what i think phpgroupware uses) in a wiki page called WebMail. you preserve the wiki interface to a certain point but what do you really accomplish other then more overhead? i think the marriage with phpgroupware could be quite valuable but i really like the idea (jeff's?) of being able to maintain the wiki interface to it, so instead of the wiki appearing inside groupware, groupware elements appear inside the wiki. however i have no idea how to structure that so it's *easy* and convenient enough that people will use it that way. ... ramble off ... adam. |