Sharepoint 2007 file naming conventions


















SharePoint has lots of great features, but its primary function is to allow users to create, manage, track, locate, and collaborate on data as efficiently as possible.

Often, these functions are achieved through the use of document libraries. Although document libraries are handy, I have found that a lot of administrators initially want to create a default document library, and then allow that document library to evolve as the organization's needs change and as the staff gets to be more comfortable with SharePoint.

This approach usually gets the job done, but there are other types of document libraries that can more efficiently meet a company's needs. In fact, lists are often overlooked, but are more suitable for storing some types of data than document libraries are.

In this article, I'll focus on the differences between lists and libraries and when it is appropriate to use each. I'll also cover the various types of libraries that are available, and some things you'll need to consider when planning a list or a library.

Data stored on a SharePoint server typically resides in either a list or in a library. The first step in planning a SharePoint server is to understand the differences between lists and libraries, and knowing when to use which structure.

Generally speaking, a library is used to store documents, while a list is used to store the same sorts of data that you would normally place into a spreadsheet. There are exceptions to the rule though. For instance, you can attach documents to list entries in much the same way that you can include attachments within Exchange public folders.

Both libraries and lists allow you to associate metadata with them. Typically though, metadata columns in document libraries are limited to characters of metadata per column. Therefore, if you need to include extensive notes in your metadata, you will usually be better off using a list than a document library because a list is not subject to the same metadata constraints as a library. Now that I have talked about the differences between lists and libraries, I want to talk about some of the types of libraries that are available to you.

So far, I have addressed libraries from the standpoint of a generic document library, but there are also some specialized library types that are ideally suited to storing specific types of documents.

The biggest consideration when planning SharePoint lists and libraries is the content type. As you have already seen, there are list and library types that are geared specifically to certain types of data. Dear all, Is it possible to force users to save their files in Sharepoint using a standard name system?

However, there are some problems with considering this way: 1. Therefore, Is it possible to do it using the "file name" field? Monday, June 8, PM. What are other files? Could you please for same examples?

You could change the filename to keep these files such properties. Tuesday, June 9, AM. I tried to do it and totally works for me! More Insider Sign Out. Sign In Register. Sign Out Sign In Register. Latest Insider. Check out the latest Insider stories here. Multilingual display names are stored as title resources within the field. Under the hood, this sets the title resource for the current language in which you created this column, e. Payroll ID. If you change your language preference by using the user profile service, to specify your preferred language and then rename the column, this sets this for that language.

Note: Bing Translator for illustration. With naming lists or libraries in the modern interface, be aware of the titles you are giving the libraries, for example, in the screenshot below, I have created a library called "Finance, HR, combined strategic team collaboration area", there are a few factors to consider:.

Principal author : Paul Bullock. Skip to main content. This browser is no longer supported.



0コメント

  • 1000 / 1000