Inherent Document Properties and SharePoint - does SharePoint utilize them?
This question may reveal how truly naive I am about SharePoint but here it goes.
Does SharePoint, in any way, capture a typical documents properties? See pdf uploaded. Most documents have inherant properties or metadata, does sharePoint utilize this in any way? If so, how do I display this exact metadata inherant in a document in a column or elswhere in SharePoint. Note the modified date property is not the same in SharePoint. For example, if you move a file in SharePoint it's modifed date gets revised although the document content itself (or document itself) is not modified. Do I have to re-create/add the document metadata by hand inside SharePoint. If not, where does SharePoint utilize the Document properties metadata.
Thank you for your help.
docProperties.pdf
Does SharePoint, in any way, capture a typical documents properties? See pdf uploaded. Most documents have inherant properties or metadata, does sharePoint utilize this in any way? If so, how do I display this exact metadata inherant in a document in a column or elswhere in SharePoint. Note the modified date property is not the same in SharePoint. For example, if you move a file in SharePoint it's modifed date gets revised although the document content itself (or document itself) is not modified. Do I have to re-create/add the document metadata by hand inside SharePoint. If not, where does SharePoint utilize the Document properties metadata.
Thank you for your help.
docProperties.pdf
Jamie McAllister
The data is utilised by Search. You'll find that MS Office documents and [probably] other documents with iFilters installed will have their document metadata crawled by Search and can be found via those attribute values. This is why it's good practise to add Author, Title, and Description to the e.g. MS Word document before uploading to SharePoint.
ASKER
Thank you Jamie.
Do you search by the metadata category, "Author" or for example, type in "Charles Dickens" to find Charles Dickens if, it was entered in the original document.
In the same way, could you add custom data to the document as well I suppose. Is it possible to actually use the metadata headings "Title" for example in a column heading for a site, to list the category of metadata such as "created date" or "last saved" clearly visible on a site or list for each document?
Do you search by the metadata category, "Author" or for example, type in "Charles Dickens" to find Charles Dickens if, it was entered in the original document.
In the same way, could you add custom data to the document as well I suppose. Is it possible to actually use the metadata headings "Title" for example in a column heading for a site, to list the category of metadata such as "created date" or "last saved" clearly visible on a site or list for each document?
There are 'Managed Properties' which map to crawled attributes you can search on. You get many OOTB with the product. This covers metadata such as Author and allows you to search on it. If the Author property on a Word document was specified as Charles Dickens search would find it, even though that name wasn't in the actual content.
You can create your own managed properties to extend what is searchable.
As for getting the metadata to show up in a list, I'd say you're looking at custom code. I have interrogated document metadata in code I've done before, and this technique could be used to gather the data and e.g. write it to columns in a list. I'm not aware of any OOTB way that this metadata would be made visible in a list.
You can create your own managed properties to extend what is searchable.
As for getting the metadata to show up in a list, I'd say you're looking at custom code. I have interrogated document metadata in code I've done before, and this technique could be used to gather the data and e.g. write it to columns in a list. I'm not aware of any OOTB way that this metadata would be made visible in a list.
ASKER
Thanks Jamie. what is OOTB?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.