Forum Discussion

Venkata Ratnam Vemula's avatar
Venkata Ratnam Vemula
Brass Contributor
Mar 17, 2017

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 providing required criteria.

Is it good to add so many additional columns to a document library?

 

Please advise if any other best approaches are there.

  • JaredMatfess's avatar
    JaredMatfess
    Iron Contributor

    Agree with some of the fellow posters, I try to steer clients towards 3-5 columns worth of metadata at most. 3 tends to be the most common, 5 is more for strict publishing site or application that was built on top of SharePoint.

  • paulpascha's avatar
    paulpascha
    Bronze Contributor

    There are limitations around the use of columns. These are described in this article (written for SharePoint 2013 but still applicable as far as I know)

    https://technet.microsoft.com/en-us/library/cc262787.aspx?f=255&MSPPError=-2147217396#Column

     

    I don't think you will run into the technical limits described in the article above.

     

    A potential downside of this many columns is they ultimately have to be filled with data. If some person is required to fill in all those columns manually the experience might not be that good. If an automated proces is used to fill in the columns this is less of a concern. 

     

     

  • I don't think that's gonna work if you later want to show/query all the fields (like in a List View). From my experience, once I tried to add like 14 metadata columns to the Pages library. I was able to add them, but then I got errors when trying to show and item with all the columns (don't remember exactly the case, but didn't work).

     

    Metadata columns are threated like "lookup" columns, and there's a limit here:

    https://technet.microsoft.com/en-us/library/cc262787.aspx?f=255&MSPPError=-2147217396#Column

     

    List view lookup threshold

    12 join operations per query

    Specifies the maximum number of joins allowed per query, such as those based on lookup, person/group, or workflow status columns. If the query uses more than eight joins, the operation is blocked. This does not apply to single item operations. When using the maximal view via the object model (by not specifying any view fields), SharePoint will return up to the first 12 lookups.

    Note: After applying the SharePoint Server 2013 cumulative update package released on August 13, 2013 (https://support.microsoft.com/en-us/kb/2817616), the default value is increased from 8 to 12.

    • 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's avatar
        paulpascha
        Bronze 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?

Resources