The Source Address for files is set in Import profiles settings and can’t be changed to a local address when creating a new Import Package.
For a global company where users are located around the world, it’s unreasonable to force users to first copy the files to a location before they can create an Import Package and it doesn't make sense to create an import profile for every location and reserve space on the local network drive for the import files to be imported in every location.
It would be more efficient if user can give the address for files to be imported, this probably means that the files should be moved to servers with author account not with server account.
An archive file (zip) is better for the user. In this case the user can upload the file from any location. No need to remember where the correct location is. This option has the same problem. Data will need to be duplicated and users never clean up anything. Anyway, out of these two options, archive file would serve our needs better.
List of import locations would not really solve the double copying problem. Files to be imported are already in some folder. Ideally they could be imported from that folder. It is not possible to list these folders because they are typically on network drives under project folders. A new project means a new path. So, the list would need frequent updates.
An archive file is better for the user. In this case the user can upload the file from any location. No need to remember where the correct location is. This option has the same problem. Data will need to be duplicated and users never clean up anything. Anyway, out of these two options, archive file would serve our needs better.
But then the issue would be that the import location must be visible to the server, which the user may not realize.
I see two options:
Allow to configure a list of import locations per import profile from which the user can choose
Allow the user to upload an archive with the file content