In the test environment/data is connected to a different NFS drives than in UAT and Production.
/data is where original images are stored using new OIDs or OIDs from ladybird before they are coverted to PTIFFs.
For new OIDs generated from Goobi and Preservica sources, the IDs in Test/Uat/Prod are set up so that they do not conflict.
Discussion:
Should we keep /data different in test than Uat/Prod or make it the same for all of them? - yes
Are there advantages to keeping them separate? - yes, see teams chat in DCS channel on 6/4
Details:
test mounts wcsfs00.its.yale.internal:/yul_dc_nfs_store_X_test_11212022 to /data
prod/uat mounts wcsfs00.its.yale.internal:/yul_dc_nfs_store_X to /data
"valyrie-poc" only has access to wcsfs00.its.yale.internal:/yul_dc_nfs_store_X
Acceptance Criteria
[ ] Update wiki with why and how the Test and UAT environments have different access
Background
In the test environment
/datais connected to a different NFS drives than in UAT and Production./datais where original images are stored using new OIDs or OIDs from ladybird before they are coverted to PTIFFs. For new OIDs generated from Goobi and Preservica sources, the IDs in Test/Uat/Prod are set up so that they do not conflict.Discussion:
Should we keep
/datadifferent in test than Uat/Prod or make it the same for all of them? - yes Are there advantages to keeping them separate? - yes, see teams chat in DCS channel on 6/4Details:
test mounts
wcsfs00.its.yale.internal:/yul_dc_nfs_store_X_test_11212022to/dataprod/uat mountswcsfs00.its.yale.internal:/yul_dc_nfs_store_Xto/data"valyrie-poc" only has access towcsfs00.its.yale.internal:/yul_dc_nfs_store_XAcceptance Criteria