Create a Property Mapping Template
An import profile property mapping template is a MS Excel workbook file that contains one or more worksheets of columns for the system to look for in the metadata workbooks of the import packages. The worksheets should contain columns only and no rows. They make it easier for you to specify the property names of the import metadata instead of you having to enter the metadata fields manually in the import profile. The import data itself (rows) are provided in similar metadata workbooks of the import packages. You can download a copy of a property mapping template to give to others to fill with the document metadata to import.
The property names that are specified in the columns in the template will be shown in lists in the import profile. You select properties from these lists to map to the corresponding Meridian Enterprise properties where you want to import the metadata.
It's important that the metadata to import is saved in the workbook with the correct data types to match the destination vault property data types. Meridian Enterprise Server supports the following data types in the metadata cells:
-
Text
-
Number
-
Date/Time
-
Boolean
During import, Meridian Enterprise Server converts the data type found in the template to the correct data type of the destination property.
Review and note the following requirements pertaining to property mapping templates.
-
The References tab in the spreadsheet is mandatory.
-
The template must contain at least one worksheet and its name must be specified in the Document table option.
At a minimum, it should contain the applicable columns that are listed in the Document Key Columns group on the Key Columns page.
-
If you want to import additional properties, provide one column for each property in this worksheet and map them to the vault properties on the Property Mapping page.
-
If the documents listed in the worksheet specified for Document table contain references to other files in the import package and you want to create corresponding Meridian Enterprise references for them in the vault as they are imported, the workbook file must also contain another worksheet and its name must be specified in the Reference table option.
At a minimum, the worksheet should contain the applicable columns that are listed in the REFERENCE KEY COLUMNS group on the KEY COLUMNS page.
-
If the Rendition Format field is not included as a column, the extension of the rendition file will be used to set the rendition format.
-
If the File Type field is not included as a column, the file type will be set as the uppercased extension of the document name, concatenated with the word "File".
For example, the file type for the file ABC123.dwg would be "DWG File".
The following requirements are specific to import packages which will be imported to Meridian Portal.
-
For metadata that will be used with the Meridian Portal hierarchical lookup properties Discipline or Classification that have corresponding code properties, specify the full property name and values.
The matching code properties will be set accordingly during import.
-
Custom properties defined in Meridian Portal will be automatically included in the import profile that is exported
-
For properties that allow the selection of multiple values, the values must be enclosed by two separators, and each value must be separated by a separator.
The default separator is an asterisk, but you can also use different separator.
For example, if you were using the default separator, the format of the property values would be: *Option1*Option2*Option3* .
Supported Data Types