Tuesday, April 26, 2011
Understanding SharePoint Recycle Bin
Nice Read: http://weblogs.asp.net/jimjackson/archive/2007/10/03/sharepoint-recycle-bin-administration.aspx
Sharepoint Recycle Bin Administration
The recycle bin in Sharepoint is a 2-stage operation where the user can delete content and get it back for a configurable amount of time and then an administrator can get it back for a configurable frame after that.
User Level Recycle Bin
The first and most simple operation is just to click on the recycle bin link in the corner. Go to the list or content area where you deleted the item and click on the link. You should see the item if it hasn't exceeded its retention expiration date.
Administrative Level Recycle Bin (Site Collection Level)
If your item is not in the recycle bin or you can't find it in your content, ask an administrator to pull it from the site collection recycle bin.
To do this, click on Site Actions in the top right corner of the site and select Site Settings --> Modify All Site Settings.
On the next page, select the Recycle Bin link.
You can now select either all user's recycle bin items or the items that have been deleted from the user recycle bin.
Administering the Recycle Bin Retention Policies
So all the documentation talks about how an adminsitrator can change the retention policy for both the entire server and all users so lets look at how to do that.
Start by going to Administrative Tools in Windows. Select SharePoint 3.0 Central Administration. This opens the admin web site.
Select the Application Management tab.
Now, in the SharePoint Web Application Management section, click on Web application general settings.
Scroll all the way to the bottom of the next page and find the place to edit your Recycle Bin settings for the server.
You can turn off the recycle bins (not recommended), change the user level or the admin level recycle bin settings and then save your new values.
Sharepoint Recycle Bin Administration
The recycle bin in Sharepoint is a 2-stage operation where the user can delete content and get it back for a configurable amount of time and then an administrator can get it back for a configurable frame after that.
User Level Recycle Bin
The first and most simple operation is just to click on the recycle bin link in the corner. Go to the list or content area where you deleted the item and click on the link. You should see the item if it hasn't exceeded its retention expiration date.
Administrative Level Recycle Bin (Site Collection Level)
If your item is not in the recycle bin or you can't find it in your content, ask an administrator to pull it from the site collection recycle bin.
To do this, click on Site Actions in the top right corner of the site and select Site Settings --> Modify All Site Settings.
On the next page, select the Recycle Bin link.
You can now select either all user's recycle bin items or the items that have been deleted from the user recycle bin.
Administering the Recycle Bin Retention Policies
So all the documentation talks about how an adminsitrator can change the retention policy for both the entire server and all users so lets look at how to do that.
Start by going to Administrative Tools in Windows. Select SharePoint 3.0 Central Administration. This opens the admin web site.
Select the Application Management tab.
Now, in the SharePoint Web Application Management section, click on Web application general settings.
Scroll all the way to the bottom of the next page and find the place to edit your Recycle Bin settings for the server.
You can turn off the recycle bins (not recommended), change the user level or the admin level recycle bin settings and then save your new values.
Saturday, April 9, 2011
My First Interview Experience :-p
After Campus that is...
DotNet:
DotNet:
- Different Types of Inheritance
- How to implement Hydrid Inheritance in c sharp
- Can Getter and Setter Methods have different Access Modifiers. Meaning, Get has, say, Public and Set has Private
- What's a CLR
SharePoint:
- What is WSS
- Differences between WSS and MOSS
- What are the classes used in Custom WebPart creation
- VirtualPath Concept in MOSS. How a request is handled
- Asked about InfoPath, Excel Services, Custom WF's to which I said Pass :)
DataBase:
- What are Triggers, Cursors
- Difference between Functions and Stored Procedures
- Normalization, Different types, Why it's needed
Friday, April 8, 2011
Web Part description(.dwp) file
A Web Part description file is an XML text file with the extension .dwp. It can contain the following:
- Property names and settings for the instance of this Web Part.
- A reference to its companion Web Part assembly file (.dll).
- If a user has personalized a Web Part, changes to any common and custom property settings
When Windows SharePoint Services is first installed, a Web Part description file is often stored in the Site Web Part Gallery. Other instances of this Web Part description file are created over time as users export Web Parts, and as site administrators upload and download Web Parts.
Thursday, April 7, 2011
SharePoint Site Owner Tip: Restrict the number of versions for documents
Source: http://www.modery.net/1_moderynet_--_share-manage-govern/archive/648_sharepoint_site_owner_tip_restrict_the_number_of_versions_for_documents.html
One of the great features of SharePoint is the possibility to keep previous versions of documents and list items. This makes it easy to see who modified what when, and to also have a look back to see what was changed. Furthermore, you can also easily restore previous versions if required.
PROBLEM
The problem with versions, however, is that if you allow an unlimited amount of versions you risk that you require a lot more storage space for all these versions. To give an example: Let's say you store one document with a size of 100KB and you allow unlimited versions (Major versions only). People start to make changes, and after a while you have reached version 50. Assuming that the document still has the same size (to simplify calculations here), that would mean that this single document now uses 50 x 100KB = 5,000KB = 5MB. While 5MB doesn't sound like much, think about how many documents there are on your site, or even on your whole intranet, and what the possible impact is if unlimited versions are allowed for all of them!
SOLUTION
After you have identified a library for which versions are required, the next step is to find out how many versions are required actually. There may be cases where it is important to keep all previous versions, but usually you will rather only need to keep a few of them. For example, it may sometimes be required to be able to revert back to only the last version that existed before changes were made to a document. You could then set the restriction to 2 versions only, however this might mean that if someone saves a document twice within a short time frame you won't be able to restore the "original" document from before these changes. A number of 5 versions may be a better and slightly safer choice here.
To activate versioning, first go to the corresponding library's settings, and then follow the Versioning [[check]] link. In the section Document Version History, select either Create major versions or Create major and minor versions. Afterwards, tick Keep the following number of major versions and Keep drafts for the following number of major versions respectively and enter the appropriate numbers.
One of the great features of SharePoint is the possibility to keep previous versions of documents and list items. This makes it easy to see who modified what when, and to also have a look back to see what was changed. Furthermore, you can also easily restore previous versions if required.
PROBLEM
The problem with versions, however, is that if you allow an unlimited amount of versions you risk that you require a lot more storage space for all these versions. To give an example: Let's say you store one document with a size of 100KB and you allow unlimited versions (Major versions only). People start to make changes, and after a while you have reached version 50. Assuming that the document still has the same size (to simplify calculations here), that would mean that this single document now uses 50 x 100KB = 5,000KB = 5MB. While 5MB doesn't sound like much, think about how many documents there are on your site, or even on your whole intranet, and what the possible impact is if unlimited versions are allowed for all of them!
SOLUTION
After you have identified a library for which versions are required, the next step is to find out how many versions are required actually. There may be cases where it is important to keep all previous versions, but usually you will rather only need to keep a few of them. For example, it may sometimes be required to be able to revert back to only the last version that existed before changes were made to a document. You could then set the restriction to 2 versions only, however this might mean that if someone saves a document twice within a short time frame you won't be able to restore the "original" document from before these changes. A number of 5 versions may be a better and slightly safer choice here.
To activate versioning, first go to the corresponding library's settings, and then follow the Versioning [[check]] link. In the section Document Version History, select either Create major versions or Create major and minor versions. Afterwards, tick Keep the following number of major versions and Keep drafts for the following number of major versions respectively and enter the appropriate numbers.
Subscribe to:
Posts (Atom)