Path Aliases

As part of ongoing maintenence of the system, data curation activities may lead to files being renamed or moved to a different directory. This has the potential to break subsystems depending on those files being available at their original filepaths. To suport these activities, it is possible to define aliases such that any requests for data from an old filepath is automatically forwarded to the new filepath. These aliases are optionally defined in a hidden .tmaliases JSON configuration file for each backend source in the root directory. For example the following configuration:

{
     "old_file.json": "new_file.json",
     "old_path/file.json": "new_path/file.json"
}

Would lead to the following behaviour for a TMData frontend object:

• get("old_file.json") would get new_file.json

• get("old_path/file.json") would get new_path/file.json

• get_subtree("old_path").get("file.json") would get new_path/file.json