Metadata is information about your document and generally known as "data about data". All the documents, folders, and workspaces metadata associated to the external systems are listed here. You can manually add metadata and assign values to the metadata to be applied to workspaces and template folders.
Field | Description | ||||||
---|---|---|---|---|---|---|---|
Metadata | Enter a name for the metadata. | ||||||
Display Name |
Enter the display name for the metadata. Make this as specific as needed to differentiate between similar metadata names that may exist. |
||||||
Data Type |
The default metadata type is displayed as String. You can change the data type to be assigned to the metadata. Options available are:
|
||||||
Parent |
Select Parent metadata to tie the metadata value and make it a dependent metadata. For e.g. Client & Matter Note: Class Metadata should be non inherited. |
||||||
Auroradb Column |
Selection required for Data Sync task The Aurora is a cloud database that will sync all the metadata to the S3 bucket during a mirror task. Select the column from the drop-down to map the metadata values with the Aurora database column names. For e.g. for a Client metadata field, if the selected Aurora database column is c1, then when running a Data Sync task the client metadata value will be replicated in the c1 column of the Aurora database. |
||||||
Unique | Select Yes to set the metadata value as a unique identifier. When a job is uploaded with a unique metadata, CAM will only modify the workspace(s) that have the unique metadata assigned. If the unique metadata does not exist in any of the existing workspace(s), CAM will create a new workspace for the uploaded job. If the metadata exists, the workspace will be skipped. | ||||||
Look Up | Select Yes to add the metadata as a look up search field in the applied external systems or workspace wizard. This will allow the user to select the value from the drop-down. | ||||||
Encrypted | The metadata can be encrypted to secure sensitive data. Select Yes to encrypt sensitive metadata. | ||||||
Is Composite |
Select Yes to mark the metadata as composite and define more attributes to the metadata. This displays two additional fields to add more details to the metadata.
Note: Database Metadata should be marked as Is Composite to No. |
||||||
Metadata Type | Select Internal if the metadata already exists in CAM. Select User Defined, if the metadata is from external systems. |
The list of information displays in the following columns:
Column Name | Description |
---|---|
Metadata | The metadata name entered above. |
Display Name |
The display name entered above. |
Data Type |
The data type assigned to the metadata. |
Parent | The parent metadata assigned. |
Unique | Is updated based on selection made when adding metadata. |
Lookup | Is updated based on selection made when adding metadata. |
Encyrpted | Is updated based on selection made when adding metadata. |
Action | Click to edit the metadata. In the Edit Metadata window, modify the metadata details and click Update. |
Manage | The option to assign value to the metadata is displayed, if Lookup option is selected when adding the metadata. Click Data to add the metadata value. In the Manage Metadata window, click the Add button. Enter a metadata value and click Save. These values can be selected when assigning unique or system metadata to the workspace or to a template folder. |
Click Edit in the Action column. In the Edit Metadata window, click the Delete button to remove the Metadata.
The search field for are displayed at the top of the page. Enter the appropriate search criteria in the search fields and click Filter. The screen refreshes, showing a list of matching results. Click to update the search results with new search criteria entered. Click x to clear the search filters.
Permissions | Allows User To |
---|---|
View Metadata | View the Metadata option in the Administration tab |
Add Metadata | Add metadata (Hides the Add Metadata button) |
Add Metadata Data | Add metadata data |
Edit Metadata | Edit metadata (Hides the Action column) |
Manage Metadata | Manage Metadata Data (Hides the Manage Column) |
Delete Metadata | Delete matter metadata (Hides Delete button in Edit Metadata dialog) |
Tip: Read here for complete list of available permissions and instructions to allow/deny CAM permissions to user/group.
What would be the process if we map the metadata first in CAM, then prepare to map the data in the external system like iManage, or NetDocuments?
When the metadata is mapped in CAM, there is a Code column and Id column that is part of the CAM mapping setup. Those will be needed for the mapping from the external system. For iManage, you take the id of the metadata field in iManage, and map it to the CAM id. For NetDocuments, you take the data fields and map them by code to the respective ones in CAM.
What is the purpose of Metadata in CAM?
The purpose of metadata is to have collected data for:
Using in CSV imports and exports: So the field tokens are passed properly to tell what data to include.
Analytics: Writing appropriate queries for returning results with the metadata that is important, then export as a CSV the data.
Question:
Why can't I see Description in the Add Metadata Mapping window from the External system (e.g. iManage)?
Answer:
In Sprint 21 and higher, description is mapped using the autodiscover feature, and the field is disabled from editing in the Add Metadata Mapping window.
Open the Actions menu on the right, and select Import Metadata or Export Metadata.
Enable the permissions Can import metadata and Can export metadata to see these options.
Export Metadata will export a CSV of the metadata in the CAM system for all.
Import Metadata allows metadata to be uploaded via CSV. This will queue a job to process it.
These are some brief examples on how to set metadata in CAM:
Setting email as the folder id (for use with email folders, or template editor): Name= email, Value= @folderid@
Setting matter id: Name=matterid, Value=@matterid@
Setting client id: Name=clientid, Value=@clientid@
Setting to create workspace in imanage: Name = CreateInImanage, Value= 0 to skip, 1= to create in imanage.
Setting to create metadata in external system like imanage etc: Name: job, Value: createmetadata
Setting system to apply metadata to: Name= Systems, Value=imanage,netdocuments
Setting up Owner metadata for provisioning: Name: Owner, Value: Owner, Type: String
These out of the box fields will begin to have automatic mapping from source to CAM. Stay tuned to the release notes and this section for updated mappings.
Source system metadata | Is Mapped To | CAM Metadata |
From | Is Mapped To | emailFrom |
Custom14 | Is Mapped To | emailTo |
Custom15 | Is Mapped To | emailCC |
Custom16 | Is Mapped To | emailBcc |
Custom21 | Is Mapped To | dateSent |
Custom22 | Is Mapped To | dateReceived |
Custom23 | Is Mapped To | d3 |
Custom24 | Is Mapped To | d4 |
Date | Is Mapped To | d8 |
AdminClient | Is Mapped To | c1 |
AdminMatter | Is Mapped To | c2 |
CloseDate | Is Mapped To | d1 - d10 |