I do admit that it would be awesome for him to be the 'first e-mailing president', but it sounds like his records management team has suggested to him that this would not be a good idea. Which, fair enough, given how presumably the president has better things to do than check his email obsessively. But I do think that this shows that his staff is up on some of the information problems that could occur in a 21st century presidency, which is more than I can say about the incumbent.For years, like legions of other professionals, Mr. Obama has been all but addicted to his BlackBerry. The device has rarely been far from his side — on most days, it was fastened to his belt — to provide a singular conduit to the outside world as the bubble around him grew tighter and tighter throughout his campaign.
“How about that?” Mr. Obama replied to a friend’s congratulatory e-mail message on the night of his victory.
But before he arrives at the White House, he will probably be forced to sign off. In addition to concerns about e-mail security, he faces the Presidential Records Act, which puts his correspondence in the official record and ultimately up for public review, and the threat of subpoenas. A decision has not been made on whether he could become the first e-mailing president, but aides said that seemed doubtful.
Showing posts with label email. Show all posts
Showing posts with label email. Show all posts
Monday, November 17, 2008
Yet another Obama giving up his BlackBerry post
See, now, THIS is how presidents should take care of their email issues:
Monday, September 15, 2008
Sarah Palin's e-mail chicanery (Warning: Political)
I thought we had enough of this from the CURRENT administration, but no.
Introducing Dean Dawson, ladies and gentlemen! The man with the most thankless job in the state of Alaska. (I would say 'in the United States', except you have to contend also with Missouri's records manager... or Texas's records manager... or the guy at NARA who has to archive the emails of the Bush Administration... Ah, right, this is why I am not working for the U.S. government!)
Palin routinely uses a private Yahoo e-mail account to conduct state business. Others in the governor's office sometimes use personal e-mail accounts, too.The practice raises questions about backdoor secrecy in an administration that vowed during the 2006 campaign to be "open and transparent."
[...]
She is allowed to keep e-mails confidential if they fall into certain categories, such as "deliberative process," said her press secretary, Bill McAllister.
[...]
"I don't hear any public clamor for access to internal communications of the governor's office," McAllister said.
No, no, Mr. McAllister, that's not how Public Records Laws work. The question is not whether there IS public clamor for the records; the question is whether there COULD be public clamor, say, I don't know, if she were to run for the Vice Presidency of the United States? Admittedly I have not read the Alaska Public Records Law, but I am reasonably certain that there is not a clause in there that says "unless it would be politically inconvenient." There is a reason these things are in place, you know.
Also, it's pretty clear to me that Gov. Palin and you both know that this is sort of a disingenuous argument at best, seeing as how the whole reason that she would use a Yahoo Account is so her emails wouldn't be trackable by the State of Alaska's email system.
No one in the Palin administration could say if the governor is saving her Yahoo e-mails. If she's emptying her e-mail trash, they are zapped from Yahoo's storage system within days or at the longest, months, Yahoo says.
"If you are asking do we have those e-mails, then the answer is no," said Anand Dubey, director of the state's Enterprise Technology Services. "We don't control Yahoo or Gmail or Hotmail or anything like that."
This to me seems awfully convenient, particularly in the wake of the 1100 emails that WERE on official Alaska servers which were withheld from a FOIA request on the grounds of 'executive privilege.' One has to wonder what is in the emails that aren't technically subject to Alaska public records laws. Except that they are. Unless the Governor's personal attorney says that they aren't. Hmmm.
I don't know. I just think it's very frustrating to give an email seminar in which you instruct people not to send business email from their personal accounts, and then read about a vice-presidential candidate for a major party who specifically instructs HER staff to do just that. It's enough to make a grown records manager cry.
Dean Dawson, state-records manager, is working on an e-mail-archive system for state employees, who tend to want to hang onto e-mail forever, he said. E-mail records should be kept as long as paper records of the same type — for instance, three years for general correspondence, he said. Top executives such as commissioners and the governor often must keep records longer, under state schedules.
Introducing Dean Dawson, ladies and gentlemen! The man with the most thankless job in the state of Alaska. (I would say 'in the United States', except you have to contend also with Missouri's records manager... or Texas's records manager... or the guy at NARA who has to archive the emails of the Bush Administration... Ah, right, this is why I am not working for the U.S. government!)
Tuesday, January 22, 2008
Zimbra, E-mail management, and all that rot
Good morning, campers! This post is being written via Zimbra, the engine underpinning PantherLink, the new email/collaboration suite that is being rolled out at UWM sometime next month (and which allows direct blog posting! Very cool). UWM's IT department is surprisingly understanding of records management needs and concerns, considering some of the horror stories I heard last week at the UWROC semi-annual meeting, and they have given me a test account to play with and check out the records management capabilities of the system. So far? I like it, with a few reservations. Not really surprising, considering it's an email system first, a collaboration system second, and a records management application last-- but it's still a bit distressing, considering how much of a problem email management is for both archivists and records managers.
So, without further ado:
THE GOOD
--Tags! Oh man, tags are exciting, and they're implemented here very well. Unlike a lot of tag-enabled applications, which make you input tags separately for each email, Zimbra lets you tag a document, then saves that tag in a visual tag library with color-coded icons. This is REALLY useful for taxonomy, because if a user sees tags, and they are readily available for application to emails, that user is more likely to apply them to the emails they receive. This, in turn, makes searching for e-discovery, reference, etc. That much more likely. Well done Zimbra!
--The Ajax-based UI is a gigantic improvement over the PantherMail interface currently in use. Essentially, what Ajax does for the client is to allow for full interactivity in email management. In practical purposes, this means that things I was doing with Thunderbird-- dragging files, right-clicking to get email properties, etc.-- can be done through the web interface. This is fantastic for standardizing RM training for emails (more people are likely to use the webclient, which in turn means that I don't have to present three scenarios), and also makes it more likely that emails will be dragged to appropriate tags/folders. Speaking of which:
--The foldering schema in Zimbra allows for multi-level hierarchy, which is something not even Thunderbird does. This is great for records management purposes, because it allows users to organize by subject and date, which can (in theory) correspond to records series and disposition date. Of course, this is all still dependent on user application, but to a certain extent this can be partially automated by:
--Message filtering, which appears as a big blue plus sign on every email. With a little training on setting up filters, people can send emails from a certain address or containing certain subject terms directly to the appropriate folder, do not pass Go, do not collect $200 or create inbox clutter. I tell people to use Thunderbird because it has this functionality, but if the web client ALSO has the functionality people may be inclined to use that AND to set up filters.
--Advanced search capabilities built right in, including the use of all appropriate metadata (including tags) as well as keyword search. I don't need to mention how nice this is.
THE BAD
--As far as I can tell, there is no mechanism for actually archiving emails. This is obviously a major flaw from a records management standpoint, exacerbated by the problem from an IT standpoint of people keeping everything on the email server again instead of downloading to a departmental server. This, in turn, will lead to more "reduce your inbox size"-type emails from IT, which will lead to more difficulties with record emails being destroyed. I am hoping this will be addressed in the PantherLink meetings to which I have been invited, but I (admittedly no techie, but at the very least a "clueful user") couldn't figure it out from here.
--A lot of functionality-- but I wonder if that may also lead people to conclude it's too busy. Right now, I count 21 buttons and/or tabs to push on the main screen, and I suspect people-- particularly non-tech-savvy people-- might get intimidated by that, thus not using the RM functionality of the program at all. Similarly:
--The Ajax UI is radically different from the HTML interface being used by the PantherMail system currently in place. For me this is good because I like new and shiny things. For a lot of people this will be bad because they've gotten in the groove of their old email system and don't want to learn a new one. Ultimately, this will result in a lot of people not using the RM functionality out of sheer orneriness. In addition:
--While some aspects of the UI are very user-friendly, like dragging files and creating folders, others are, well, not. For example, it took me about 15 minutes to figure out how to even CREATE a tag, let alone how to apply a pre-existing tag to an already-existing email. This will ultimately mean A TON of training resources expended on my part and on the part of UITS. Speaking of which:
--Zimbra does not, as far as I can tell, include functionality for top-down tag dissemination or categorization. This is problematic because if I don't have the power to make tags immediately available for insertion into people's clients, they will invent their own tags, categories, and folders. This works well for one-computer searching, but not so well for multi-computer searching of the kind that universities often have to do. To a certain extent I can ameliorate this by posting a list of suggested tags on the RM website or something, but again, it's a case of "you can bring a horse to water, but you can't make him drink".
THE UGLY
--The Help menu, in addition to not working right at the moment, takes you to a page on purging the trash folder when you click on "archiving email" in the index listing of topics. Yikes. I hope that's just a link error and not what passes for records management at the Zimbra corporate offices, 'cause if so I think a couple of fellows named Sarbanes and Oxley are going to want to have a few words with them.
So, my initial impressions? As an email management system, very good! This will help a lot of people keep their emails straight, which means less work for me in explaining to people how to find that one email. As an enterprise records management system, less good! There doesn't seem to be any account taken for disposition, workflow, or even exporting of email into a program that CAN do that stuff. Which is fine, considering that Zimbra didn't design the client to incorporate disposition scheduling or archiving, so I can't really blame them for doing that. But it also means more work for me in attempting to come up with a workaround for the lack of university-wide control. If it's helping people organize their emails it's probably a no-score win, but when people start deleting stuff to meet quotas... Oy.
Anyway, this is all subject to change after the PantherLink meetings and/or the actual rollout. We'll see what happens.
ETA: Apparently, I'm not the first person to note that there's no archiving tool in the Zimbra Client, as a little poking around on their website yielded a link to Zimbra Archiving and Discovery. So I stand partially corrected. However, I will keep the original concern up in the post because this is an add-on rather than an automatically included part of the Zimbra email client, and at $24/mailbox, I'm not sure that UITS will be entirely happy to invest in that. Also, the archiving/discovery functionality is administrator-based, which DOES take the onus off of users to archive their email (good) but relies entirely on the discretion of the IT professionals to determine which mailboxes and email messages are worth keeping (potentially not so good). Anyway, I reserve judgment until such time as I actually meet with the PantherLink folks and voice these concerns.
So, without further ado:
THE GOOD
--Tags! Oh man, tags are exciting, and they're implemented here very well. Unlike a lot of tag-enabled applications, which make you input tags separately for each email, Zimbra lets you tag a document, then saves that tag in a visual tag library with color-coded icons. This is REALLY useful for taxonomy, because if a user sees tags, and they are readily available for application to emails, that user is more likely to apply them to the emails they receive. This, in turn, makes searching for e-discovery, reference, etc. That much more likely. Well done Zimbra!
--The Ajax-based UI is a gigantic improvement over the PantherMail interface currently in use. Essentially, what Ajax does for the client is to allow for full interactivity in email management. In practical purposes, this means that things I was doing with Thunderbird-- dragging files, right-clicking to get email properties, etc.-- can be done through the web interface. This is fantastic for standardizing RM training for emails (more people are likely to use the webclient, which in turn means that I don't have to present three scenarios), and also makes it more likely that emails will be dragged to appropriate tags/folders. Speaking of which:
--The foldering schema in Zimbra allows for multi-level hierarchy, which is something not even Thunderbird does. This is great for records management purposes, because it allows users to organize by subject and date, which can (in theory) correspond to records series and disposition date. Of course, this is all still dependent on user application, but to a certain extent this can be partially automated by:
--Message filtering, which appears as a big blue plus sign on every email. With a little training on setting up filters, people can send emails from a certain address or containing certain subject terms directly to the appropriate folder, do not pass Go, do not collect $200 or create inbox clutter. I tell people to use Thunderbird because it has this functionality, but if the web client ALSO has the functionality people may be inclined to use that AND to set up filters.
--Advanced search capabilities built right in, including the use of all appropriate metadata (including tags) as well as keyword search. I don't need to mention how nice this is.
THE BAD
--As far as I can tell, there is no mechanism for actually archiving emails. This is obviously a major flaw from a records management standpoint, exacerbated by the problem from an IT standpoint of people keeping everything on the email server again instead of downloading to a departmental server. This, in turn, will lead to more "reduce your inbox size"-type emails from IT, which will lead to more difficulties with record emails being destroyed. I am hoping this will be addressed in the PantherLink meetings to which I have been invited, but I (admittedly no techie, but at the very least a "clueful user") couldn't figure it out from here.
--A lot of functionality-- but I wonder if that may also lead people to conclude it's too busy. Right now, I count 21 buttons and/or tabs to push on the main screen, and I suspect people-- particularly non-tech-savvy people-- might get intimidated by that, thus not using the RM functionality of the program at all. Similarly:
--The Ajax UI is radically different from the HTML interface being used by the PantherMail system currently in place. For me this is good because I like new and shiny things. For a lot of people this will be bad because they've gotten in the groove of their old email system and don't want to learn a new one. Ultimately, this will result in a lot of people not using the RM functionality out of sheer orneriness. In addition:
--While some aspects of the UI are very user-friendly, like dragging files and creating folders, others are, well, not. For example, it took me about 15 minutes to figure out how to even CREATE a tag, let alone how to apply a pre-existing tag to an already-existing email. This will ultimately mean A TON of training resources expended on my part and on the part of UITS. Speaking of which:
--Zimbra does not, as far as I can tell, include functionality for top-down tag dissemination or categorization. This is problematic because if I don't have the power to make tags immediately available for insertion into people's clients, they will invent their own tags, categories, and folders. This works well for one-computer searching, but not so well for multi-computer searching of the kind that universities often have to do. To a certain extent I can ameliorate this by posting a list of suggested tags on the RM website or something, but again, it's a case of "you can bring a horse to water, but you can't make him drink".
THE UGLY
--The Help menu, in addition to not working right at the moment, takes you to a page on purging the trash folder when you click on "archiving email" in the index listing of topics. Yikes. I hope that's just a link error and not what passes for records management at the Zimbra corporate offices, 'cause if so I think a couple of fellows named Sarbanes and Oxley are going to want to have a few words with them.
So, my initial impressions? As an email management system, very good! This will help a lot of people keep their emails straight, which means less work for me in explaining to people how to find that one email. As an enterprise records management system, less good! There doesn't seem to be any account taken for disposition, workflow, or even exporting of email into a program that CAN do that stuff. Which is fine, considering that Zimbra didn't design the client to incorporate disposition scheduling or archiving, so I can't really blame them for doing that. But it also means more work for me in attempting to come up with a workaround for the lack of university-wide control. If it's helping people organize their emails it's probably a no-score win, but when people start deleting stuff to meet quotas... Oy.
Anyway, this is all subject to change after the PantherLink meetings and/or the actual rollout. We'll see what happens.
ETA: Apparently, I'm not the first person to note that there's no archiving tool in the Zimbra Client, as a little poking around on their website yielded a link to Zimbra Archiving and Discovery. So I stand partially corrected. However, I will keep the original concern up in the post because this is an add-on rather than an automatically included part of the Zimbra email client, and at $24/mailbox, I'm not sure that UITS will be entirely happy to invest in that. Also, the archiving/discovery functionality is administrator-based, which DOES take the onus off of users to archive their email (good) but relies entirely on the discretion of the IT professionals to determine which mailboxes and email messages are worth keeping (potentially not so good). Anyway, I reserve judgment until such time as I actually meet with the PantherLink folks and voice these concerns.
Subscribe to:
Posts (Atom)