A publishing site and a Team Site are common in many ways but there are some differences. Here I am going to talk about the High level differences without going Into too much of detail.
One of the main differences between a Publishing Site and a Team Site is that a publishing site can be customized to a larger extent than a Team Site. If you are planning to Install a 3rd Party tool like Akumina or Live Tiles, you could either deploy it on a publishing site or you could deploy it on the Team Site and activate the Publishing Features under Site Settings.
Some of the libraries that are available by default on a Team Site are not there on a Publishing Site. Some of them are News Feed and Calendars.
Finally, A Team Site is light weight whereas a Publishing Site requires more resources. So, while creating a new site you would need to think about the requirements and accordingly make a decision on which type of site you would need to create.
SharePoint is a platform for document management and collaboration. Documents such as Word, Excel and PDF’s are the common document types that are uploaded in SharePoint. In order to view documents in SharePoint, particularly SharePoint Online, you would normally click on a file which opens an Online Version of the Document.
Suppose you have documents that you need to access in a regular basis, it would be Inconvenient for a person to navigate through different pages and finally land Into the Document.
If you have One Note and you need to view the document, all you have to do is copy the URL of the Word Document from the Address Bar and paste it on One Note. After you paste it One Note would automatically render the document. This saves you time navigating and searching for the Document!
Out of three, I am pretty sure many of you would have not heard of Folksonomy. Before we dive into Folksonomy let’s see what a Taxonomy is? A Taxonomy is a classification system that is used to classify organisms into different categories and sub-categories. The tags which are used for classification are a standard and were created by experts.
Like Taxonomy, folksonomy is also a classification system but with a difference. Here, the tags are created by end-users of an application.
Now let’s come to the third part ‘Keywords’. Let’s see how does this fit in? Keywords in SharePoint are stored in the Managed Metadata term store. They are located under System->Keywords. Keywords in this location are termed as Folksonomy since they are created by end-users. But the problem with this arrangement is that the keywords can only be used within the site for which it is configured. If you need to manage the keywords in a central location so that it can be used in all the sites of the site collection, you would need to move the keywords to a term set. Please Note: Once the keywords are moved to a term set , they cannot be moved back. They are trapped in a sense!
Once the keywords are stored in a term set, they are part of a taxonomy. So, the process of moving keywords to a term set is often called as Folksonomy to Taxonomy.
When we search for something using a search engine we normally don’t enter the exact keywords that would be present in a website or a document. What we actually enter is something that tends to have the same meaning as those keywords or a phrase that would relate in that way.
Search without synonyms would definitely be something that someone does not want to live with! Without synonyms configured, if you don’t happen to enter the keywords that are present in a document or a website you would get 0 results. This obviously would be really frustrating and you might end up pulling all your hair out off your head :D!
Fortunately SharePoint Search recognizes synonyms and it can be configured. In order to configure it, one would need to Import a Thesaurus file to SharePoint using Power Shell. The Thesaurus file basically contains the key with the corresponding synonym, something like this
key, synonym, language
For Example in a thesaurus file an entry would be-
emerges, rises, en
where en stands for English
So suppose a document had a word called as “emerges” and you search for “rises”, you would still be able to retrieve the document from the search results.
Each line is a new entry in the file. And once you are done adding the entries, the file can be uploaded to SharePoint. One must note that if you re-upload the Thesaurus file with new keywords, it would not automatically add those keywords to the existing thesaurus file. It is basically going to create a new file with the keywords that you had planned to add. So, it is always wise to keep a backup of your Thesaurus file in your local hard drive so that you don’t loose your data if you accidentally happen to upload a file with just the new words.
The term keywords is in a way synonymous to search. It helps a person be able to retrieve an Item or a group of Items based on the keywords he/she entered in the search bar. This so happens because someone (Person/Algorithm) has formerly associated those keywords with those Items. In technical terms it is known as Indexing.
With reference to documents, it is people who are working or collaborating with it who know the essential keywords for that given document. With SharePoint, we enable our end users to add keywords. Keywords can be added to 2 different types of Items. It can either be added to a list Item of a SharePoint List or it can be added to a document in a Document Library.
Obviously when you are trying to add an Item to a list or a document library, you would need to add it to a specific column. The column is called the “Enterprise Keywords” column. Over here, end users can add any number of keywords to any of the list Items (In case it is a SharePoint List) or a document (In case it is a Document Library).
In the figure below, you can probably see a clipping of a Document Library with columns- Modified By and Enterprise Keywords. In Enterprise Keywords, one would be able to specify the keywords to be associated with a document or a list Item.
In order to add the Enterprise Keywords Column to a content type, one would first have to configure the Default storage location for the keywords. The default location for the keywords should point to the Managed Meta Data Service. This can be done in the Central Administration.
SharePoint is the cloud sibling of the SharePoint family. It comes with your Office 365 Subscription. Microsoft Initially built SharePoint solely for on-premises but since the launch of SharePoint Server 2013, they have also come out with their cloud product.
The advantages of SharePoint Online is the end users get acquainted with the latest features from Microsoft. It is easier for Microsoft to release new features to the cloud rather than the On-Premise version. Hence, the cloud version gets newer features and updates before the On-Premises Version.
With SharePoint Online and Office 365, Microsoft has created a new view or look for SharePoint itself. It translates to the entire SharePoint Online Infrastructure. There have been changes to the appearance of Items in the Menus and some of the menus which were quite prominent in the On-Premises version is not there. They have tried to make use of the Office 365 ribbon and have tried to transfer most of the functionality over there.
If a user is not comfortable with the the new look, he can switch over to the old view at any point of time. There is a link at the bottom left hand corner which says “Switch to Classic view”. There is a perceptible difference in the appearance of the old and new view, just to give you an Idea here is the view of a Document Library. This is a view from the New look
And this is the old view
See the difference? The old view has a menu for the library which Includes difference functionality which is not there in the new view. So if you happen to be in the old view and want to come back to the new view, simply close your browser and open it again, this would delete the cookies associated with the old view.
Information Architecture deals with how Information in SharePoint is presented to the End Users. The goal of an Information Architect is to design and present Information in a way that it is easily accessible to the end users. They should be able to search for the Items that they are looking for.
Navigation is one of the aspects of Information Architecture. The Architect can control the way how the user maneuvers over the site. Another point while considering developing a good architecture is that it should be easily managed. After the process of Installation and migration, the IT department has to be in charge of the Intranet and it would make their lives better if it is easily manageable.
Organizing content is the next part of Information Architecture. Some content maybe sensitive and needs to be placed in a specific location of a site and some content should be displayed publicly among all users. The Architect needs to work with the Compliance Team of the company in order to find the requirements regarding organization of documents.
Folders are a good way to store files and documents but with SharePoint 2016 this is slowly becoming a thing of the past. Now the trend is to use metadata to tag documents. Metadata radically improves the search capabilities of SharePoint. Once documents are tagged they would appear in the Search Results based on the tag. And through metadata there is the ability to connect or link disparate sites. For Example you might be in the HR site collection, but through metadata you could also get results from other site collections as well. And another good thing about metadata is it eliminates redundancy in terms of document creation. With metadata, you wont have documents in two different site collections with the same file names.
Information Architecture is all about creating or design a proper structure and then organizing the content in a way so that end users can easily access them.