Importing file metadata from a CSV file allows you to take any edited or added metadata for an item, and re-sync it with content that has already been imported into Metalogix Content Matrix. This allows you to help customize your content for migration to SharePoint. For example, you can add a set of columns to the CSV file, import these columns into Metalogix Content Matrix, and then use them to map and populate values on the SharePoint target.
To Import Items from CSV:
1.Select the top level connection node for the project connection/web content (the root node).
2.Right click and choose CSV Actions > Import Documents from a CSV File to display the CSV File dialog.
3.In the Source file field at the bottom of the dialog, either:
§enter the file path and name for the CSV file that should be imported
§ click [Browse] and navigate to the location where the CSV resides.
4.Select the applicable check box options. Use the information in the following table for guidance.
If you want to ...
ignore the internal unique ID assigned to the metadata entry (the MetalogixID field) in favor of the file path of the associated file (the SourceURL field)
Find existing Items by SourceURL, rather than MetalogixID.
NOTE: When importing data from a CSV file, Metalogix Content Matrix need to be able to identify what data goes with what item. In order to do this a synchronization is done on one column (the MetalogixID column by default) so the remaining data is correctly paired up with the item it belongs to.
This option is useful when moving metadata between Projects as the unique IDs will be different.
overwrite any existing values in a column field with a blank value, if that field already contains a non-blank value
Allow overwriting non-empty fields with empty values.
NOTE: If this option is not selected, then any fields that already contain a value will retain that same value, even if the imported CSV has a blank value for the same field.
allow for new properties (columns) to be added in the specific project connect
Allow creating new properties.
NOTE: If this option is not selected, then any new columns that have been added to the CSV file will not be added under the specific project connection node.
log details of any failures that occur when trying to import a CSV file
Enable logging for failed imports only (Recommended).
open an Import From CSV Preview dialog before the actual import action is run
Preview before importing.
NOTE: This dialog will list each column that is included in the CSV file. It will also list the column type within the CSV file and the column type in the specific connection, so you can see if there are any discrepancies. The Status column will also list if there are any mismatches in the column type between the two, or if the column types match. This gives you a chance to see if there are any potential issues for importing the content.
5.Click [OK] to start the CSV file import action.
If the Preview before importing option has been checked, the Import From CSV Preview dialog displays. After [Import] is clicked, the import process will continue.
When the CSV import starts a status box will be displayed. The logs for the import can be viewed (in progress or after the action is finished) by clicking [Details>>]. After the action has completed a note will be displayed in the bottom left corner of the dialog stating the number of records that were imported into the CSV, as well as any warnings or errors that may have been encountered (if there were any).
The imported CSV file will now update the specific project connection with its data.
You can manage the creation and changing of metadata for each source connection through the use of an internal database. This internal database can be saved for later use, or it can be exported and loaded into another source connection with similar files to transfer metadata.
To Save Metadata:
1.In Explorer View, select the source blog or Wiki root node from which you want to save metadata.
2.Right-click and choose Save Metadata As.
3.Save the file using the name and location of your choice.
NOTE The metadata will be saved as an internal database (MGR) file
The file that is created during this process is the same MRG file that is created when a source connection has been disconnected and users are prompted to save the associated metadata.
To Load Metadata:
1.In Explorer View, select the source blog or Wiki root node for the connection to which you want to load the metadata.
2.Right-click and choose Load Metadata.
3.In the Open Metabase Project File window, navigate to the location that contains the internal database file for the metadata (MGR file) to load to the for the source connection.
4.Click [Open] to load the file.
If any metadata already exist for the source connection, you will be prompted to save it to a MGR file.
The Find/Replace action allows you to search for specific values within a selected property field and either return the results of the search, or replace the searched for value with a new value. The Find/Replace action can be run on any selected node from Explorer View, or on any selected item(s) in Items View.You can only search within User Defined (Custom) columns.
To Find/Replace a Property Value:
1.Select a node in Explorer View or one or more items in Items View.
2.Right-click and choose Metadata Modifications > Find and Replace in Column to display the Search And Replace dialog.
NOTE: If no User Defined (Custom) columns exist on the source, a message will display informing you that you cannot perform a Find/Replace.
3.In the Find what field, enter the value to search for.
4.If you want to replace the value, enter the value to Replace with.
5.In the Look in field, select the column that you want to search. The drop-down is automatically populated with all of the currently available columns for which the Find/Replace can be performed.
6.Select a the Match parameter.
§Any part of Field - Each occurrence of a the search expression is replaced.
§Whole Field - If the whole field is equal to the value.
§Start of Field - Only occurrences that appear at the beginning of a property are replaced.
§End of Field - Only occurrences that appear at the end of a property are replaced.
§Regular Expression - Each occurrence that matches the regular expression is replaced.
NOTE: When you select Regular Expression as the Match type, a Multi-line check-box becomes enabled. This allows the search/replace value for both the searched for and replacement value to be multiple lines of text.
§XPath - Each node that matches the xpath query is replaced. Replacing text needs to be valid XML.
7.If you want any replaced value to be added with the same case as the value in the Replace with field, check the Match Case box to make the search/replace case sensitive and only search/replace vales that meet the exact case of the search value.
NOTE: This is available for all Match types, except for XPath.
8.Click [OK] to run the action.
When the search/replace action starts the logs can be viewed (in progress or after the action is finished) by clicking [Details>>]. After the action has completed a note will be displayed in the bottom left corner of the dialog stating the number of completions, as well as any warnings or errors that may have been encountered (if there were any).
Once complete, all of the search values will be listed in the logs, and if a value was replaced the log will indicate that there has been a change.
The Merge/Duplicate action allows you to copy one or more source property columns into a another property column. The resulting column can only be of one type, so it recommended that any property columns that are "merged" should be of the same type. For example, merging two text columns, or two date/time column, but not merging a text column with a date/time column. If merging multiple property fields or copying a single property field, the original property field(s) will still remain so that the source data will still exist on its own. The copied /merged data can be output into either another existing property field (column) or it can be placed into a new column.
To Merge/Duplicate a Column:
1.Select a folder in Explorer View, or select one or more items in Items View.
2.Right-click and choose Metadata Modifications > Merge/Duplicate Columns option to display the Copy or Merge Columns dialog.
3.In the Available Columns list, select the columns to copy or merge.
4.Use the left and right arrow buttons to move columns from the Available Columns list to the Selected Columns list. Use the up and down arrow buttons to change the order of columns in the Selected Columns list.
·Select an an existing column into which you want to merge the data from the Output Column drop-down
· Click [New] and add a new column into which to copy data.
6.The resulting data can either be placed from an existing column, selectable in the drop down menu, or from a column. Please see the Adding, Editing, Deleting, and Displaying Properties page for more details on adding a new property field.
7.If multiple property columns are being merged, enter a Separator to use between properties The default separator values are
§\t - This adds a tab space.
§\n - this creates a new line.
§\r\n - This adds a carriage return and new line.
8.Click [OK] when ready to continue.
The columns and their data will now be copied into the new or existing column using the specified settings, and the original source data will still exist in the source columns.