Add custom fields (MDP)

Applies to which all objects

Define the objects for which you want to add the custom field. It can be all or one of the following:

Where does the field show

Define where the field should show. it can be any of the default sections or a custom section you have added to the pages.

The default sections are: Informational, Technical, People.

Field properties

Decide field properties such as name, type of field (single-line or multi-line), any display and edit hint text for the field, should the field always show on screen when it has no value, should the field be available for filtering search terms.

:MetadataPresentation-Custom

Yes

This is the unique identifier for the custom field. Replace custom with the name of your custom field.

:MetadataPresentation-Zipcode

rdf:type dwec:MetadataPresentation ;

Yes

This property is for internal use of the application and should be added as-is.

rdfs:label "Custom";

Yes

The name as it should appear on the UI.

Replace Custom with the label of the field you want to display on the UI.

rdfs:label "Zip code";

dwec:forType

Yes

Specify the objects for which you want to add the custom field. You can define multiple objects here.

Possible values:

_ dwec:forType dwec:DwDataset ;

_ dwec:forType dwec:Analysis ;

_ dwec:forType dwec:BusinessTerm ;

(subtypes of business terms)

_ dwec:forType dwec:Catalog ;

_ dwec:forType dwec:DatabaseTable ;

_ dwec:forType dwec:DatabaseColumn ;

_ dwec:forType dwec:_Custom* ;

dwec:inMetadataSection

Yes

Specify the section where you want to show the custom field.

Possible values:

MetadataSectionInformational

MetadataSectionTechnical

MetadataSectionPeople

MetadataSectionCustom

dwec:viaProperty

Yes

A unique internal name for the field. This is the field in which the values are stored internally in the system.

zipcode

dwec:presentationSortOrder

No

When defining multiple custom fields, define the order. If you don't define one, the fields show in alphabetical order.

2

dwec:presentationTemplate

No

Instead of just displaying the field value on the resource page, you add text around to make it more meaningful.

For example, instead of just showing 95050, you would display This 5 digit zip code is 95050.

"This 5 digit zip code is {{$1}}."

{{$1}} gets programmatically replaced by the value of the field. For example, it could look like: This 5 digit zip code is 95050.

dwec:displayHint

No

Provide a help text to give context to your users about the field when they are viewing the field values.

dwec:editHint

No

Provide a help text to give context to your users for what values they should provide while they are editing the field.

rdf:typedwec:Multiline

No

Add the field as a multiline field that supports markdown.

By default the fields are single-line and only support simple markdown syntax such as hyperlinks.

rdf:typedwec:Mandatory

No

Define if the field should always show on the Ul. When marked Mandatory, the fields always show on the resource page even when they do not have any values.

When not mandatory, the field shows on the resource page only when a value is set for the field.

Note: Custom sections show only if fields have values or if the fields included in the custom section are marked as mandatory.

rdf:typedwec:AdditionalProperty

No

For fields that are used less often, define them as additional properties so that they show as secondary field under an Add new field dropdown on the page where the field values are defined and edited.

rdf:typedwec:Facetable

No

Specify if the field should show in the search filter options so that users can use it for filtering search results.

:certified_on rdfs:range xsd:date

Use this property to provide a date picker for the date field.