Modify the sync transfer app to be able to send files to the absolute path given by MyTardis 3.0 METS ingest
Currently, the MyTardis sync app determines the location for file transfer (GridFTP in synchrotron's case) to be FILE_STORE_LOCATION + EXPERIMENT_ID (eg. /var/www/mytardis/store/5)
The introduction of many-to-many dataset storage has seen a change in MyTardis' underlying file store layout. Once METS is ingested, MyTardis returns an absolute temporary directory location for files to be copied to (eg. /var/www/mytardis/tmp//). The sync app should then request that files be transferred to this location. From there, MyTardis will handle transfer into the correct location internally.
This should require a change in the MyTardis sync app (hopefully a 1-line change) with the new location rule. This change can be implemented outside of the synchrotron but would require testing with the synchrotron workflow.
Modify the sync transfer app to be able to send files to the absolute path given by MyTardis 3.0 METS ingest
Currently, the MyTardis sync app determines the location for file transfer (GridFTP in synchrotron's case) to be FILE_STORE_LOCATION + EXPERIMENT_ID (eg. /var/www/mytardis/store/5)
The introduction of many-to-many dataset storage has seen a change in MyTardis' underlying file store layout. Once METS is ingested, MyTardis returns an absolute temporary directory location for files to be copied to (eg. /var/www/mytardis/tmp//). The sync app should then request that files be transferred to this location. From there, MyTardis will handle transfer into the correct location internally.
This should require a change in the MyTardis sync app (hopefully a 1-line change) with the new location rule. This change can be implemented outside of the synchrotron but would require testing with the synchrotron workflow.
original LH ticket
This ticket has 0 attachment(s).