When Do I use a Multi-Field Vs. Single Field Fact


Multi-Field Facts and Single Field Facts are two different formats for storing your metadata. In this article, we will go over when a Multi-Filed Fact or a Single Field Fact is better suited for your data.

 

Multi-Field Fact (MFF)

If you have multiple pieces of interconnected data related to each document a Multi-Field Fact (MFF) and need to return that document and the data, this is the right format for you! If you just need to search by one of these elements but just need to return the document, then using multiple Single Field Facts will be your best option.


An example of interconnected data is Well Information on a lease, think of the elements of those wells:
API, Status, Well Name, and Well Number. A MFF would capture each of those elements in a separate field, as seen below.

 

Document Name

Well Info - API Well Info - Status Well Info -  Well Name
Well Info - Well Number
OGL Lease 123 123 Held Randy's Well 5
OGL Lease 123 456 Active Doug's Well 6


The table above is how the information would appear when exported, which is different from Single Field Facts.

 

Cons:

mceclip0.png

 

 

 

Single Field Facts (SFF)

Single field fact (SFF) types give you the ability to easily search and update data by the individual data points associated with the Fact. You will have a separate Fact for each kind of data (i.e. API, Well Number, Well Name, etc.). This method is best if you are managing your data point in another system and primarily using this data to aggregate searches. Having single field facts will allow you to perform bulk updates to your Well info and create Relational Libraries.

 

Cons:

  • loses the context of the other related well information.
  • More Facts to Review

mceclip1.png

 

 

 

 

 

If you have any questions or technical difficulties, you can reach out to support@thoughttrace.com

Was this article helpful?
0 out of 0 found this helpful