Command: attribute-export

• Options: -p --project-code, -n --attribute-name

• Usage: Export an attribute from given Project by attribute name

• Output:

  • (1) Attribute Template JSON file

  • (2) Attribute Definition JSON file

• Prerequisites:

  • User login is required, otherwise error is returned: "The current login session is invalid. Please login to continue."

  • Project must be accessible to the user, otherwise, error is returned: "Project Code not found in list. Please verify and try again."

  • Requires the Project Code (retrieved via pilotcli project list).

  • Requires that the Attribute Template exists. If Attribute Template does not exist or is spelled incorrectly, the following error is returned: "Attribute 'sample-template' not found in Project. Please verify and try again."

  • pilotcli must have permission to write file in the directory

Examples

(1) Export attributes from a given Project by attribute name:

• Directly export an attribute by name from a given project

• Denoting the project options are not required in the command explicitly, however if they are not included you will be prompted to enter them

• Command structure: pilotcli file attribute-export

  • example: pilotcli file attribute-export

(2) Export attributes from a given Project by attribute name with options:

• Directly export an attribute by name from a given project, including the options in the command itself.

• Command structure: pilotcli file attribute-export -p <project code> -n <attribute template name>

  • example: pilotcli file attribute-export -p IndocTestProject -n IMG_CoreMetadata

Command: attribute-list

• Options: -p --project-code

• Usage: List all attributes from given Project

• Prerequisite:

  • User login is required, otherwise error is returned: ‘The current login session is invalid. Please login to continue.’

  • Requires the Project code (retrieved via pilotcli project list).

Examples

(1) List attributes from a given Project:

• Generate a list of attributes in any given project.

• Denoting the project options are not required in the command explicitly, however if they are not included you will be prompted to enter them

• Command structure: pilotcli file attribute-list

  • example: pilotcli file attribute-list

(2) List attributes from a given Project with options:

• Directly generate a list of attributes from a given project, including the options in the command itself.

• Command structure: pilotcli file attribute-list -p <project code>

  • example: pilotcli file attribute-list -p IndocTestProject

Command: download

• Usage: Download a file/folder from a Project using a full path: project code/folder type (users vs. shared)/folder name/file or folder name (i.e., indoctestproject/users/username/folder1/file.csv)

• Options: -z --zone, -i --geid, --zip

  • To look up a file’s geid, or unique file ID, open the Project File Explorer in the Portal and inspect the File Properties for the ID.

• Prerequisite:

  • User login is required, otherwise error is returned: "The current login session is invalid. Please login to continue."

  • File/folder must exist, otherwise error is returned: “File does not exist or source file provided is invalid: folder_name/file_name.”

  • If user has no access to the file/folder on the Portal, an error is returned: “Permission denied. Please verify that your role in the Project has permission to perform this action.”

Examples

(1) Download file/folder from Green Room

• Downloading a file/folder from Green Room with download command requires the environment variable to be configured, and pilotcli will prevent upload of duplicate file names (case insensitive). If user inputs multiple file/folder names, these files or folders will be downloaded one by one to the given directory.

• Command structure: pilotcli file download <project code>/<folder type> (users or shared)/<folder name>/<file or folder name> <file output location>

  • example: pilotcli file download indoctestproject/shared/IMG/test.csv ~/Documents

(2) Download file/folder from Core

• Use the download command to download a file/folder from Core with option -z or --zone.

• Command structure: pilotcli file download <project code>/<folder type> (users or shared)/<folder name>/<file or folder name> -z <zone> (i.e., greenroom or core) <file output location>

  • example: pilotcli file download indoctestproject/shared/IMG/test.csv -z core ~/Documents

(3) Download multiple files/folders as a compressed zip

• Use the download command to download multiple files/folders as a compressed zip file with option --zip.

• Command structure: pilotcli file download <project code>/<folder type> (users or shared)/<folder name>/<file or folder name> -z <zone> (i.e., greenroom or core) <file output location> --zip

  • example: pilotcli file download indoctestproject/shared/IMG/test.csv -z core ~/Documents
    --zip

(4) Download file/folder by geid

• Use the download command to download file(s)/folder(s) by geid with option -i --geid. The option -z --zone is not required when downloading by geid.

• Command structure: pilotcli file download -i <geid from file 1> <geid from file 2> <file output location>

  • example pilotcli file download -i 6d89afd4-f86e-4df7-b6c5-01a9af4e828e-1627499957 7e8e2bac-97c6-4738-bc08-12139c9ba225-1627498854 ~/Documents

• If the --zip option is used then command interface will automatically group input geid by the project, zone and then download as different zip files.

• Command structure: pilotcli file download -i <geid from file 1> <geid from file 2> <file output location> --zip

  • example: pilotcli file download -i 6d89afd4-f86e-4df7-b6c5-01a9af4e828e-1627499957 7e8e2bac-97c6-4738-bc08-12139c9ba225-1627498854 ~/Documents --zip

Command: list

• Options: -z --zone

• Usage: List files and folders in the directory. Folders will be displayed in blue and files will be displayed in white.

• Prerequisite:

  • User login is required, otherwise error is returned: "The current login session is invalid. Please login to continue."

  • Project must be accessible to the user, otherwise, error is returned: "Project Code not found in list. Please verify and try again."

  • Requires the Project code (retrieved via pilotcli project list) and path.

  • Requires indicating whether the folder is a shared folder or a user folder in the file path. Not denoting this will return only two options shared users

Examples

(1) List files/folders in a Green Room user folder

• List all files/folders in a Green Room folder

• -z is not required, however you must denote whether the folder is a shared folder or a user folder in the path in order to return the file/folder list

• Command structure: pilotcli file list <project code>/<folder type> (users or shared)/<folder name>

  • example: pilotcli file list indoctestproject/shared/IMG

(2) List files/folders in a Core shared folder

• List all files/folders in a Core folder

• Command structure: pilotcli file list <project code>/<folder type> (users or shared)/<folder name> -z <zone> (i.e., greenroom or core)

  • example: pilotcli file list indoctestproject/shared/IMG -z core

(3) List files/folders in Trash Bin from the Green Room

• List all files/folders in the Trash Bin from the Green Room

• Non-administrator users with access to the Trash Bin can only view the files they have moved to trash. Platform and Project Administrators can view the files in the Trash Bin from all Project members.

• Command structure: pilotcli file list <project code>/trash -z greenroom

  • example: pilotcli file list indoctestproject/trash -z greenroom

(3) List files/folders in Trash Bin from the Core

• List all files/folders in the Trash Bin from the core

• Non-administrator users with access to the Trash Bin can only view the files they have moved to trash. Platform and Project Administrators can view the files in the Trash Bin from all Project members.

• Command structure: pilotcli file list <project code>/trash -z core

  • example: pilotcli file list indoctestproject/trash -z core

Command: metadata

• Usage: Download a file’s metadata including properties, attributes, and tags.

• Options: -z --zone, -g --general, -a --attribute, -t --tag

• Output:

  • (1) attribute.json - a file containing the file’s attributes

    • { "<template_name>": { "<attribute_1>": "<value_1>", } }

  • (2) general.json - a file containing the file’s general metadata

    • #sample general.json file { "id": "40219ea6-ef6a-436a-8458-2d654b27e239", "parent": "ff009692-537b-45da-b74a-a4255adf5eec", "parent_path": "users/blasalandra", "restore_path": null, "status": "ACTIVE", "type": "file", "zone": 0, "name": "TestFile.pdf", "size": 128000, "owner": "blasalandra", "container_code": "indoctestproject", "container_type": "project", "created_time": "2024-03-20 17:28:58.365001", "last_updated_time": "2024-03-20 17:29:00.690349", "storage": { "id": "2db51316-2d7d-40a9-96a8-dfe05ca2ea2a", "version": null, "upload_id": "a353b5de-53a2-46e6-9ca8-be3dd34e5cba" }, "favourite": false }

  • (3) tag.json

    • ["tag1", "tag2", "tag3"]

• Prerequisites:

  • User login is required, otherwise error is returned: "The current login session is invalid. Please login to continue."

  • File must exist, otherwise error is returned: “File does not exist or source file provided is invalid: folder_name/file_name.”

  • If user has no access to the file/folder on the Portal, an error is returned: “Permission denied. Please verify that your role in the Project has permission to perform this action.”

(1) Download a file with general metadata, attributes, and tags.

• Download file metadata in the form of: attribute.json, general.json, tags.json

• Command structure: pilotcli file metadata -g . -a . -t . -z <zone> (i.e., greenroom or core) <project code>/<folder type> (users or shared)/<folder name>/<file or folder name>

  • example: pilotcli file metadata -g . -a . -t . -z core indoctestproject/shared/IMG/testfile.csv

Command: move

• Options: -z --zone

• Usage: Move/rename files/folders to a given Project Path within the same project

• Prerequisite:

  • User login is required, otherwise error is returned: "The current login session is invalid. Please login to continue."

  • Project must be accessible to the user, otherwise, error is returned: "Project Code not found in list. Please verify and try again."

  • Project path must include the project folder type (i.e., shared or users).

  • When moving a file to the Project Core, user must have access to the Core (Project Contributors cannot move files/folders to the Project Core).

Examples

(1) Move a file from one folder to another within a Green Room Project

• Move a file from one folder to another folder within that same project in the project Greenroom.

• When moving/renamine a file within the project Greenroom, -z is not required.

• Command structure: pilotcli file move <project code>/<origin folder type> (users or shared)/<origin folder name>/<file or folder name> <project code>/<destination folder type> (users or shared)/<destination folder name>

  • example: pilotcli file move indoctestproject/shared/IMG/test.csv indoctestproject/users/blasalandra/

(2) Move a file from one folder to another within a Core Project

• Move a file from one folder to another folder within the same project in the project core zone.

• Command structure: pilotcli file move <project code>/<origin folder type> (users or shared)/<origin folder name>/<file or folder name> <project code>/<destination folder type> (users or shared)/<destination folder name> -z <zone> (i.e., greenroom or core)

  • example: pilotcli file move indoctestproject/shared/IMG/test.csv indoctestproject/users/blasalandra -z core

(3) Rename a file in a Green Room folder

• Rename a file from the command line using the move command.

• Command structure: pilotcli file move<project code>/<folder type> (users or shared)/<folder name>/<original file or folder name> <project code>/<folder type> (users or shared)/<folder name>/ <new file or folder name>

  • example: pilotcli file move indoctestproject/shared/IMG/test.csv indoctestproject/shared/IMG/newfile.csv

Command: resume

• Options: -td --thread, -r --resumable-manifest

• Usage: Upload unfinished file/folder uploading based on the resumable upload file (resumable_upload_log.json)

• Prerequisite:

  • User login is required, otherwise error is returned: "The current login session is invalid. Please login to continue."

  • Project must be accessible to the user, otherwise, error is returned: "Project Code not found in list. Please verify and try again."

  • Resumable upload manifest file is required, which is generated from using the file upload command (see example 10 above) [default: ./resumable_upload_log.json]

Examples

(1) Resume the upload with resumable upload file (resumable_upload_log.json)

• The resumable command uses the manifest file generated from file upload to resume all uploads

• Command structure: pilotcli file resume -r <resumable manifest json file>

  • example: pilotcli file resume -r ~/Documents/resumable_upload_log.json

Command: upload