Page History
...
Place your data files (i.e. the completed templates) in a directory of your choice, e.g.
dataDirectory
. All files contained in this directory will be processed by the ETLer.To run an ETL, execute one of the two commands below.
- A detailed report of the ETL results is generated in the
./logs
directory; please inspect it to verify that all rows were correctly uploaded. The RDF version of generated resources is also logged in this directory. - To further verify the data upload, log on to the SWEET application and select the lab to which the ETLd resources belong.
Code Block | ||||
---|---|---|---|---|
|
...
Code Block | ||
---|---|---|
| ||
./ETLer.sh -d dataDirectory [-p DRAFT|CURATION|PUBLISH] -c username:password -r repositoryURL |
- This command will not attempt to determine if matching resources exist already in the eagle-i repository; it is therefore not idempotent - if it is run two times with the same data file, duplicate resources will be created.
- The value of the
-p
(promote) parameter indicates the desired workflow state for all resources - we recommend to choose CURATION, verify the resources were ETLd correctly, and then publish using the bulk workflow command (see below). If you've already ran a test ETL in a staging environment, choose PUBLISH directly.
Code Block | ||||
---|---|---|---|---|
|
...
|
...
Code Block | ||
---|---|---|
| ||
./ETLer.sh -d dataDirectory [-p DRAFT|CURATION|PUBLISH] -c username:password -r repositoryURL -eid property-uri |
...
Overview
Content Tools