Rachel posted such an interesting comment on her experience of using Office2.0 technologies at the recent Society of Archivist’s conference that I thought it deserved picking up in a separate posting.
Rachel is absolutely right in pointing to how reliant the ‘dream’ of Office2.0 is on the nuts and bolts of technical infrastructure and quite correct that at the moment that infrastructure is not yet sufficiently developed to turn the dream into a reality. However, I suspect the phrase ‘not yet’ is really key here. In response to Rachel’s experiences I think I would offer the following points (aside from a hearty ‘well done’ for the whole experiment!).
The infrastructure is still developing, but developing fast. I know (from bitter experience!) that relying on wifi access for internet access when on the road can still be a very patchy and frustrating experience. But, what I would say is cast your mind back 5 years or so and then compare it with today. Five years ago I couldn’t even get a mainline broadband connection for my rural home. Today, not only do I get a reasonable BB connection, but I actually first read Rachel’s comments on my Blackberry whilst walking the dog round a field this morning…
Similar evidence of progress can be seen around the country, whether it be wifi hotspots in stations and coffee shops or the increasing number of hotels that are now offering connections (including an increasing number providing free access). Of course this isn’t the same as being universal and I suspect that it will be some time – perhaps another 5 years or so – before coverage begins to approach this. But I find it hard to believe that it won’t happen soon – just look at the rise in mobile phone coverage over the past decade.
Incidentally, Rachel may have had more luck with a 3G card than she suspected. I’ve used one for several years now and though not without their own frustrations, do mean that access to the internet is possible pretty much anywhere you can get a mobile signal (at least at GPRS speeds, if not 3G).
It might also be worth checking out the potential of Google’s Gears. I’ve not yet got round to trying it myself, but the logic of a piece of software which enables offline access to services which are normally only available online (including Google Docs and Zoho) would seem a potentially valuable means of plugging this temporary gap as seamlessly as possible.
So, I guess in summary its worth saying that this blog is called ‘futurewatch’ for reason! The reality of the universal, seamless access to the web that is required to fully realise Office2.0 may still be a little way off, but personally I still have no doubts that it is the direction in which we are heading.
The world is changing fast. Changes in technology are having a profound effect on the role of records management. The purpose of this blog is to give records managers and others interested in this area a 'heads up' as to what these changes might mean and how the profession needs to adapt to keep pace and maintain its relevance in the years ahead.
Monday, 1 September 2008
Wednesday, 27 August 2008
How not to panic when you lose your laptop...
There was an interesting post (now sadly removed) from a delegate at the Office2.0 conference which flew in the face of the current convention: a man who fears that he has lost he his laptop but loses no sleep about the data he might have lost. Okay, so losing something as valuable as a portable computer would have been no laughing matter and then there is all the hassle with filling out insurance forms, sourcing a new machine etc, but (and here is the crucial difference) no panic about the data that’s been lost with it. No fear about personal information falling into the wrong hands. No paranoia about identify theft.
The difference? This owner of this particular laptop relies on his laptop for little more than access to the internet. No data is stored on it (and in all likelihood virtually no applications either). He is a proponent of Office2.0 technology and as a result his data is all stored on secure, backed-up, safely housed, hulking great servers that can’t get left in the back of a taxi or dropped down the back of a pub sofa.
Okay, so I no it is not as black and white as that and there are plenty of potential risks to data security posed by reliance on external service providers and wireless internet connections – but all the same, perhaps in the current climate there is something to be said for moving back to a situation where the client machine is little more than a dumb terminal, devoid of stored data and therefore devoid of risk and of value to a third party. A move which Office 2.0 is perfectly placed to enable. It lets your staff wander around the country with laptops, it lets them work wherever they need and it lets them have access to the data they require - it just doesn't let them take it with them, with all the attendant risks this seems to bring...
The difference? This owner of this particular laptop relies on his laptop for little more than access to the internet. No data is stored on it (and in all likelihood virtually no applications either). He is a proponent of Office2.0 technology and as a result his data is all stored on secure, backed-up, safely housed, hulking great servers that can’t get left in the back of a taxi or dropped down the back of a pub sofa.
Okay, so I no it is not as black and white as that and there are plenty of potential risks to data security posed by reliance on external service providers and wireless internet connections – but all the same, perhaps in the current climate there is something to be said for moving back to a situation where the client machine is little more than a dumb terminal, devoid of stored data and therefore devoid of risk and of value to a third party. A move which Office 2.0 is perfectly placed to enable. It lets your staff wander around the country with laptops, it lets them work wherever they need and it lets them have access to the data they require - it just doesn't let them take it with them, with all the attendant risks this seems to bring...
Monday, 11 August 2008
Records Management as part of Staff Development?
We held our first online workshop on the new Records Management 2.0 social networking site last Friday on the topic of ‘what does RM have to offer the information literate user? Though the number of participants was quite low, the debate was lively and certainly interesting enough to justify arranging another scheduled workshop on another topic in the near future.
One of the thoughts which the discussion prompted in my own mind was the potential value of the RM function actually forming part of the ‘staff development’ (or similar) unit within an organisation – usually to be found as part of the Human Resources function. As we all know, the records management team - or individual records manager - can currently be found in a wide variety of places within the organisational structure (IT, information services, legal/compliance, facilities management, Chief Execs office etc) but rarely, if ever, within HR.
At first glance they might seem unlikely bedfellows, especially given the great stress placed on RM as part of legal compliance in recent years. But my fear is (as expressed during the discussion) that we, as a profession, are currently seen by many individual users as being too bureaucratic, heavy-handed and ‘dictatorial’ and therefore as part of ‘the problem’; rather than as an ally, someone with practical answers to real problems and someone who understands and sympathises with their needs. I know many of us strive to take as many steps in this direction as we possibly can, but perhaps by so often being inextricably linked to the policy and management functions of the organisation we make this task far harder to achieve than it would be if we were seen to be on the side of the users. After all, at the end of the day it is their actions – rather than policy frameworks and central diktats – which have the greatest impact on how our records are managed. To a great extent this has always been the case, but is a trend which continues to increase the more technology continues to empower the individual user.
There is often a lot of talk about the records manager making use of the ‘carrot’ as well as ‘stick’ but my suspicion is that this is usually more along the lines of "this new process/system/policy that I am about to force you to use is actually great because…", rather than "what could we do to help make your life easier?".
One of the thoughts which the discussion prompted in my own mind was the potential value of the RM function actually forming part of the ‘staff development’ (or similar) unit within an organisation – usually to be found as part of the Human Resources function. As we all know, the records management team - or individual records manager - can currently be found in a wide variety of places within the organisational structure (IT, information services, legal/compliance, facilities management, Chief Execs office etc) but rarely, if ever, within HR.
At first glance they might seem unlikely bedfellows, especially given the great stress placed on RM as part of legal compliance in recent years. But my fear is (as expressed during the discussion) that we, as a profession, are currently seen by many individual users as being too bureaucratic, heavy-handed and ‘dictatorial’ and therefore as part of ‘the problem’; rather than as an ally, someone with practical answers to real problems and someone who understands and sympathises with their needs. I know many of us strive to take as many steps in this direction as we possibly can, but perhaps by so often being inextricably linked to the policy and management functions of the organisation we make this task far harder to achieve than it would be if we were seen to be on the side of the users. After all, at the end of the day it is their actions – rather than policy frameworks and central diktats – which have the greatest impact on how our records are managed. To a great extent this has always been the case, but is a trend which continues to increase the more technology continues to empower the individual user.
There is often a lot of talk about the records manager making use of the ‘carrot’ as well as ‘stick’ but my suspicion is that this is usually more along the lines of "this new process/system/policy that I am about to force you to use is actually great because…", rather than "what could we do to help make your life easier?".
Tuesday, 5 August 2008
An admirable summary of Managing the Crowd
I am indebted to James Lappin at TFPL for posting as succinct a summary of the main points contained within Managing the Crowd as you are ever likely to find.
In fact, it makes me wonder what I wasted the other 60,000-odd words on...
In fact, it makes me wonder what I wasted the other 60,000-odd words on...
Friday, 1 August 2008
Launch of the Records Management 2.0 social networking site
Some of you may recall from previous postings that I have been keen to try to conitnue discussion and debate about the future of records management and in particular with regards to its role in the 'Web 2.0 world'; and hopefully to find ways of enabling those with an interest in this area to work together to create practical solutions.
After investigating a few different approaches I settled on creating a social network within Ning, not least because this platform combines the ability to keep in touch with like-minded colleagues with useful tools including online forums and event management. To be honest, I was still thinking through the details of how best to take this foward when a particularly interesting and robust debate about the future of records management on the Records-managment-uk jiscmail list convinced me that now was the right time to run with this (ready or not!). As with any such site, it will succeed or fail depending on the commitment of its members. Initial take up has been brisk, lets hope this burst of enthusiasm is sustained and turned into ongoing collaboration, discussion and progress.
If anyone else would like to join this site, please drop me an email and I will send you an email in return containing the relevant joining instructions.
After investigating a few different approaches I settled on creating a social network within Ning, not least because this platform combines the ability to keep in touch with like-minded colleagues with useful tools including online forums and event management. To be honest, I was still thinking through the details of how best to take this foward when a particularly interesting and robust debate about the future of records management on the Records-managment-uk jiscmail list convinced me that now was the right time to run with this (ready or not!). As with any such site, it will succeed or fail depending on the commitment of its members. Initial take up has been brisk, lets hope this burst of enthusiasm is sustained and turned into ongoing collaboration, discussion and progress.
If anyone else would like to join this site, please drop me an email and I will send you an email in return containing the relevant joining instructions.
Monday, 21 July 2008
Separating management from storage
I’ve recently been mulling over the nature of the relationship between where we store the information we create (the repository) and the rules governing its management – not least because it seems to represent one of the fundamental divides between the approach to records management which I am advocating (RM2.0 for shorthand) and the majority of ECM products on the market.
In the pre-Web 2.0 world there was a division between the applications we used to create information (e.g. MS Word) and the repository we used to store our outputs. We didn’t store our documents in Word, we stored them on our C://, on a separate file server, or even a removable storage device (though the MOD are beginning to wish they hadn’t!). All of which created a separate shared repository available for the storage of unstructured information created by a range of applications. This, in turn, influenced the nature of first EDRMS and latterly ECM technologies, the majority of which included their own separate repository for storage and intrinsically linked it to their management/rules layer.
As noted in Managing the Crowd: "The crucial difference with Web 2.0 services such as You Tube, Flickr, Facebook and the like is that they are content storage repositories as well. They no longer just represent the tools, but also the filing cabinet" which changes things considerably – especially when you consider that the majority of these services may be hosted outside the organisation. In this model there is no shared underpinning repository, nor is it possible to create and rely upon an intrinsic link between the management/rules layer and the repository of content we wish it to control. To my mind, this places those systems which are built upon the assumption of a combined repository and rules layer at a severe disadvantage by closing off the ability to manage information which it does not itself ‘physically’ hold.
One of the reasons for musing over this now was in the wake of an interesting chat I had the other day with some folks from Computer Associates marking the release of their new CA Records Manager product. In contrast to most other ECM products it apparently does not include its own integral repository – it’s a management layer only, managing content in its original native location. Though there are still currently limitations in terms of how widely this management layer can be applied (not yet extending to encompass the externally hosted Web2.0 services mentioned earlier) it seems to me to at least represent a more open-ended solution which at least offers the promise of achieving some of these wider, more demanding goals, further down the line.
In the pre-Web 2.0 world there was a division between the applications we used to create information (e.g. MS Word) and the repository we used to store our outputs. We didn’t store our documents in Word, we stored them on our C://, on a separate file server, or even a removable storage device (though the MOD are beginning to wish they hadn’t!). All of which created a separate shared repository available for the storage of unstructured information created by a range of applications. This, in turn, influenced the nature of first EDRMS and latterly ECM technologies, the majority of which included their own separate repository for storage and intrinsically linked it to their management/rules layer.
As noted in Managing the Crowd: "The crucial difference with Web 2.0 services such as You Tube, Flickr, Facebook and the like is that they are content storage repositories as well. They no longer just represent the tools, but also the filing cabinet" which changes things considerably – especially when you consider that the majority of these services may be hosted outside the organisation. In this model there is no shared underpinning repository, nor is it possible to create and rely upon an intrinsic link between the management/rules layer and the repository of content we wish it to control. To my mind, this places those systems which are built upon the assumption of a combined repository and rules layer at a severe disadvantage by closing off the ability to manage information which it does not itself ‘physically’ hold.
One of the reasons for musing over this now was in the wake of an interesting chat I had the other day with some folks from Computer Associates marking the release of their new CA Records Manager product. In contrast to most other ECM products it apparently does not include its own integral repository – it’s a management layer only, managing content in its original native location. Though there are still currently limitations in terms of how widely this management layer can be applied (not yet extending to encompass the externally hosted Web2.0 services mentioned earlier) it seems to me to at least represent a more open-ended solution which at least offers the promise of achieving some of these wider, more demanding goals, further down the line.
Wednesday, 9 July 2008
The need for dynamic records management
I’ve made the point before that one of the greatest challenges posed by Web 2.0 to records management is the fact that the underpinning focus of control has now shifted significantly from the organisation to the individual (a fact acknowledged by Time magazine two years ago when it made ‘You’ its prestigious ‘Person of the Year’ in recognition of the fact that in the Web 2.0 world ‘You’ control the information age. This trend is, of course, contrary to many of the assumptions on which records management is based which relies upon and extols the virtues of organisation-wide standards, policies and conformity.
In the latest print edition of Information World Review (though curiously not yet on their online version which is still showing last month’s column) David Tebbutt alludes to the same general trend in relation to social networking technologies:
“Forget centralised planning and control. No one can plan these connections, or their value, in advance. Power shifts to the participants who, frankly, deserve it most”.
Though not talking specifically about the RM and governance agenda, its not difficult to see how these same trends apply in this context and point to the need for far more reactive and dynamic approaches to information management which are able to adapt and change ‘on the fly’ .
In the latest print edition of Information World Review (though curiously not yet on their online version which is still showing last month’s column) David Tebbutt alludes to the same general trend in relation to social networking technologies:
“Forget centralised planning and control. No one can plan these connections, or their value, in advance. Power shifts to the participants who, frankly, deserve it most”.
Though not talking specifically about the RM and governance agenda, its not difficult to see how these same trends apply in this context and point to the need for far more reactive and dynamic approaches to information management which are able to adapt and change ‘on the fly’ .
Subscribe to:
Posts (Atom)