|
|
Master
The Master pattern is the inverse of data aggregation patterns such as Tiered and Secure Separation. Within SharePoint, the common thought is that information is distributed throughout the workplace in sites and what you want to do is aggregate data. This is because a collaboration platform typically distributes information, so the issue appears to be the need for aggregation. This is often the case. However, in a modular architecture you can use the same components to address different
design requirements.
The master design pattern is used in situations where you do the opposite – you centralize the information in a single list in a single site and then create displays of this information anywhere in the workplace where you can work with it. In a master solution, the information is centralized and the views are distributed. You use this pattern to eliminate duplication and provide greater information integrity. This pattern starts to transform SharePoint to resemble the classic normalized database architecture.
With SharePoint data it begins with the idea of a “master” list, such as a single list for customers. There is a centrally located single list or library from a single site, with all of its data being viewed within the other sites. Only the single list needs to be maintained, as the other sites are pointed to roll–down the information. Of course, from each of the other locations you may want to be able to add, edit, and delete the information in the master site or not.
In Breeze, we also use this approach to store information within SQL Server. We store our customers and employee information in SQL Server. These “master” tables are used throughout the system.
Training Central and Approval
Breeze has a rather extensive training application. There is a central application for managing training by a Training Administrator. The Administer creates classes, reviews approvals from the departments, and manages the evaluations. There are three separate Training Approvals applications in each department: Operations, Products and Services, and Sales and Marketing. This is where the individual goes to sign up for classes and fill out evaluations and where managers approve training requests. The design is show below.
This distributed design is a classic Master pattern. The training classes reside in Training Central. The users work in the Training approval sites and use the training class master list to sign up for classes. However, the actual signup is stored in the local Training Approval site where the departmental work happens. If the Training Administrator adds, changes or removes a class in Training Central the information appearing in all Training Approval sites is immediately different.
Click here to access the Training Approval workspace in the Operations department.
Click here to access the Training Central workspace.
Global Menu Navigation
A different type of use of the Master design pattern is how we implement the Global Workplace Menu in Breeze. There is a master list that contains the global navigation. The navigation on each page then uses this master list. Thus, you have central configuration. Change it in one place and all pages changed. This is possible because the CorasWorks navigation is able to cut across sites, site collections, and web applications, thus, allowing the use of central navigation.
Below is a screenshot of the CorasWorks Management Console. This console provides the means to configure various elements of the system including the global navigation.
Click here to access the CorasWorks Management Console. Then, click on the Navigation icon.
|
|