Bootstrap CDN is a convenient way to explore the functionalities of Bootstrap without the hassle of downloading and saving it to your local server. All you would have to do is paste some script tags on the header of your HTML page that would link to the files in the Bootstrap Server.
As I write this blog, the latest Version of Bootstrap is v4.0.0-alpha. You can find the script tags to Include on your page over here.
Be aware that once you are using features like DropDowns, they won’t work. The reason being that Dropdowns require JQuery and that is not normally given with the CDN. You would have to explicitly specify a script tag to compile JQuery. And make sure that is the first tag that you put on your header tag before the Bootstrap script tags.
Your header should eventually look something like this-
Once you have this on your header , the dropdowns should work 🙂
There is not a straight forward process to forward email from a distribution list to an Office 365 Group. You would need to follow these steps in order to do that-
- Create a Shared Mailbox.
- Add the newly created Shared Mailbox as a member of the distribution list. Doing so would allow the Shared Mailbox to receive email from the distribution list.
- Set up Email forwarding in the shared mailbox to forward email to the Office 365 Group. Now there is a point to be noted here, you would not be able to do this in the Exchange Online Admin Center. You would need to use Power Shell in Order to setup forwarding to an Office 365 Group.
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.
Add-ins in Outlook help the end user to connect to different applications of Interest. Those applications might be a plugin for a CRM tool or anything that would help in Improving the productivity of an end user.
There may be times when Outlook has too many add-ins which consequently might cause it to crash or run slowly. The email client has an inbuilt mechanism to disable add-ins that are possibly causing the crash. This would be the done automatically without the permission or approval from the user.
The next time you would open Outlook, you might find that some of the add-ins that you see everyday are apparently missing! Now there is no reason to panic, fortunately there is an easy way to bring them back to life and I will show you how!
- Click on the File Menu located in the top left hand corner.
- Click on the Info tab on the left and scroll down.
3. Scroll down and click on Slow and Disabled COM Add-ins.
4. Click on the Add-in that you want to enable.
And now you have brought your add-in back to life 🙂 !
Outlook as we all know is a popular email client. It gives you the functionality of connecting to different applications. In order to do that one would need to Install an add-in for that application.
Over a period of time if you go on adding add-ins, Outlook would reach a point where it would become terribly slow and prone to constant crashes. This is a time when you need to start thinking about deleting add-ins that you don’t need.
Fortunately deleting Add-ins in Outlook is very easy. It is similar to uninstalling an application in Windows. Most of the outlook add-ins would be located in the Programs and Features section of the control panel. All you would have to do is go to the Programs and Features section and uninstall the add-in.
- To open Programs and Features, there is a shortcut. Press the Windows Key and X, this would then open up a menu that would appear to be something like this
- Click on Programs and Features.
- This would then take you to the Programs and Features section of the control panel, where you can uninstall that add-in.