Metadata import allows the metadata to be added to files through the use of a .csv file. This is largely useful when individual files need individual sets of metadata to be added to them that is not already present. In our examples the Source Connector will be Network File Share and the Destination will be Box. Though it is important to keep in mind that any connector which allows metadata can be used.
Creating the import file
1) Create a .csv file named "skysync_metadata.csv" in the parent directory of the source files, or within the same directory as the source.
2) Determine the best method to identify the files having metadata added to them.
A) FileName, filename, file_name: These only require the full name of the file including its extension as the value. This should be used if the file names are not repeated throughout the structure of the data set being transferred. Example values: " file.txt, file.docx, Everyday.txt, Plans.pdf"
B) FilePath, Path, FullPath, File_Path, Full_Path: The relative or full path will need to be added as the value. This is useful if file names are repeated throughout the structure of the data set being transferred. Example values: "/Desktop/SkySync-TestData/boxMetadataTemplate/source/test1.txt, /SkySyncbox/Test/Data/test22.txt"
C) FolderName, Folder_Name,foldername: This attribute can be used in conjunction with the "FileName" attribute explained in A. Like the "Path" attribute this can be used to differentiate files that have the same name but are in different locations. Example values: "TestFolder, Boxmetdata, Copied1"
It should be kept in mind that when using a local connector the path can have /c/ however this will not work for NFS connectors.
3) The names of the remaining columns and their respective values added to the .csv file should correspond with the metadata attributes and necessary values used in the destination.
4) Once the .csv file has been created you can proceed to the job creation steps below.
Example "skysync_metadata.csv" data structures
Key column: file_name
file_name,contract effective date,location,number,agreement type
test1.txt,05/26/2017,philadelphia,12345,Cloud
test2.txt,,costa rica,12345,Europe Distributor
test4.txt,05/17/2017,seoul,12345,License
test3.txt,20150521,iceland,12345,Partner
file_name,contract effective date,location,number,agreement type test1.txt,05/26/2017,philadelphia,12345,Cloud test2.txt,,costa rica,12345,Europe Distributor test4.txt,05/17/2017,seoul,12345,License test3.txt,20150521,iceland,12345,Partner