I do understand that, that's why we only move the LST file to the Monitored Folder - and have no problems with that file being moved when completed. But within the LST file are paths pointing to images on our network shares (rather than copying files into the monitored folder). And It's the fact that the agent also moves those linked files from their respective locations that is not as desirable. If the agent was able to keep the original Structure in tact, we may be able to work with that. I guess for now we will just make 2 copies, An Original, and a Temporary used for import. 

thanks for the reply.

Your request makes sense to me. I think we will address this issue in our next update. One purpose of moving referenced files is to let people know those files are archived into repository successfully. So if Import Agent moves LST file only, do you have concern about which images on your network shares are imported and which not?

I am not sure if changing profile to move referenced files into the same network shares but different folder is an option to you. As it helps you get the overall view of the archive processing.

That would be great at least an option to not move the files. I would suggest for an option of "do not move after processing" to allow for maybe a log file to be created in its place? That would represent the file had been imported properly.

As it stands now, our current work around is to basically make a copy of the files to be imported, which can be a bit cumbersome at times. 

The problem with the suggestion of Moving the referenced file to the same location is that we have a specific folder structure the files are stored in. When the files are imported & moved, they do not retain the structure. Otherwise We'd be making a new profile for every directory within the structure. 

Ex:

Parent Folder\

Child1\

File 1

File 2

File 3

Child2\

File 4

File 5

File 6

Whereas it is much easier to just make a copy of the LST file to the monitored folder and allow that to be moved. Since the size is small and there is no special structure to worry about maintaining. 

Thanks for your suggestion! We will look into the details.

As for your problem that "When the files are imported & moved, they do not retain the structure",  you are right, when people using LST file to import files, the folder structure will be not be kept. However, if you monitor the folder/files directly, the structure can be kept when moving to processed folder, which is done by using %(Subfolder) token. Do you have concern or reason you prefer LST file?