Dataroom ExternalMetadataMap Guidelines?

I'm looking for information regarding the acceptable usage of the ExternalMetadataMap for foldering documents.

In my case I would like to persist information that is not explicitly included on the contract to the metadataMap if its acceptable.

Link to Contracts for the document types I am working with.
http://c111vcqspbd29.tlr.thomson.com/cs-api-documentation/Folders/POSTv2userfolderscontainerIditemstransactionallawitemIdapplicationjson.html

Find more posts tagged with

metadata

data

refinitiv-internal

Accepted answers

Mike Tietel

Data Room's external metadata has certain assumptions:
- It is not cross-product - other products cannot see your product's external metadata, nor can yours see theirs
- It is not searchable, filterable, or facetable
- Data Room does not touch it nor can it base any logic upon it
- Your app gets only a single metadata block and is completely responsible for maintaining it

So if your use case cannot abide by all those assumptions, external metadata might not be the right solution for you.

All comments

matt.dimich

What's the purpose of the information you want to store there? Is it specific to your product for example?

Chad Nogosek

The information will be used to generate an internal link upon retrieval. It contains information about the content type of underlying documents used to generate a "TDRReport". It shouldn't be specific to any product.

Mike Tietel

Nathan Biles

Data Room's external metadata is a Map of "String key" to "Object value" pairs, and the Map must support serialization to a JSON string. The size limit of the serialized JSON string is 200,000 characters.

EXPLORE OUR SITES