OneNote and Metadata in SharePoint – Add a Notebook to a Library – Part 4 of 5

As described in our original scenario, we want to create a relationship between our Client list and their related documents, including a new OneNote notebook.

OneNote notebooks are different from their sister programs in the Office application suite because a notebook consists of several related files, and thus are stored differently. As a result, you wouldn’t simply Upload a OneNote notebook into a document library. Let’s go thru the steps and options for adding our OneNote notebook to SharePoint:

OneNote and Metadata in SharePoint–Connecting Related Documents to Client Names–Part 3 of 5

As described in our original scenario, we want to create a relationship between our Client list and their related documents, so that ultimately we can make a relationship between our OneNote notebook, and the related Client. We created our Client Names list in Part 2, now lets see about making the connection with the documents.
Here we have a basic document library that contains several different documents:

But how do we know which Client the Expense Report belongs to, for instance? We’d have to open the document and read its contents to try to figure it out. Wouldn’t it be nice if we could add a column that could tell us that information right in the default view of our document library? Fear not – we can!

OneNote and Metadata in SharePoint–Creating a List of Client Names – Part 2 of 5

As described in our original scenario, we want to create of list of Client Names so that we can ultimately associate our OneNote notebook with one of them.

This list can be thought of as a standard Lookup list, as well as a repository for Client information. The Client Name will be used to fill dropdowns in other list columns or forms, but also provides a 1-click way for a user to see more detailed information about a Client associated with another item. I’ll show you what I mean, but first let’s create the list. You can use any of the following methods:

• The Standard Way
• The Import Way
• The SharePoint Designer Way
• The PowerShell Way
• The Visual Studio Way
• The External Content Type with Azure Way

Choose the option that works best for you – let’s begin! (click on images for larger views):

OneNote and Metadata in SharePoint–Part 1 of 5

The Scenario

As a SharePoint Consultant, I support several clients. I keep a list of my clients in my SharePoint MySite:



For each client, I store and manage related documents (like Statements of Works, Requirements documents, or important Emails) as well as OneNote notebooks for each client. Using SharePoint’s concept of Related Lists, each document can contain metadata about the client to which it applies:



And together, I can get a comprehensive view of each client’s important information:

 

The Problem

For many clients, I like to capture information, including handwritten notes from my tablet, in a OneNote notebook. OneNote is a great solution for capturing, categorizing, and sharing both structured and unstructured information. Add a tablet PC and a pen stylus to the mix, and you’ve got a very powerful & versatile tool. Storing my OneNote notebooks in SharePoint allows for easy syncing across devices and collaborators.

The 3 T’s of Giving Back to the SharePoint Community

I recently had an article published regarding ways to give back to the IT community. Later, my Twitter buddy SB Chatterjee tweeted it to his followers, and pointed out that it applies to the SharePoint community as well.
Good point! With that in mind, here’s a pointer over to to the BIT Tech Digest where you can find the article. Let me know what you think – do the same principles apply to the SharePoint community as well?:

• The 3 T’s of Giving Back to the IT Community

Overview of SharePoint 2013 Development Features

Last week, I spoke at the DogFood Conference 2012 in Columbus, OH on the topic of InfoPath, as well as on the new development features in SharePoint 2013. The DogFood Conference was a great event, with over 90 different sessions on all things Microsoft.

As I prepared this talk, I thought back to my last SharePoint Dev Features presentation, where I compared SP2007 with the new features of SP2010. My analysis now is that, while SP2010 was a huge leap forward from SP2007, SP2013 is more of a ‘somersault vault’ off of the vision that SP2010 started, in terms of maturing the development model and empowering the developer.

If you were to ask me to sum up my SharePoint 2013 Development presentation in 30 seconds, here’s what I’d say:

SharePoint Saturday Cincinnati 2012–Retrospective

Well, I’ve returned home from a day well-spent at the now famous event:

It was a great event filled with great speakers and good information. It was also complemented by attendees dressed in kool & unforgettable costumes, as well as other folks whose costume I’m trying to erase from my memory.