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.
...
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.
...
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
Key column: Path
path,contract effective date,location,number,agreement type
/Desktop/SkySync-TestData/boxMetadataTemplate/source/test1.txt,06/01/2017,philadelphia,12345,Cloud
/Desktop/SkySync-TestData/boxMetadataTemplate/source2/test1.txt,05/01/2017,Las Vegas,54321,Written
Key columns: foldername,filename
foldername,filename,contract effective date,location,number,agreement type
subfolder,test1.txt,06/01/2017,philadelphia,12345,Cloud
...
1) Create a Copy Job, using the directory containing the "skysync_metadata.csv" file as the source
2) Add the words "-Metadata Import" anywhere within the job name, this is not case sensitive but must be present
...
5) Check the Destination to confirm metadata is present
| Info |
|---|
The files present on the Source will transfer to he destination even if the metadata transfer fails. Check the job history and skysnc_metadata-failures.csv if not all of it was moved. |