Magenic Company Blog

Microsoft introduced a new feature in SharePoint 2013 called Cross-Site Publishing. This new functionality allows content in one site collection to be more easily shown in another site collection.

If you're like me, challenges are what make being a developer fun. Sometimes, however, these challenges can be daunting. With piecemeal information at one's fingertips, it can be aggravating to say the least to try to solve a vexing problem.

Last month, a group of Magenicons, including myself, descended upon Microsoft’s annual SharePoint Conference, this year in Las Vegas. Front and center was SharePoint 2013, a brave new release that literally changes the game in so many ways, it’s hard to list them in a single blog post.

Of course Magenic provides many services and products for many different businesses. As an example, Steve Hughes, Business Intelligence Project Lead for Magenic, took some time to share some elements of a recent project.

When Dakota County needed a solution to make their Criminal Justice Integrated Information Network (CJIIN) move to the next level, they looked to Magenic for help.

It’s important to properly manage how site collections are placed into content databases within a SharePoint Farm. This is because a content database size can negatively affect performance, especially when it grows to hundreds of gigabytes or even terabytes of data.

A very commonly misunderstood concept in SharePoint is the notion of page customization and uncustomization. While this topic has been hashed and re-hashed, it seems that every time I revisit it, I gain new insight. This post will try to sort out some of the spaghetti to bring more clarity and also try to point out a different perspective on a familiar concept.

One aspect of FAST Search for SharePoint that needs to be considered is how to effectively “tune” the search engine to increase recall and relevancy. Out of the box, FAST includes a default configuration that while handling most situations, is not meant to be left in its default state. Since each business scenario carries a different set of requirements, it is most useful to configure the engine to produce results that are of high value to one’s organization.

Imagine that you are creating a content type for a publishing page or a document and you want to have a field in that content type that is a managed metadata field (a.k.a. a taxonomy field). This allows users to select a term from one of the termsets that you have in your Managed Metadata Service’s termstore. There are many steps to do this.

Hello everybody, and welcome back to the second post in our blog series about SharePoint Enterprise Application Development. Our topic this time around is Build Engineering.