When we export data from the library, the only option is to export it to a server-wide set location. We would like the option to point the export to a different location individually for each export. This would better allow access the export location. If we had this option in automation services, we could automate backups of specific objects to different locations. Also, exports can be quite large and can take up all of our disk space. It is worrisome that anyone with export privileges could potentially export a large amount of data to our central location.
Natalie, his suggestion did help immensely! I would still like the option to be able to choose the location each time, but that is definitely a nice-to-have.
Hi Kelsey,
Did Pete's suggestion this help your issue? We also have a way to do this in the CLI, but you have to be on the server to do this.
Export-Library-Content
Import-Library-Content
Thanks,
Natalie
Ahhhhh nice, thanks! I will go change that right now! I refine my idea to individual control.
I agree that it would be nice to be able to individually control where export files are created, but there is a setting that allows you to change the default (we save ours to a network share so that all servers share a common folder):
Configuring a specific directory for library import and export