I’m not all that fond of the word “curator.” (Keep in mind, though, that for some time I wasn’t all that fond of the word “blog.”) I was fine with the original meaning–a person in charge of things in a museum, zoo, or similar place of collection. I agree it’s a logical extension to use it for someone who chooses items from a collection, or chooses the items that go into a collection.
In the online world, though, there’s a tendency to call anyone who slaps four things together a curator. Sometimes, I think, he’s just a guy letting you look into his virtual junk drawer.
David Kelly looks at this more seriously. He believes anybody in the learning and performance field (or probably any field) can be a curator if they listen, analyze, and share:
I’ve just finished my first year in a new job. One of the things I want to do in the coming year is more deliberate personal knowledge management. Part of that involves collecting information from the networks I’m involve in and sharing that with my colleagues. I know from experience this increases my mindfulness, and the more I seek, the more things I find I have to think about and to share.
My trusty sidekick for sensemaking is Evernote. (I just looked up their home page, and I smiled at the tag line, “the workspace for your life’s work.”) On my own computer, I can use their web clipping widget to add notes, adding my own tags and (if I’m so inclined) sending the new note to a particular notebook (section) in my Evernote collection. I can email things to my Evernote account, and from my phone I can create notes directly (in the Evernote app) or share things from other apps.
All that’s by way of introduction. Some time back I created a “keeper” tag for items I wanted to hang onto, specifically because I might want to share them with people.
What I’m now planning: a series of keeper posts. Rather than fling a bunch of things onto a page here because I have a bunch of things, I’ll go through my most recent keepers and pull out a subset of them. I’ll try to explain what I’ve kept, why I’m keeping it, and (at least implicitly) why I’m sharing it.
That’s what the next post will kick off.