Tuesday, September 2, 2008

ATR: What is a Record?

I'm thinking... hard. We had a presentation today on what comes next in the wonderful world of IT and it looks like we may be off to the cloud and this whole Web 2.0 thing. Now I have never been one to chase the buzzword du jour, but I sense a bit of stickiness in the media hype right now.

I've got some ideas about what the new world may look like, but it starts with thinking about records in a slightly different way. The way I see it, a record is fundamentally two things: something that is communicated and something that has a business purpose. ISO 15489 says that a record is "information created, received, and maintained as evidence and information by an organization or person, in pursuance of legal obligations or in the transaction of business". The approach that I'm taking indicates that the record has to be communicated in some fashion, which in my mind implies that it is transmitted to someone or something. So arguably, a "note to self" that is recording by pen on paper and put into a file folder is likely not a record, as such (it may well be evidence, however). And that old bugaboo, the voicemail message, now becomes an object that we're going to have to seriously consider keeping as a record.

So why mess with this definition? Well, in this brave new 2.0 world, we will have to start thinking in terms of objects when we talk about unstructured information. And we will need to think of all these 2.0 tools like blogs and wikis as mechanisms for communications and collaboration for these objects. If you think about it, email is simply a push mechanism for a document that is either the body of the document or attached. A blog is a way to broadcast an object (either passively or actively through RSS feeds). A wiki is a way to collaboratively edit a document. And those are examples with text.

My sense is that, in the fairly near future, a person will create an object for business purposes. Perhaps they have a question about something. They will authenticate themselves and designate the audience for their object (individuals or a group of other authenticated persons). The object will be stored and the audience will be notified that there is an object that they need to review. They will follow a link to a single instance of the object and see how the sender wished to be communicated with in return. Perhaps they want the object edited (a wiki). Perhaps they want a discussion (threaded discussion). Perhaps they have a finished product and want comments around their object (a blog). There are many scenarios. What will be consistent is that the object creator will deliver the object to a repository with information about who should see the object, who *may* see the object, who can edit it, what sort of record it is, and any other attributes or metadata that might be helpful.

Other users will have a browser dashboard that allows them to see a worklist (effectively, what has been pushed to them for information or actual work), a reading list (items that they have subscribed to or placed into ongoing searches, newsfeeds, a calendar, and whatever other widgets make sense for their daily jobs. They'll have something that notifies them of items to follow up on. And we'll have to make some fundamental changes to how we work. When you connect to that object, you'll have to do something. Reading and setting it aside for later will require you to decide when it will resurface for work. The good news (at least in my little fantasyworld) is that once you take an action, that action will be stored in the cloud and Inbox clutter goes away. Search will need to be much more effective.

Perhaps they will have a "presence awareness" window that allows the user to see who is available -- and allows textual, voice or video communications. Perhaps their voicemail will be stored as an object and made available for review.

At the end of the day, the user will need to be much more decisive about what is a record and what sort of record the object is. The user will have to make a few more decisions about what they create and receive. And our "connectedness" will need to be nearly seamless. If everything exists in "the cloud", you have to be able to get there to work.

Records management will need to adapt. We will be in the attribute or metadata business and we will need to work with a lot of other folks to develop processes to authenticate information, ensure security, and ensure disposition. The good news is that we'll have a virtual central file room; the bad news is that the end user will have far more power to decide what to keep and what to throw away. So we'll also have to do more compliance monitoring.

So that's what is in my head tonight, keeping me from my pillow...

OTR: Where Did All the Computer Books Go?

So here's a new feature, "OTR". OTR means "Off the Record", which will be does for topics which have little or nothing to do with records management. Might be opinion, might be a musing... whatever. I've had a few of these along the road, but I'll label them going forward to match my other posts.

I have a reading habit. Actually, I have a book-buying habit. I chain-read. I'll have three to five books started at any given time and often never get around to finishing most of them. I'll glean out some interesting stuff, set the book aside, and pick something else up. I generally will pick up a bit of mind candy (something in the Tom Clancy genre) for trips away from home. I'll see an interesting business book, and give that a run on the airplane. Lately, I've been dabbling in history books -- several on Lincoln and more on Chicago history, even picking up a paper-bound set of Bessie Louise Pierce's History of Chicago.

But I've always been a sucker for computer how to books. Lately, it has been various test-prep and "body of knowledge" books for some certifications that I'm considering in my new areas of responsibility. If nothing else, they point out the competencies that I need to strive for.

Anyway, when I stroll to the back corner where you find the computer books these days (usually hard by the business books), I've noticed fewer and fewer linear feet of computer books. And the ones that are there are looking long in the tooth. You get a smattering of program-specific manuals, plus a few books for various computing languages, a bit of theory, some security stuff, and a couple shelves of general computing books. Ten years ago, they didn't have enough shelf space! Could it be that we're all experts now? Or is do-it-yourself programming a thing of the past? Or are all the answers on the Web?

I'm guessing that the dot com bust has a lot to do with the relative shrinkage here. The demand for people to learn Web-programing and website design from a book has declined. You get trained more formally now.

But it is still amazing.

Back to thinking about cloud computing and this whole "2.0" thing. Steve Bailey's book should be on its way from the UK any day now. More to come.

Sunday, August 17, 2008

Geek or Nerd?

I'm dissatisfied with the traditional definitions of these terms. Heck, Wikipedia wants to merge the two entries... The way I see it, A nerd is someone who has a bunch of specialized knowledge by virtue of concerted effort and study, generally formal education in a particular field. A geek is someone who has similar knowledge, but has gained it out of sheer desire to attain that knowledge, perhaps on the job or through experience. Nerdiness pays the bills; geekiness is what you do for fun. Cliff Clavin is a classic extreme geek in my book, although he often wanders into the world of triviality.

So I'm a nerd about records management and Chicago history, but I am a geek about airplanes, computers, and trains. Ok, elements of my computer knowledge border on nerd-dom, but only in a few small areas.

Funny thing is that I periodically call upon my geekiness to help out my nerdiness. So why do I keep some things classified as "geeky" -- particularly the computer stuff? Well, the way I see it, I know a lot about computers for a records manager and I have some particular areas of knowledge that will spin an IT manager's head around. But when you run up against people who really know computers, you're just a minor geek against their nerdiness. That happens with a fair amount of regularity when talking to two members of my staff. These guys are hardcore. A couple months ago, I showed one of them my home network layout. He then showed me his home network. He runs a series of virtual machines. He has built in hardware firewalls. He has various filters running to keep the bad stuff out. I simply trust Symantec and Linksys. My other staff member will periodically walk me through the finer points of forensic analysis, root kits, and hackerdom. I smile, nod, and play sponge -- there's geekiness to be learned here!

At the end of the day, I have to assimilate all that stuff, apply good judgment to the decisions that I have to make, and hope that I'm properly translating all this stuff to the lawyers. Oh yeah, there's another set of geekiness in my world....

Tuesday, August 12, 2008

ATR: RIM Best Practices

Mimi's been making me think again. She's had any number of posts recently that have provoked some thought on my part. But one recent posting that included her list of "Best Practices" is fodder for this post. Now these being blogs, I'd suggest that these ruminations aren't the end-all and be-all on the matter. But Mimi is pretty solid on hers and I'd like to spend a bit of time on mine.

Here's Mimi's list:
  1. Keep right amount of information for right length of time
  2. Meet all legal requirements
  3. Control costs
  4. Demonstrate good faith through consistent implementation
  5. Protect vital/historical records
  6. Produce information quickly and efficiently
  7. Integrate policies/procedures organization wide
  8. Establish ownership and accountability
  9. Ongoing organization-wide training
  10. Compliance controls: audit against ISO 15489

I like them, but I think that I would generate my list in this fashion:

At a Strategic Level:
  1. Establish senior management program support and appropriate organizational placement.
  2. Drive consistency into all RIM practices.
  3. Ensure global / enterprise-wide program implementation.
  4. Develop policies, not guidelines.
  5. Mandate training.
  6. Require annual compliance.
  7. Audit compliance.
  8. Support legal discovery efforts.
  9. Support data privacy efforts.
  10. Support organizational heritage collections.
At an Operational Level:
  1. Efficiently locate and deliver needed records to requestors.
  2. Associate appropriate information attributes (metadata) to all records.
  3. Ensure that cost savings generates value for the organization.
  4. Minimize end-user impacts.
  5. Develop systems to efficiently disposition records on a regular basis.
  6. Develop systems to ensure preservation of records on legal or tax hold.
  7. Leverage imaging systems to replace hard copy systems where appropriate and as part of a business process.
  8. Utilize document / content management and email management systems whenever possible.
  9. Continually seek program feedback and incorporate user suggestions for continuous improvement.
  10. Hold vendors accountable through service level agreements with meaningful penalties for non-performance.
I think RIM managers often focus too much on the operational aspects of the profession and not enough on the strategic aspects. I think we often focus on delivering the records to the end user and not on ensuring that all records creators are trained on RIM practices and checked for compliance.

In years past, I had distilled my thoughts about records management to three terms:
  1. Record worthiness: Assurance that the integrity and fidelity of records is maintained, regardless of the media upon which the record is stored.
  2. Records retention: Assurance that records are retained consistently, in accord with applicable governmental laws and regulations.
  3. Records efficiency: Assurance that records are maintained in an efficient and cost-effective manner, while providing timely access to the records by the end users.
I think these can be powerful ways of breaking down what we do, but they do leave unsaid much of the strategic approach to managing records.
Powered By Blogger