Forum Discussion
Venkata Ratnam Vemula
Mar 17, 2017Brass Contributor
Sharepoint Document Library- Metadata
Hi, We have a document library in which the requirement is to add 20+ custom columns (Meta data). Adding custom columns (Meta data) to document libary helps to search the documents easily by provi...
Agree with Luis, the more metadata you add to a list or a document library, the more probability you will have of experiencing performance problems when working with the list or document library
paulpascha
Mar 17, 2017Bronze Contributor
The types of columns used make a huge difference as described in the article. 20 columns of type "Single line of text" has way less impact compared to using 20 columns of type "Managed Metadata". It wasn't clear to me from the original question what types of columns where to be used...
Venkata Ratnam Vemula: by "Columns (metadata)" do you refer to the fact each colum specifies a piece of metadata or do you refer to Columns of type "Managed Metadata" here?
- Venkata Ratnam VemulaMar 18, 2017Brass Contributor
Paul,
Each column is specifies a piece of metadata not the managed meta data. Agree the user has to input more data while uploading the document.
Do we have any other alternate approaches for this requirement?
- paulpaschaMar 18, 2017Bronze ContributorYou should carefully consider if all meta data is really needed. If so, you should strive to make the end users' life as easy as possible. SharePoint provides only a few ways here that could help you out. Column default values specified at the folder level for example where the library folder you put a document in determines the default values to be used.
A custom add-in could also help in providing a better data entry experience...- kevmcdonkMar 18, 2017MVPDo you need all columns for all types? I tend to use different content types with different columns for each to reduce number of fields. You can also use lookup columns so you have one select but show more info. As Paul mentioned, definitely check the limits and limitations.