You can create a site definition by copying and modifying an existing site definition. This task involves use of Collaborative Application Markup Language (CAML) in two schema files: one that is a copy of a WEBTEMP.XML file, and the other a copy of an ONET.XML file. It is required that you create a site definition as described in this topic rather than modifying the originally installed WEBTEMP.XML file.
- Copy the existing site definition folder located in the Local_Drive:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions60Template1033 directory.
For example, to create a custom site definition that derives from the site definition for Microsoft Windows SharePoint Services, copy the STS folder located in the 1033 directory. Name the new folder using all capital letters.
- Make a copy of the WEBTEMP.XML file located at Local_Drive:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions60TEMPLATE1033XML.
Give the file a unique name by appending a string to the name of the original file; for example, WEBTEMPACTION.XML. At run time, the compiler merges information contained in this file with the information contained in the original file in order to specify which site templates are available for creating new sites.
- Customize the contents of the new WEBTEMP file.
Each WEBTEMP.XML file contains a collection of Template elements and Configuration subelements, which identify to the compiler all the site definitions that can be instantiated. The Configuration element defines a title, a description, and a URL for the image displayed in the user interface, properties common to each Web site created using the site definition.
Important In each Template element defined in the WEBTEMP file, the Name attribute must contain the same name, in all capital letters, that is assigned to the new folder. Also, in order to avoid conflict with IDs already used in Windows SharePoint Services, use unique values greater than 10,000 for the ID attribute.
The following example defines a single site definition. The example assumes the existence of an ACTIONCOMMITTEE directory that has been created as previously described.
<?xml version="1.0" encoding="utf-8" ?> <Templates xmlns:ows="Microsoft SharePoint"> <Template Name="ACTIONCOMMITTEE" ID="98"> <Configuration ID="0" Title="Action Committee Team Site" Type="0" Hidden="FALSE" ImageUrl="images/stsprev.jpg" Description="This template provides a forum for the team to create, organize, and share information quickly and easily. It includes a Document Library, and basic lists such as Announcements, Events, Contacts, and Quick Links."> </Configuration> </Template> </Templates>
- Save the file.
- You may need to reset Internet Information Services (IIS) for the new template to appear as an option on the Template Selection page.
For a recent project, I accessed imaging requirements specific to usability (image quality) vs the footprint of the image (size). Prior to the project starting, the client had conducting image quality testing and stated that TIFFs with maximum compression and low image quality resulting in a usable image 30k in size. We conducted some testing and found that the clients tests were in accurate and their sampling of fiche was to small to represent the full spectrum.
For those without imaging experience, image format and quality settings affect the image size. For example, if you scan a letter in black and white, you could probably squeeze the file down to 30k. If you had to support grey scales the image might require 200k. Why the concern? Imagine having 20 million items to scan – 30k * 20 mil vs 200k * 20 mil. Consider this…do the math and then consider the impact on a Storage Area Network (SAN). 2 TB vs 10 TB of space – including a safety margin.
With any microfiche conversion project, the task of Fiche cleanup and scanning is quite the task. Depending on your approach it could take 2-3 years + to scan all the fiche into the Records Management System. Some client try to avoid this work by conducting a risk benefit analysis to determine the risk of not scanning all the images and just active records or the scanning of new records only – from an agreed upon date forward.
Given the range in quality due to image deterioration (some from the 70s) and photography consistency (camera operator sloppy), images are mostly yellow and shadowed. As you probably have guessed, grey scale support is required and that means a larger footprint for the image. Why? We tried TIFF with maximum compression and image pixelated and for the most part was black and not usable.
Another aspect of assessing image format is to consider the viewer required to support some of the more advanced image compression types. For example, the format JPEG within TIFF is supported by the native Windows image viewer since Microsoft doesnt license the Kodak viewer since Windows 2000.
In the end, our testing found the fiche required TIFF in JPEG compression that resulted in 200k image on average. The SAN sizing had to increase 4-5 times in size which affected the total storage required. The moral of the story? Do your testing! Take a wide sample of images from the oldest to the newest. Conduct usability testing by having users read the scanned images on a computer to verify they can be read.