Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Please make sure you have JAVA installed on your computer. If you don't, you can download it here: https://java.com/en/download/
  2. Download the SEAD Uploader jar file :  sead2.0.211.jar.  (1.5 Users can still use sead1.2e.jar) 
  3. For SEAD 1.5 only, request the sead-google.json file by sending an email to SEADdatanet@umich.edu.
  4. On your computer, open the root directory that contains files and folders you would like to upload to your Project Space in SEAD.
  5. Put the sead1.2e.jar file and (for 1.5) sead-google.json files in this directory.
  6. Holding the SHIFT button, right click on your mouse to open a menu. Select the "Open Command Window Here" option.
  7. Once you have the Command Window open, invoke the SEADUploader by typing the following in the Command Window:

java -cp sead1sead2.0.2e11.jar org.sead.acr.client.SEADUploader <-listonly> <-merge> <-limit<X>> <-ex<Y>> <serverUrl> <directories/files list...>

...

2.0 examples: use of the Uploader creates one Dataset with Folders and Files inside

 

java -cp sead2.0.11.jar org.sead.acr.client.SEADUploader -listonly -merge -sead2 https://sead2.ncsa.illinois.edu mydir

Using SEAD's 2.0 instance, check ./mydir and list the Dataset and all Folders and Files that would be created without the -listonly flag

java -cp sead2.0.11.jar org.sead.acr.client.SEADUploader -merge -sead2 https://sead2.ncsa.illinois.edu mydir

 Using SEAD's 2.0 instance, create a 'mydir' Dataset in your account on sead2.ncsa.illinois.edu and create Folders and Files for all contained items. Each File will be annotated with metadata indicating the original path (user metadata: "instanceOf (http://purl.org/vocab/frbr/core#embodimentOf) with the value /mydir for the mydir directory in this example and /mydir/<relative path> for all Files). Note that if this command is run without the -merge flag, it will create a new Dataset and upload all folders and files again, even if a Dataset already exists from a prior run (which is not usually what you'd want). -merge makes the Uploader check for an existing Dataset and only uploads missing content, or folders/files added to your local directory since the last upload.

java -cp sead2.0.11.jar org.sead.acr.client.SEADUploader -merge -sead2 -verify limit100 https://sead2.ncsa.illinois.edu mydir

 Using SEAD's 2.0 instance, verify that all files previously uploaded to SEAD 2 are exactly the same as those on your disk.  Since SEAD 2 currently calculates hash values with a delay, the -verify flag should be added on a second run of the Uploader.

 1.5 examples: use of the Uplaoder creates a Collection (Dataset in 2.0) with Sub-collections (Folders in 2.0) and Datasets (Files in 2.0) inside

java -cp sead1.2e.jar org.sead.acr.client.SEADUploader -listonly https://sead-demo.ncsa.illinois.edu/acr mydir

Check ./mydir and list all collections and datasets that would be created without the -listonly flag

java -cp sead1.2e.jar org.sead.acr.client.SEADUploader https://sead-demo.ncsa.illinois.edu/acr mydir

Create a "mydir" collection in the project space and create collections and datasets for all contained items. Each item will be annotated with metadata indicating the original path (user metadata: "instanceOf (http://purl.org/vocab/frbr/core#embodimentOf) with the value /mydir for the mydir directory in this example and /mydir/<relative path> for all children).

Note that if this command is run a second time, new collections and datasets will be created - probably not what you'd want. Instead use:

...

locate/create a 'mydir' Dataset in your account on sead2.ncsa.illinois.edu and create Folders and Files for the first 100 contained items. Running the command again will add the next 100 items (becasue of the -merge flag it will find/skip the ones already uploaded). 

java -cp sead2.0.11.jar org.sead.acr.client.

...

SEADUploader -merge -sead2 -verify https://

...

...

 mydir

 Using SEAD's 2.0 instance, verify that all files previously uploaded to SEAD 2 are exactly the same as those on your disk.  Since SEAD 2 currently calculates hash values with a delay, the -verify flag should be added on a second run of the Uploader.

...

This command will only create collections and datasets that have not previously been uploaded. (The "instanceOf" metadata is used to identify matching items, so starting with the same directory on your disk is required (i.e. starting up or down one directory will result in new uploads))

java -cp sead1.2e.jar org.sead.acr.client.SEADUploader -merge -limit100 https://sead-demo.ncsa.illinois.edu/acr mydir

Upload a maximum of 100 datasets (files) and only create the collections (directories) required. Using this command repeatedly (with the -merge flag) will upload the next 100 datasets, so repeated use will eventually upload all datasets, as though the limit flag had not been used. Since this mode (with -merge and -limit) requires the Uploader to check for existing files to identify where to begin, it will be slower than not using the -limit switch.

java -cp sead1.2e.jar org.sead.acr.client.SEADUploader -merge https://sead-demo.ncsa.illinois.edu/acr file1.txt file2.txt file3.txt

Upload the three listed files if the do not exist in the ACR space

 

SEAD 2.0 Authentication Process

Uploading data to SEAD 2.0 requires a local SEAD username/password (Social logins not yet supported). Each time you run the Uploader, you will be prompted for your username and password. Your password will be transmitted via https to the SEAD2 server, but no copy is stored on your local machine.

SEAD 1.5 First Time Google Authentication Process

The SEADUploader requires authentication. SEAD's google id for devices is in sead-google.json. The first time the SEADUploader is invoked, it will initiate a Google "device" authorization request for SEAD (similar to what you may have seen with Netflix or other services on your TV). The Uploader will generate a code and provide a Google URL.

...

machine

...

Once you've completed that, hit <enter> and the SEADUploader will continue and acquire a Google token it will use to authenticate you to SEAD.

...

.

Help

If you experience problems with using the SEADUploader, please contact SEAD at SEADdatanet@umich.edu and we will be happy to walk you through the steps.

...