Join Mongo Document Metadata
The purposes of this task is to retrieve metadata from an outside mongo database during a migration, adding it to the repository document before mappings are performed.
This task is called a “join” because it checks for a value on both the Repository Document and in the Mongo Document.
- The checked field on the Repository Document can be either a standard field mapping, or it can be calculated using the Expression Language (see Federation Services Expression Language).
- If either checked field is missing, the process will be skipped.
- If the values of the checked field matches, the comma delimited list of fields will be added from the Mongo Document, in lowercase.
- They can then be added as normal field mappings in a job mapping, as Field mappings take place after Tasks.
- This task supports multiple fields to check on the Mongo document and repository document
- Users can sort the order in which the fields are checked
Fill in the following fields to configure this task. Some fields come with default configurations. Update them as necessary.
- Task Name
- The fields you’re checking for on the mongo document (comma separated)
- Default: doc_id,doc_name
- The fields you’re checking for on the repository document
- ’#{rd.id}’
- ’#{rd.filename}’ Each line contains one field. The number of fields must match the ones you are checking on in the Mongo document.
- Comma delimited list of fields to add to the repository documents, should the fields match
- Mongo field to be used for sorting followed by a comma and sort order
- docCreated:1 The Sort order can be +1 for ascending or -1 for descending.
- The MongoDB Url
- localhost
- The Mongo Port
- 27017
- The mongo database to query
- admin
- The mongo collection to query
- collection
- The mongo user, leave blank if no authentication is set
- The mongo password, leave blank if no authentication is set
Metadata Extraction - EML
An EML file is an email message saved by an email application, such as Microsoft Outlook or Apple Mail. It contains the content of the message, along with the subject, sender, recipient(s), and date of the message. EML files may also store one or more email attachments, which are files sent with the message.
This task extracts metadata from emails and adds as fields to the repository document. These extracted fields appear as:
- Email.Subject: The subject line of the email.
- Email.From: The ‘from’ line of the email.
- Email.To: The ‘to’ line of the email.
- Email.Body: The body of the email.
- Email.CC: The CC line of the email.
- Email.BCC: The BCC line of the email.
- Email.EmailList: Space separated list of To, From and CC addresses.
- Email.InternetMessageId: The message ID of the email.
- Email.Size: The size of the email.
- Email.HasAttachments: Whether the email has attachments or not.
- Email.Attachments: Comma delimited list of email attachments by name. Blank if none.
- Email.AttachmentCount: The number of attachments in this email.
- Email.DateTimeSent: The date time the email was sent.
- Email.DateTimeCreated: The date time the email was created.
- Email.LastModifiedTime: The modified date time of the email.
- Email.DateTimeReceived: The date and time the email was received.
Metadata Extraction - Path
This task will extract the metadata from the file and add it as fields to the repository document.
Configuration-
Path Field: Which field to use to extract metadata.
Options are:
- Repository ID (for repos that use the entire path as an ID, such as Filesystem, or Amazon S3)
- Parent Path, for repos that don’t use paths as ID.
-
Path Rules: Comma delimited list of rules to extract. The
format is [New Field Name]=#{Location}:
- Location takes the form of an integer, starting at 0 for the root folder.
- Additionally, 'filename','parent',and 'grandparent' with **quotes included can be used.
Output Metadata As JSON
This task fully converts each document to a json object and exports to it to the configured path on the local filesystem where 3Sixty is running.
- Output Path: Folder where the json files will be written. Path will be created if it does not exist.
File name pattern = [filename].document.metadata.json
Folder name pattern = [foldername].folder.metadata.json
Replace Metadata
This task will perform a Regex search on the configured metadata field and replaces it with supplied text.
- Source Metadata Field: The field to check.
- Regex to Match: A regular expression to use as the first argument of a Java String.replaceAll() method.
- Replacement Text: The text to use as the second argument of the replaceAll() method.
Metadata from Properties File - Filesystem
If there is a separate properties file then 3Sixty will get the metadata from that file. This only works for a File Systems connector. Configure this task by completing the following fields.
- Properties filename
- Skip files with no property file found in hierarchy