Fulfilling Copy to Core Requests from Other Users
- Mojib Javadi
- Jonathan Gane
Project members cannot copy files to the Core themselves but can select files and/or folders in their Green Room folder and submit a Copy to Core request to the Project Administrator to copy the selected files to the Core. Project Administrators can approve or deny each file in the request individually, then complete the request and notify the user.
Only Project Administrators can fulfill copy to core requests. Project Members who hold a custom role with the “copy to core” permission can copy data to the Core, but cannot fulfill another Project Member’s request to copy data to the Core.
Instructions
Approve or Deny selected files
Project Administrators are notified about pending Copy to Core requests with a red notification dot on the Requests icon. The following steps describe how to review, approve, and/or deny Copy to Core requests:
Click the Requests icon from the Project left menu bar and view the tab Copy Data To Core Request.
Click New to view the new user requests that have not been fulfilled, or Completed to view requests that have been fulfilled.
Select a New request to be fulfilled and review the request details in the header. A file explorer table on the right-hand side allows you to browse through all files and/or folders that are part of the selected request and approve/deny the copy to core request on an individual file-to-file (or folder-to-folder) basis.
To approve or deny the copy to core request for an individual file or folder that is part of the Copy to Core request, select the file/folder by clicking its corresponding checkbox in the file explorer table. You can also approve or deny multiple files/folders at once by clicking all their corresponding checkboxes. The decision you make (approve / deny) will be applied to all currently selected files/folders.
When at least one file or folder is selected, two options become visible at the top of the file explorer table. Click one of the following:
Approve Selected to copy the selected files/folders to be copied to the Core.
Deny Selected if you do not wish to copy the selected files/folders to the Core.
A confirmation code is randomly generated. Type the code in the entry box to confirm your intention to Approve or Deny copying the selected files to the specified destination, then click Confirm.
Another popup confirms the action was completed. Click Close to dismiss.
After completing the above steps, the Approved files are visible in the File Explorer Core folder destination and can be accessed by all Project members with View access to the Core. Denied files are not copied.
Close the Request
After Approving or Denying every file/folder in the request, it’s time to close the request and notify the user. To close the request:
Click Close Request & Notify User.
If you haven't approved or denied all the files/folders in the request, a popup window appears reminding you to go back and approve or deny the remaining files.
If you have approved or denied all the files/folders in the request, a popup window prompts you to confirm closure of this request and enter optional Review notes that will be seen by the requester.
Click Confirm.
An email notification is sent to the requester, and the request appears in the Completed tab in the Requests panel.
After completing the above steps, the request status moves to Completed.
Considerations
Large files may take some time to copy to the Core. To view the progress, open the File Status panel in the Main Menu.
If a file with same name already exists in the destination folder in the Core, the file will be copied and a time-stamp will be appended to its filename.
If a folder with the same name (case insensitive) already exists in the destination, the files will be copied into the existing folder and a datetime string will be appended to the duplicate filenames.
The original file remains in the Green Room and a copy of the file is moved to the destination folder in the Core. The new Core file metadata and Data Lineage properties are updated:
Created - the timestamp indicating the time the copy was created.
Data Lineage Pipeline - copy - the time the file copy landed in the Core.