SPC2011: Best Practices from the Field: Managing Corporate Metadata and Taxonomies

Notes from the SharePoint Conference 2011
Session:  Best Practices from the Field: Managing Corporate Metadata and Taxonomies
  • Terms – max: 7 levels deep
  • managed metadata can be imported
  • Content Type Syndication (this is new) – federated service for reusing content types across the enterprise
  • Design Best Practices

– define purpose of taxonomy
– avoid deeply nested taxonomies: start with 2-3
– do not underestimate the time for prep

  •  Technical

– Translate business requirements to sharepoint capabilities
– understand limits (max level = 7, max term sets in term store = 100, max terms in termset = 30,000, max terms in term store = 1,000,000)
– multilingual consideration

  • Business Best Practices

– Identify ownership
– Keep it simple
– factor ongoing maintenance
– identify change control protocol
– define governance

  • Challenges: Life science area

– complex process to ensure traceability for FDA audit
– patent expiration
– drug discovery
– account for regulatory compliance and record retention

Advertisements

SPC2011: Best Practices for User Profiles

Notes from the SharePoint Conference 2011
Session: Best Practices for User Profiles

1. Don’t  enable personal sites just for search

2. Host mysites on its own web application

3. Don’t create personal sites ahead of time

4. Encourage users to observe and use existing tags -> consistency
*FAST search does not index social tags

5. Enable metadata keywords
– list settings > metadata publishing
– follow tags as interest in MySite
– get all info about tag in MySite newsfeed
– tags don’t have permissions but search is security trimmed so users wont see anything they aren’t supposed to

6. Ratings are overrated. Use with caution

7. Enable Activity feed timer job (may be disabled by default)
– default scheduling is hourly – may want to change according to your needs

8. Take time to plan
– what are the business goals?
– which features do you want enabled?
– what permissions should users have?
– what profile properties do you need? (talk to HR/AD group)
– create governance around tagging, ratings, updates, and privacy

9. The AD group may lie to you

10. Configure write back to AD to show picture of users in outlook and lync

12. Use dedicated account for synchronization
Each connection needs to be configured separately – AD, BCS, LDAP

13. Remove disabled users
userAccountControl = 2 filter

Check out:
– Spence Harbor’s blog for more details
– White paper on technet about planning for user profiles

SPC2011: Clearing away the clouds: what’s hype and what’s real about cloud adoption

Notes from the SharePoint Conference 2011
Session:  Clearing away the clouds: what’s hype and what’s real about cloud adoption

Benefits

  • capability on demand
  • reduce cost

Approaches

  • Most companies start by moving their email to the cloud
  • Also consider try before buying

Challenge: end users overlook IT and engage cloud services

Getting Ready

  • Engage compliance/legal groups
  • Determine why to move to the cloud (ie. flexibility, cost)
  • Determine where to start (ie. email, storage, business applications)
  • Find areas of least risk
  • Look for vendors
  • Create criteria for moving off the pilot
  • Create criteria for success

Why to consider waiting

  • Complex customizations
  • Cost saving is the only driver
  • Custom applications/integration
  • No buy-in from upper management

Talking to the boss

  • Compare cloud to current
  • Don’t minimize risk
  • Describe exit plan
  • Make sure peer and other leaders are behind it
  • Research what other organizations are doing

SPC2011: Out of the Sandbox and into the cloud: Build your next SharePoint app on Azure

Notes from the SharePoint Conference 2011
Session:  Out of the Sandbox and into the cloud: Build your next SharePoint app on Azure

Overview:
Using Windows Azure as a workaround for sandbox solution limitations in SharePoint Online

How to get around sandbox solution limitations

  • Fully trusted proxy
  • Client side web part that contains javascript and jquery
  • Silverlight web part

How to consume Azure based solution in SharePoint

  • Content Editor web part
  • Sandbox solution web party
  • BCS
  • Search

How to enable Azure based solutions to interact with SharePoint

  • Client Object Model
  • REST
  • SPS Authentication configurations (ie. Classic mode, Claims based)

Demos

  • Using an IFRAME to show Azure content in SharePoint site
  • Using a Content Editor web part that contains javascript/async JSON to access the Odata svc
  • See Andrew Connell’s blog for more information/materials
  • Check out the Azure learning kit

SPC2011: Understanding SharePoint Administration, Part 1

Notes from the SharePoint Conference 2011
Session: Understanding SharePoint Administration, Part 1

Overview:
Discussed infrastructure best practices, virtualization, hardware/software requirements and installation

Infrastructure

  • Have SQL server on a separate server
  • Use load balancing
  • Need a server license for all SharePoint servers
  • Consider search on a separate server – Crawling will not affect web front ends
  • Consider separate index servers for large document capacity

Production environment

  • 100 GB C drive (used by e. 14 hive)
  • X GB second drive (move all possible files such as logs)
  • 4 cores
  • 8 GB RAM
  • Make sure that you have the same drives on each server
  • All servers need to be in the same datacenter

Virtualization

  • Web front ends – sure
  • Application – usually
  • SQL – never
  • Reference: Todd Klindt’s blog on sp2010 hardware/software requirements

Development environment

  • Need at least 4 GB RAM
  • Can run on Windows 7 or Vista but never for PROD

Test environment

  • Developers should have zero access to test servers
  • Should be multi-server if PROD is

Installing

1. Prereq installer

2. Installing the bits (setup.exe)

  • Install on all servers at the same time
  • Use admin account
  • Do not do standalone install
  • Uncheck the box to run the config wizard – will run later

3. Configure the bits (powershell)

  • Powershell: New-SPConfigurationDatabase
  • Now run config wizards on each server – can run all at the same time
  • Use NTLM

4. Farm configuration (powershell/central admin)

  • Manually provision servers (if do automatic, may get strange names)
  • Use powershell for service application configuration
  • Todd Klindt has a blog for cheat sheet for required service accounts to have
  • Create state service and usage and health data collection using powershell (not available via UI)

SPC2011: Best Practices for Creating Publishing Page Layouts

Notes from the SharePoint Conference 2011
Session: Best Practices for Creating Publishing Page Layouts

• Use DIV tags for positioning
• Only give users control to alter content when they need it
• Use case: Brembo (http://www.brembo.com )
• Example: jquery against dataform web part

○ Site has an area that flips through multiple images
○ Images are kept in an image library
○ Add library fields like “order” to configure image order and time from library

• Modal Dialog framework (ie lightbox)

○ Part of the client object model
○ Example: when you click on a news preview, it opens the news article in a lightbox
○ Consider using a modal dialog over a page reload – appears faster to users

• EditModePanel & delegate control

○ EditModePanel – content area that is only viewable/editable when edit page. Used to add page metadata (ie “Summary” or “Keywords”) –> increases search optimization
○ Delegate control – Region in an aspx page that allows content to be replaced with custom content without having to redeploy the page layout. Retrieve data in the editmodepanel fields and put it in the metatag in the head -> search engine optimization

○ Content Query web part (CWQP)

§ Customize to look up page field value and filter content based on value
§ Field needs to be a managed metadata property

• Dataform – Rolls up information from multiple data sources – beyond the site collection boundaries
• Content Query web part

○ Use when possible because of it’s flexibility to customize
○ Consider having it pull configurations from an splist so easy for a site owner to change the configuration parameters if needed

• CQWP caches while dataform does not
• Create as few page layouts as possible and make them as multi-purpose as possible
• Content Types

○ Reusable collection of metadata for a category of items in a splist
○ Create Content Types mainly via Sharepoint Designer (SPD) and Visual Studios (VS)
○ SPD – Pro: easy, Con: less flexible, page becomes customized
○ Visual Studio – Pro: flexible, Con: developer tool
○ Consider designing in SPD but implementing in VS

• Visual Studio plugins

http://cksdev.codeplex.com
○ Caml .net intellisense – http://bit.ly/hV4xe5

Passed 70-576: PRO Designing and Developing Microsoft SharePoint 2010 Applications

Today I passed the 70-576: PRO Designing and Developing Microsoft SharePoint 2010 Applications!

This resource definitely helped me study in the short amount of time that I had:

http://sharepointstream.com/2011/01/21/study-guide-to-the-exam-70-576-microsoft-sharepoint-2010-designing-and-developing/