I'm using version 6.1.3. I have about 500GB of dicom files on a USB drive. I setup PacsOne to import the files and after 3 days it seem to have completed. I was able to see the studies just fine. Unfortunately the files were all left on the USB drive which was not what I needed ( I need them moved to the server on which PacsOne is installed).
1. Do I need to copy the files from the USB drive to the server before I import them?
2. If I do that what about all the entries in the data base from the last import?
Thanks
Another Import Question
1. You can run another Import job to have PacsOne Server import from the removable media drive (i.e., the USB drive) AND specify a destination folder for PacsOne to copy the imported Dicom images into.
2. You don't need to worry about the database records as they will be updated to link to the new image paths under the Import destination folder when the Import job is completed.
2. You don't need to worry about the database records as they will be updated to link to the new image paths under the Import destination folder when the Import job is completed.
I did as you suggested. I created a folder on the server and set PacsOne to import from the USB drive to the folder. It has been about 2 hrs and nothing seems to be happening. I checked the folder and there are no files yet. I also didn't see any errors. How long should I wait before I should be concerned?
Thanks
Thanks
In order to display the job status information, e.g., x% complete, PacsOne Server must read ALL files under the import source first before it can begin parsing/copying of the Dicom images. So as long as the Job Status shows Processing for the Import job, you should wait for the Import job to finish as it'll take some time to read all source files from the 500 Gb usb drive.
You can also check the CPU and memory usage of the PacsOne.exe process from the Windows Task Manager, and make sure it's busy running, i.e., CPU/memory usage growing.
You can also check the CPU and memory usage of the PacsOne.exe process from the Windows Task Manager, and make sure it's busy running, i.e., CPU/memory usage growing.