Recently I had two clients who are using File Jockey to copy files between SharePoint and Connections. Its great to see how people fix their challenges with File Jockey. This blog explains how to carry out this task and how File Jockey is a part in the process.
In SharePoint files are stored in Libraries in most occasions. When the files are stored in Lists the files are not so important compared with the List columns. So we focus on SharePoint Libraries in this post.
In a SharePoint Library the files can be stored in the default way or the files are stored in SharePoint document sets.
The trick is to open the Library in the internet explorer because then you will have this option under Library settings available (it is greyed out in all other browsers).
When you press it it will open the library as a network drive in your Windows file explorer.
The next trick is to create a network drive, so copy the SharePoint URL as illustrated below
The create a new network drive
No need to enter credentials in my case, I guess its already cached somewhere in Windows. And a new network drive is created.
The SharePoint library will display the same files obvious.
The same approach will also work if the SharePoint library is using document sets which contains folders and files.
Now we have one network drive that displays the files in a SharePoint library.
What about IBM Connections? Default the client can install the IBM Desktop plugin. The issue with the desktop plugin is that it does not allow you to copy to or from a while community.
For example, if I would like to copy all Community Libraries in one go this is not possible. I have to go into each Library and then I am able to copy all folders and files in one go.
In the case I would like to copy files from a SharePoint Library to Connections Folders I have the same issue. I cannot past multiple folders in one go from SharePoint to Connections. So the IBM plugin is a bit limited when used this way.
The alternative is to use File Jockey. It can be used to create a SharePoint alike network drive to the files in IBM Connections. For Connections on premises you have to install the solution first on WebSphere. For IBM Connections Cloud we offer a free File Jockey cloud service.
In this example I have a network drive to IBM Greenhouse via File Jockey.
So now I have two network drives on my PC to SharePoint and IBM Greenhouse (via File Jockey).
Now I can use a program like Total Commander to display the two network drives left and right and to start copying files between Connections and SharePoint. On the left Connections and right SharePoint
Its also possible to use the file explorer to copy files, but total commander does it a bit better is my opinion.
In below example I copy all files from the SharePoint library (with document sets) to a library in Connections
The nice thing of Total Commander is that you can put the copy action to the background allowing you to start a second copy operation.
In below example I will copy 4 Connections communities with all content (Folders, Libraries) in one go to SharePoint.
When the copy operation is ready you want to be sure that everything is transferred properly. For this task you can use the Beyond Compare program.
In the example below you can see that this program is used to compare the two network drives with SharePoint and Connections (the copy process is not ready yet, that’s why Beyond compare reports differences).
Lets use Beyond compare to synchronize Connections to SharePoint
Bottom line, when the files of SharePoint and IBM Connections are available on two network drives on the same computer a lot of programs and approaches can be used to copy files between these two sources.