Repository Specification
- Source Directory: The directory to begin crawling for BFS files.
- Do not convert metadata keys to lowercase: Federation Services converts all type and field values to lowercase by default. If this is checked all fields will keep their original case
- Process Folders: Tells the job to process to folders. If checked and the job is rerun for errors, folders will be processed again.
- Process Files: Tells the job to process files. Check by default
- Check for multi-valued fields: Will check for commas in field values. If present, they will be added as multivalued fields to the metadata
Output Specification
- Name: Name of your BFS Auth Connector
- Output Folder Path: The output directory location where your BFS files will be stored
- Multi-Value Separator: Multi-value fields will be combined into a list using this separator
- Include Un-Mapped Properties: If selected, all available properties will be included in the metadata output file. If not selected, only mapped properties will be included in file
- Inherit ACLs: If selected, inherited ACL properties will be included in the metadata output file.
- Metadata as XML: Creates a metadata XML file. If not selected, metadata will be stored in a properties file
- Zip Output: If selected, output will be created as zip files. This option can only be used with batch migrations (i.e. batch size must be greater than 0).
- Aspect Remove Field Mapping: Takes a JSON string. Remove aspects if the listed fields are not present.
The example of the UI:
{"myaspect:two":["field1","field2"],"myaspect:one":["field1","field2"]}
Meaning that if field 1 or field 2 is not present, do not add the aspects.
DateTime Config (Output)
Note: BFS as an output repository now uses the job’s Repository Time
Zone and Output Time Zone fields for time zone conversion
- Date Format: Date mappings will be converted to this ISO format
- Date Time Format: DateTme mappings will be converted to this ISO format