Value types vs. shared properties

[noraskj]

Hey,

New to Palantir and I’m looking into a common information architecture for my space. Can anyone explain to me the differences between value types and shared properties?

Also, is it possible to use value types as codelists?

[harikrishna]

Welcome to the community!

Value Types//

• Think of value types as standardized data formats that can be applied consistently across your ontology.
• They define the structure and constraints of specific data elements, like strings, dates, numbers, or more complex types like email addresses or currency values.
• Value types ensure consistency across different objects by enforcing rules like validation, formatting, and unit standardization.
• Example: You might define a value type for CurrencyAmount that includes fields for amount, currency code (e.g., USD, EUR), and a precision level.

Can value types be used as codelists?

• Not directly. Value types are primarily about defining data structure rather than a fixed set of predefined values.
• However, you can mimic codelist functionality by defining a value type with an enumeration of allowed values, but it’s not the intended use case.

Shared Properties//

• Shared properties are attributes that can be reused across multiple object types.
• They allow you to define a property once and use it across different entities, ensuring consistency and avoiding duplication.
• Shared properties make it easier to maintain relationships and standardize key attributes across different parts of your ontology.
• Example: If multiple object types (e.g., “Employee” and “Customer”) share the concept of EmailAddress, you can define it as a shared property and apply it universally.

[9aebee43292b35f5ac9a]

@harikrishna

• Think of value types as standardized data formats that can be applied consistently across your ontology.

To tack another question onto the correct use of value types I have the following:

Object type = marine
Property = rank
Value type —> constraint type —> Enum
List of Enum:

• Private
• Private First Class
• Lance Corporal
• Corporal
• Sergeant

Action type = create new marine

Question 1) Is my rational is that I will add a constraint so that I get an extra layer of assurance on an important property necessary / in any way useful?

Question 2) I navigate to the action type —> Form —> form content —> rank—> Constraints —> multiple choice

• Is there a way to have my entire list of enum (Private, Private First Class, Lance Corporal, Corporal, Sergeant) appear in the form?
• Or will I have to select multiple choice —> define options manually?

Thanks for any help!

[noraskj]

Thank you! That makes sense. Does that also mean that you’ll need to specify several shared properties and add them to a spesific object type (which will serve as a generic/master object type) in order to emulate inherance?