Tomorrow sees the first unveiling of IBM Notes/Domino V10. Personally I’m really looking forward to it and on October 23rd we will have our own unveiling in Norway, arranged by us in the Norwegian IBM Collaboration Software Group (ISBG). Now that HCL has taken over the development of the the IBM Collaboration Software portfolio, they have started slowly revealing their plans for the Domino platform.
Yesterday I upgraded Office 2016 manually on my computer. This because I changed my Office 365 subscription to a payment plan that gives me more apps, like Teams and Skype for Business. This made the IBM Connections plugin for Outlook stop working. But thanks to IBM, I managed to fix it. Here’s how you can do the same.
I’ve worked with IBM Notes/Domino (formerly known as Lotus Notes/Domino) since 1997. In those years, the death of Notes/Domino has been predicted so many times. But it hasn’t happened yet.
Now, don’t get me wrong, it could have been at better health than it has been for years.
But as I’ve written several times in this blog, a new initiative has been started, lead by HCL taking over the development of the platform. And they’ve got hundreds of people working on it.
In the past weeks I’ve been part of a group of people who have given input on the design of the user interface for IBM Notes v11, which most likely will appear next autumn. And it looks very promising.
However, there are plenty of new stuff coming for Domino v10 as well. I’ve summed that up in this blog posting. Check it out for all the goodies.
If you need need an expert on IBM Notes/Domino. Or if you want to know anything about the future of Notes/Domino v10 that is out in October. Or if you need a skilled Notes/Domino developer. Or if you need help with your licensing. Or maybe you want to webify your notes applications and make them available on cell phones and pads? Or do you simply want to make your native Notes applications look more modern and sexy?
We in Brainworker can help you. Please get in touch!
Look, I even got a certificate to prove it:
A real life story that happened to me with two different customers.
Once upon a time there two files. Each file was used in a different organisation. The files were important for the organisations and several people needed access to them as several departments and projects needed to be able access, update and read them.
The Microsoft customer
In the first organisation the file was created by a team manager who then uploaded it into a team room in Microsoft Teams. Everybody with access to the team room could now reach the file and work on it. However, they didn’t have version control, nor could they really set different permissions for different users of the team room.
Furthermore, other teams also wanted access to this file. But as long as they weren’t members of that particular team, they couldn’t reach the file. The solution was to upload a copy of each file to the other team rooms in Microsoft Teams. Each team got a different copy. The problem with that solution was everybody was now working on different files. This created a lot of confusion.
Finally they had to sit down and try to merge all the copies into one file, which took a hell of a lot of manual work. When the file was to everybody’s liking, they now uploaded it into Sharepoint. They could now add this Sharepoint file to several team rooms in Teams. They could also set permissions so that some teams could write to the file, while others could only read the file. But they could only set the permissions for the team room as a whole. They also had version control now.
However, the team members had a hard time understanding why the file wasn’t in their Teams files. They had to remember to go to the Sharepoint tab in Teams to get to the file. If they wanted to see the file revision and version control, or wanted to see who had done what to the file, they had to open the Sharepoint app. It was a lot of unnecessary work that made a lot of users rather grumpy and confused.
They also wanted to share the file outside of their organisation with a couple of business partners. This could be achieved via a guest account, but this wasn’t something they wanted to do. Instead they discovered that they could share the file externally via the Offie 365 apps, but only if you changed several permissions in the Sharepoint admin tool first. It was a lot of work and they ended up emailing the files to the external users. They then uploaded the edited file they got in return into Sharepoint, with all the pitfalls that came with such an approach.
What they did love though was the ability to let several people edit a document at the same time in their web browser. This worked beautifully, and they could have an online meeting where everybody was working on the same file, seeing the updates being made live. After saving, all the formatting in Office file was intact.
It was also very easy to access the file via Windows Explorer and to open it up in Office to work with it locally on their computer.
But as the number of Teams grew and people started using more and more of the many apps inside Office 365, it became more and more difficult to have the overview the workers needed to keep up to date. There was no singular newsfeed to keep people updated.
The IBM customer
In the second organisation the file was created by a team manager who then uploaded the file to his own profile in IBM Connections. He then shared the file with his team via the community the team had in IBM Connections. Now all the members of this community could both work with and read the file. They also had full version control and they could also set different permissions for different community members.
Other teams also wanted access to this file. This was no problem. Since the original team leader had uploaded the file to his own profile, he could just share the file with any other community or other users directly. Everybody was now working with the same file without any hazzle.
And even though the file really resided in the original team leaders profile, each community saw the file in the Files view of their community, as if the file was there. There was no need to look for other apps or tabs inside the community. To see who had done what to the file, and to have revision and version control, all they had to do was to to go to the file inside their community. All the details were there.
They also wanted to share the file outside of their organisation with a couple of business partners. This could be achieved via a guest account, but this wasn’t something they wanted to do. And since they didn’t want t to do that, there wasn’t much they could do, without buying a third party app like Box or similar. This was a major grievance for the organisation.
What they also wanted was to be able to let several people edit a document at the same time in their web browser. To be able to to this they had to buy IBM Docs as it doesn’t come out of the box in Connections. But they soon discovered that IBM Docs screwed up the formatting in the Office files, especially in Excel and Powerpoint. For Word documents, they got by.
However, it was very easy to access the file via Windows Explorer and to open it up in Office to work with it locally on their computer, something they were very happy with.
What the IBM customers also was very happy with was that no matter how many communities or how much functionality they used, everything was contained within the same user interface, the same program and the same newsfeed. You didn’t need to think about when to use what functions, everything was inside IBM Connections.
Microsoft’s Office 365 has great functionality when it comes to document editing and creating good and useful Office files. It’s also good for smaller collaboration teams. However, there are way too man apps and way too many possibilities, and despite this, it’s still very difficult to share information and files between these apps. Heck, it’s even hard to share information and files between different teams within the same application. For a large organisation, I would definitely think long and hard before I started using a lot of these apps, especially Teams. A Sharepoint site is better, but then you will have a lot of development costs in addition to the license. Unless you find a good Sharepoint template to use.
IBM Connections on the other hand works out of the box. There’s no development needed, unless you want to of course. It’s also very easy to share information and files across the organisation and the various applications inside Connections. The users are thinking of Connections as one app, unlike Office 365 where you have to deal with many apps. This latter so confusing that Microsoft has made an 85 (eighty five!) page manual to tell you when to use what app…
Bot solutions have the ability to create guest accounts so that you can invite external users. But where Connections can’t share files outside the organisation out of the box, Office 365 actually can.
Both solutions makes it seamless to work with files directly from your local PC and from your email.
So both have their strengths and weaknesses, but I find Connections to have the upper hand when it comes to social collaboration and it has a lower learning curve when it comes to working effectively with it as a collaborative tool across the silos of your organisation. Office 365 still encourages silos.
However, if all you want to do is work with files and not much else, Office 365 is the way to go. And: You can actually work with Office 365 files from Connections. Something you cannot do the other way around.
Any thoughts, questions or comments? Use the comment fields below!
It was when vocalist Jon Anderson gave his all at the beginning of the last section of “Heart of the Sunrise” that the hairs on the back of my neck were higher up than a Republican’s hackles if you mention Hillary Clinton.
I had chills running down my spine, and it wasn’t because the guy behind me had poured the ice cubes from his drink down my back (they had melted a long time ago and the water was now mixed in with my sweat). The stage was flooded with light from the spotlights, and I saw that the almost sold out concert venue Sentrum Scene in Oslo were having the exact same experience as me. “Love comes to you, and you foloooooooow” Anderson sang, and I realised I could either have an orgasm or start crying. I chose the latter…
But which Yes was on stage this evening? Don’t worry. If you are uninitiated, I’m not even going to attempt to explain the complicated story of exactly who is or isn’t a member of Yes at any given moment. Let’s just say that it’s complicated. I mean, really complicated. Just take my word for it, ok?
It’s so complicated that these days there are two versions of Yes currently on their 50th anniversary tours. I saw the other Yes this Easter during the 50th anniversary celebrations at the London Palladium. Said band has no original members left after bassist Chris Squire died. Still, they are the ones named just Yes, and they also are in possession of the rights to the famous Yes logo.
The band playing at Sentrum Scene in the Norwegian capital this evening, on the other hand, has Yes founder Jon Anderson as their leader and vocalist. His voice, and name, are what everybody thinks of when identifying Yes. With him he as guitarist Trevor Rabin, who came into the band in 1983 and gave the band their comeback hit “Owner of a Lonely Heart.”
Third man out is keyboardist Rick Wakeman, who’s been in and out of Yes so many times that I ran out of fingers trying to count them. However, say “Yes” and “keyboardist” in the same sentence, and most people will say “Rick Wakeman.” He’s also had a solo career that resulted him selling more records than Yes ever did.
The last time I saw Yes on Norwegian ground it was the other Yes, with Benoit David on vocals. That was an unmitigated disaster of the biggest proportions. David sang so out of tune that a dead hamster buried in the basement of a 30 storey house under a ton of bricks would have tried to get away. And people left the concert in droves.
However, with Wakeman and Anderson on the bill, it seemed that Norwegian Yes fans were willing to give this version of Yes a chance. I was also pleased to see so many young faces there, even if I was below the medium age in the room. But it didn’t really matter, because the band was welcomed with arms that were more open than a Scotsman being told he will be paid in cash. And it’s been a long time since I saw that many people at this particular venue.
The concert started with the instrumental “Cinema” from the album “90125,” before we jumped into “Hold On” from the same album. Then it was straight back to the 70s to perform “South Side of the Sky,” a song Yes almost never played in their 70s heyday. We stayed in that decade to be served one of Yes’ most famous songs, “I’ve Seen All Good People” (- For all the good people of Oslo, as Anderson said).
And so it went. We were in the 70s (“And you and I,” “Perpetual Change,” “Heart of the Sunrise” and “Awaken), with the occasional trip to the 80s (“Changes,” “Rhythm of Love” and “Owner of a Lonely Heart.”) At one point we even visited 1994 and the album “Talk” through the song “I am Waiting.”
Wakeman was in character in a long glittering cape going all the way from his shoulders to the floor (you get away with that sort of thing if your name is Rick Wakeman). His fingers were dancing over the keys like they were made of air. All the soup diets he’s constantly tweeting about didn’t seem to have had much effect, but my oh my how he played. It wasn’t quite up there where it used to be, but my music teacher in middle school would have given him a A-. At least!
And then it’s Jon Anderson. The man who was described as “slightly to the right of Hitler,” by original drummer Bill Bruford, when it came to the treatment of his bandmates… Anderson is 73 years old, and even if his voice isn’t as flawless as it used to be, I know quite a few aging rock vocalists who are green with envy when they hear what Jon Anderson is still able to pull off, vocally. (A certain other Anderson, who’s first name starts with I, I’m looking at you!)
Rabin is a few years younger than Wakeman and Anderson, but he is the one who has been seeing a plastic surgeon on a regular basis, as well as getting lots of hair transplants. He looked like a cross between Ray Monroe in Twin Peaks, Michael Jackson and Little Richard. Still, he’s a great guitarist and I didn’t mind the rearrangements he did of some of the 70s material.
Drummer Lou Molino III played the drums and percussion just brilliantly, and bassist Lee Pomeroy got to play around with “Heart of the Sunrise,” where the entire opening riff is carried by the bass. However, for a band that was started by one of the most brilliant, and original, bass players of all time, Chris Squire, it’s just plain wrong to hide the bass in the mix the way they are doing on this tour. Stop it!
The concert also lasted for just over two hours, way too short for a Yes concert!
But that is just nitpicking when you think back on such magic moments like “Awaken,” where harp, church organ and Jon’s cosmic lyrics made you fly so high that you wondered if you had consumed other remedies than just beer that night. The version they did of “Owner of a Lonely Heart” was also fantastic. Especially the incredible jam session they did towards the end, including a keytar solo.
And when the whole thing was concluded with an encore consisting of a flaming version of “Roundabout,” we all could just dance (or at least as close to a dance as a stiff and aging body is able to) out in the summer warm Oslo, knowing full well we had just seen “all good people.”
Please come back soon, Yes featuring ARW. I am waiting! I am ready!