Visee Event Plan

Visee's TB/TM Event Plan is built from CSVs exported from an Excel workbook to a folder on Tate’s internal T: drive (T:\Public engagement\3 Info internal resources TB & TM\Visee\Event Plan\exports). Currently, they are then copied from via a cron job to the Visee server (tdc_infohub) at 172.16.97.29:/home/info_datafeed/source_data

The cron job on this server is run under the user info_datafeed. The crontab looks like this:

# copy files from tdc-gallery-fp3 share to local storage for Visee App
#
# Executes at 22:01 on Sunday-Wednesday and Friday-Saturday
01 22 * * 0-3,5-6 /home/info_datafeed/scripts/cp_visee_sourcedata.sh
# Executes at 11 AM on Sunday-Wednesday and Saturday
00 11 * * 0-3,6 /home/info_datafeed/scripts/cp_visee_sourcedata.sh
# Executes at 3 PM on Sunday-Wednesday and Saturday
00 15 * * 0-3,6 /home/info_datafeed/scripts/cp_visee_sourcedata.sh

The bash script cp_visee_sourcedata.sh uses the Azure CLI command azcopy to copy the csv files over to the Azure blob storage using a Shared Access Signature:

azcopy sync "/media/tdc-gallery-fp3-share/Tate Drive/Public engagement/3 Info internal resources TB & TM/Visee/Event Plan/exports/" "https://aztateprprdewdgwgtailst1.blob.core.windows.net/visee?sv=2021-06-08&ss=bfqt&srt=sco&sp=rwdlacupiytfx&se=2033-12-31T11:59:59Z&st=2023-01-01T00:00:00Z&spr=https&sig=[...REDACTED...]" --delete-destination true
azcopy sync "/media/tdc-gallery-fp3-share/Tate Drive/Public engagement/3 Info internal resources TB & TM/Visee/Event Plan/exports/" "https://aztateprdewdgwgtailst1.blob.core.windows.net/visee?sv=2021-06-08&ss=bfqt&srt=sco&sp=rwdlacupiytfx&se=2033-12-31T23:59:00Z&st=2023-01-01T00:00:00Z&spr=https&sig=[...REDACTED...]" --delete-destination true

The current signature, generated via the Azure Storage Account settings, is valid until 23:59:59 on 31 Dec 2033.