Wednesday, August 20, 2008
Subscribe to:
Post Comments (Atom)
skip to main |
skip to sidebar
Archives
-
▼
2008
(44)
-
▼
August
(26)
- Zoho locomotion
- Realio trulio little read Rollyo
- Library Thingamajig
- People people people, and a cat
- TV is dead. Long live TV.
- Opacs are not even fruit
- Ducks without orange
- Orange, orange, against the plying of the slight
- Halftime quater-orange pull over play nice
- Lightning doesn't strike here
- Wetpaint: please touch
- Lolcats beam me up
- Drawing a long cow
- ..........over 2.5 million of them
- If a wookie could wiki
- Behind, before, above, between, below
- Percolating..
- Pushing up Daisy's last post
- On high o'er
- The big O
- Bananas for nana
- What colour are your Olympics?
- Probable podpeople nonperson
- Putting the darkling in knightingale
- Feed me, see more
- You will know when you get there
-
▼
August
(26)
23ThingTags
- #02 blogging (1)
- #03 comments (1)
- #04-5 Flickr (2)
- #06 technology (3)
- #07 RSS (3)
- #08 Delicious (1)
- #09 Technorati (1)
- #10 Library2.0 (6)
- #10 Web2.0 (3)
- #11-12 wiki (6)
- #13 ImageGen (1)
- #14 LibraryThing (1)
- #15 Rollyo (1)
- #16 ZohoWriter (1)
- #17 YahooPipes (1)
- #18 VideoSites (2)
- #19 Podcasts (2)
- #20 ebooks (1)
- #21 MyBook (1)
- #22 SocialNetworks (1)
This blog is best viewed with Firefox. Images are derived from the Commons, gathered on Delicious and subject to Creative Commons licenses. Contact me at unrequestable at gmail.
7 comments:
Love the graphic - you are just too clever it makes me sick!!(in the nicest possible way, as Dame Edna would say)
:) yes
it's fun yet, trust me, not really that complicated - its just cut and paste in photoshop. Even the splats!
but ;)
lets go with the sickening cleverness.
Now.. the rub: what about the real content, the words..
Great possibilities with your idea of one wiki to serve all public libraries - will cut out a lot of duplication. You can then have specific pages for local communities, which can still be accessed by everyone. It will be a wondeful way for people to keep up or add content to community info even if they don't live there anymore. Just think how you then can capture local info that would be otherwise lost.
Yes, indeedy - why not.
Starting from one wiki would avoid later problems of compatible softwares, ways to organiz info, etc..
It's where top-down could really give bottom-up a good kick-start.
Shrug. And if we could just use Wikipedia instead of tilting at it.. well, we could avoid even more duplication and concentrate on laying the groundwork for the unexpected.
Using Wikipedia as a base would have been an ideal way of consolidating your information base, but in practice Wikipedia is too restrictive in its writing style. A one-wiki-for-all will need to accommodate different styles, e.g. anecdotes, how-to articles, how-it-was-done-then articles, comments and even debates. Wikipedia's editors are quite zealous about preserving a encyclopedic style.
Yes, you're right Wikipedia is, in a sense, restrictive - but i prefer words like disciplined, focused.. (and if you want debate try the talk pages:)
Anyway the one-wiki notion was referring to non-wp stuff, like the things you mention. Or whatever it is a public library (system, conglomerate) might uniquely engage in. And how this might be congregated in one bit of software, the advantage being we could accommodate.. our own zealotries..
I use the word 'uniquely' pointedly because.. Are we better off managing a vertical file or should we integrate what we have with Wikipedia? Should we collate reviews or embed LibraryThing into our opac? Do we need to host how-to articles if we can direct people here here here (pick your link)?
Post a Comment