Meta-data can be imported in bulk from a local file. Four steps are required to complete a batch import operation:
- Upload: select and upload a data file from local folder;
- Configure: declare column delimitor and whether the column header (property names) is included in the file;
- Specify Header: select schema, specify property name and data type of each column, and create the properties that do not exist in the selected schema;
- Import: import meta-data from the file to the current graphset, either upsert or overwrite.
The File module in the sidebar contains a list of recent import records in the 'Import' section, in time descending order. Click the '+' to the right of 'Import', and click the metadata type to be imported:
A data file with node or edge information should be ready at this stage. Prepare a csv node file with below data for example:
Note: users can specify, or not, the _uuid of each meta-data in the file; valid file format are csv, txt, etc.
Click '+ Node' in previous step, upload the node csv file, and click 'Configure' after the upload finishes:
Set column delimitor and declare the column header of the data file. In this example, a csv file uses comma (,) as column delimitor, and the column header is included in the file. Click 'Preview' to check whether the data is parsed correctly:
Incorrect configuration of data format can be detected from the preview page. See an example of preview page resulted from a wrong configuration:
Click 'Next' and select the correct schema of the data. If new properties are recognized for the selected schema, namely there are columns that have no names or have names but are not existing in the schema, they should be set with names and selected with data types, and further be created:
When all the new properties are created, specify the insert mode (upsert/overwrite) and start the import operation:
An import operation with successful uploading procedure will be shown in the recent import list, of which the subsequent steps can be retrieved. Click 'Import' or 'Configure' of a record to recall the respective steps:
Procedure of importing edge file can be inferred from above. Note that the edge data file must contain at least the from node id and the to node id:
Corresponding to batch import, Ultipa Manager provides batch export of meta-data into csv file, with column delimited by comma (,):
One thing to mention, properties can be selected when exporting meta-data of only one schema, while all properties will be exported if exporting multiple schemas at a time.