Ah, now I see what you are trying to do.
Are the images identical to previous ones? Or are they new?
If they are not identical, I wonder why they are getting the same hash id?
Is the problem that different images with the same name are getting the
same hash id, or that you want the same images with the same name to be
in the collection twice?
These result in the same problem, but may have different solutions.
What platform are you on?
Diego Spano wrote:
>What a beatiful baby. Congratulations!!!!
>You are right, -keepold option process the file again, no matter if it is
>the same. But the problem is that archives.inf only maintains the last
>entry, and it should have both files. Let me explain why: we have a customer
>that every day generate a set of images image001.jpg to image100.jpg.
>Every day those 100 images are copied to import directory, so every day we
>will have the same filenames, with the only difference that after running
>import process, we clean the import folder just to get it ready to receive
>the new photos. But if import -keepold is executed, the older 100 photos
>don□t appear in archive.inf. If I use -incremental, it said: 0 documents
>were consider fro processing.
>So, I think it should be better to get an extra option for import.pl,
>something like -import_again, so for same filenames, get 2 entries in
>archive.inf. Could it be possible?
>Thanks a lot.