SharePoint DocumentSet vs Folders

Once i was thinking that DocumnetSet is same as a folder in SharePoint. So i did some readings and found this.

It says;

“There is a difference between a folder in SharePoint and a folder on your desktop. Microsoft made them look the same in the GUI to make it easier on users, but that’s where it stops. In SharePoint, a folder is simply a “view”. In other words, it is a way to limit the number of items the database displays. If you look at the URL, it’s a long complicated way of saying only show me the stuff assigned to this naming designation.

So if folders are views in SharePoint, why can’t I change them like views? You got me there. Somewhere along the line, the capabilities of the “folder” view and the “normal” view diverged and different rules applied. For example, I can add unique permissions to folders, but I can’t add column properties. The opposite is true for views.”

The point is in SharePoint 2010, Microsoft decided to change how it thought about Content Management. Since content types have caught on as the best way to solve the problem of “a single set of rules and naming conventions,” they started to think how they could exploit that scenario to group things together. THUS, the document set.

A document set is a group of related documents that can be created in one step and then managed as a single entity. A document set is not a view, but a special content type. It is managed and deployed from a site collection level. You can create custom document set content types with site columns and managed metadata. You can apply unique permissions to document sets. You can view a document set’s version history. You can trigger workflows within a document set.”

Here is the Complete article i’ve found.

Cheers…!!!

Unable to view uploaded documents in Sharepoint Meeting Workspace

This is something interesting. I’ve found this while I was developing an event management app. So apparently I was selected the Meeting Workspace Site Definition. The problem occurs when I was uploading a document to a document library. In here we can’t use SPFile.CopyTo();  So I used

SPSite site = SPContext.Current.Site;

SPWeb web = SPContext.Current.Web;
SPFile file = web.GetFile("/Shared%20Documents/Doc.docx");
using (SPWeb oWeb = site.OpenWeb(<siteURL>))
{
    SPList documentLibrary = meetingWorkspace.Lists["Document Library"];
    documentLibrary.RootFolder.Files.Add(file.Name, file.OpenBinary());
}
This code works fine, no issues. But if  you navigate to the document library, you can not NOT SEE any uploaded documents there(in view).  So what was happened to the document?  If you check the value of the SPList.RootFolder.Files.Count;  property you will see that the file is there too. So why does the Document Library keep saying that there are no items to display?
Here is the answer.
By default you can associate a Meeting Workspace with multiple Calendar Items. Every time you associate a Meeting Workspace with a Calendar Item, a new instance is being registered with the Meeting Workspace. In order to separate files that belong to different instances, SharePoint uploads them to separate folders. The confusing thing is, that although the instance folders are not being displayed in the UI, they are there.
So all we have to do is make sure to add the document into correct instance. Following is the workaround,

SPSite site = SPContext.Current.Site;

SPWeb web = SPContext.Current.Web;
string instanceId = "1";
SPFile file = web.GetFile("/Shared%20Documents/Doc.docx");
using (SPWeb meetingWorkspace = site.OpenWeb(<siteURL>))
{
    SPList documentLibrary = meetingWorkspace.Lists["Document Library"];
    SPFolder instanceFolder = documentLibrary.RootFolder.SubFolders[instanceId];
    instanceFolder.Files.Add(file.Name, file.OpenBinary());
}
Now Go back to the Library and check. Check this for more clarifications.
Good luck.