Office Open Specifications
Office: A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.Open Specifications: Technical documents for protocols, computer languages, standards support, and data portability. The goal with Open Specifications is to help developers open new opportunities to interoperate with Windows, SQL, Office, and SharePoint.
93 questions
Hi @M-Dev ,
Thanks for your question. To help me better answer you, where did you find the
vti_replid
,vti_rtag
etc. metadata tags? Is this from a ULS log? Also, what kind of request was being made? Was it fsshttp?Best regards,
Michael Bowen
Escalation Engineer - Microsoft Open Specifications
Hi @M-Dev ,
In addition to my previous question could I also ask, what specifically do you need the metadata information for? What kind of app are you implementing?
Thanks!
Michael Bowen
Escalation Engineer - Microsoft Open Specification
Hi @Mike Bowen ,
I'm dumping all of the metadata/properties from a document using Powershell (Server Object Model). Trying to get an understanding of what some of these properties are actually pointing to.
Thanks
Hi @M-Dev ,
Thanks for the update. Could you also explain, what type of application are you working on that requires this metadata? And how does it work with the SharePoint files you read the metadata from?
Best,
Michael
Hi @Mike Bowen ,
I'm just doing an archiving tool where I can export a document from sharepoint along with all of its associated metadata at the time of export. It's just iterating over all of the fields and properties of a document and capturing it. There is a lot of metadata that is self-explanatory, but some metadata such as those I indicated are difficult to get an understanding of their true meaning.
Thanks
Sign in to comment
1 answer
Sort by: Most helpful
Hi @M-Dev
The metadata tags such as vti_replid and vti_rtag that are not described in the documentation are not necessary for interoperability. Your tool only needs to preserve them on write to successfully interoperate with SharePoint. If you find that you do need those fields to interoperate with SharePoint or they’re needed for your tool to function, please provide the specific fields needed and an explanation as to why these are needed, and we will work to define them.
For more information about how SharePoint handles metadata and which metakeys are documented, please see MS-FPSE 2.2.4.
Best regards,
Michael Bowen
Escalation Engineer - Microsoft Open Specification
Sign in to comment