Root path for data policy when using a LBS or BeGFS chaching system
When using an intermediate caching system like a LBS or BeGFS system, the proposal root path is no longer
/data/id19/inhouse/......
but
/lbsram/data/id19/inhouse/.....
Changing the root path to /lbsram/data/id19/inhouse works fine to store the acquisition data (H5 file + images) on the LBS and to run the data analysis software on a dataset. When the analysis has finished, the raw data from the LBS is transferred to central storage under the path /data/id19/inhouse. The transferred data set is still fine, because the links to the images are relative links.
But, the path given to the MetadataManager is
/lbsram/data/id19/inhouse/.....
This is wrong and the archiving system will not find the path.
We need a possibility in Bliss to redirect a proposal to an intermediate storage system without breaking the data archiving from ICAT. On a BeGFS system we will find the same situation. The will have their own mount point /begfs.