PCT303 – Content Publishing in SharePoint Eugene Rosenfeld Black Blade Associates

Overview Address the requirements for list and library content publishing Cover the intricacies of publishing content from one list or library to another within or across sites Tricks for maintaining the state of the publication for managing the link and refreshing changes to content.

Requirements – User Transparent interaction with items – published items, non published items Interface to define a source item and target location N-level publishing Manually force updating the target Automatically updating the target Scheduled Event based update

Requirements – Content Managers Interface to define possible publishing location Comprehensive list of target locations items have been published to Ability to revoke publications Ability to approve and reject publications Relate published and non published items to one another Detecting changes to the target items Conflict resolution

Requirements – Administrators Simple application deployment Simple backup and restore Publication auditing Reporting Security

Technical Approach There are 3 – 4 main pieces User interface Synchronization engine Reporting mechanism Service interface Keeping the components separated enhances code reusability and extensibility

Technical Approach - UI Web part Can not perform excessively long transactions before browser times out request Web from Can not perform excessively long transactions before browser times out request Added deployment complexity to the server Widows app Deployment complexity to client machines Cannot use SharePoint object model

Technical Approach - Synchronization Client based - handled by web part, web form, or Windows form Windows service Event triggers

Technical Approach - Reporting Reporting web part SQL Reporting Services reports Business Score Cards (OLAP)

Technical Approach – Service Interface HTTP Get / Post interface SOAP interface File system interface Message Queue interface

Maintaining State Location of state affects: Application deployment complexity Application runtime complexity Application management Security Backup and restore

Technical Approach – What Works UI Connected web part implementing RowConsumer interface Synchronization Initiate synchronization from web part Windows service that polls for changes in published items Web part contains UI for conflict resolution Reporting Basic reporting can be accomplished with OOTB list view web parts or DataViews State Storage Publishing state is most easily stored with the lists whose items are to be published We need to track where a list item was intended to be published and where it was actually published

Questions Eugene Rosenfeld Black Blade Associates