SharePoint Search Planning

SharePoint Search Planning

The following are some core search planning items to consider and plan for:

·         Where is the information located to be crawled (file share, SharePoint, other location)?

·         What content sources need to be set-up?

·         If full or incremental crawls are utilized what are the schedules?

·         Will continuous crawl be utilized?

·         What words will be utilized in a best bet

·         Who will monitor search to ensure that crawls are running successfully?

·         When and where will reports on search usage be run and placed?

View Video:

SharePoint Planning Personalization’s

SharePoint Planning Personalization’s

The following are useful when planning personalization’s:

·         Decide what Active Directory attributes should be utilized and imported for profiles

·         Decide what profile attributes to display on user’s profile

·         Decide and implement on a profile import schedule

·         Decide what audiences to create

·         Decide when audiences should compile (after the profile import)

View Video:

SharePoint Root Directory Quick List

SharePoint Root Directory Quick List

The following are some core SharePoint root directories – these are common directories on a web front end and typically what type of files they contain in them:

C:\Programs Files\Common Files\Microsoft Shared\Web Server Extensions\

Then the last directory will be as follows – depending on the SharePoint version utilized:

14 = SharePoint 2010

15 = SharePoint 2013

16 = SharePoint 2016

 

The following are the common directories then the types of files in them:

/ISAPI – Web Services (*.svc, *.ashx and *.asmx)

/Resources  – Resource files (*.resx)

/TEMPLATE/ADMIN – Application pages used in central administration

/TEMPLATE/FEATURES – Feature definition files (*.xml)

/TEMPLATE/IMAGES – Images (*.gif, *.jpg and *.png)

/TEMPLATE/LAYOUTS – Application pages (*.aspx)

/TEMPLATE/LAYOUTS/1033/STYLES – CSS files (*.css)

/TEMPLATE/LAYOUTS\ClientBin – Silverlight components (.xap)

/TEMPLATES/Site Templates – Site definition files (onet.xml)

/TEMPLATE/XML – Custom field type definition files (fdltype.*xml)

 

View Video

SharePoint Governing Information Architecture

SharePoint Governing Information Architecture:

Governing the information architecture is a key to the successful use of SharePoint Server and requires the participation of business managers, content managers, information workers, site designers, and IT professionals.

Defining information-governance plans requires an understanding of the site topology, the purpose of each offering (example Intranet, Extranet, OneDrive etc.), and preferably a knowledge of future planned offerings, such as business intelligence.

Information policies need to be defined for each site within the SharePoint deployment. A policy needs to be defined per topic area for each site offering.

View Video:

Document Library Planning:

Document Library Planning:
The following are some items to follow in regard to document library planning:

1)      Enable the require checkout option for editing

2)      Keep the number of documents in a view below 2000 items if possible

3)      Limit the number of major versions typically recommend set to 25-50

4)      Educate users on proper naming conventions example:

IT Contacts Doc = BAD

IT_Contacts_Doc = GOOD

IT Contacts 7142017 = BAD

IT_Contacts_7_2017 = GOOD

5)      Think about if turning on metadata navigation or using document sets makes sense based on the data that will be housed in a said library.

Metadata navigation can be used when it make sense to have the ability to dynamically filter and find content in lists and libraries by using a navigation hierarchy tree control to apply different metadata-based filters to the view.

Document Sets can be used if one has a group of related documents that can be created in one step and then managed as a single entity.

Video: