importing images

[afx]

• what if I put some new files into the file structure?
  I have to remember for all the new files and import them?? Or just reimport the whole directory structure???

Have you ever looked at how dedicated DAMs work?

Just re-import. AS will know about the files it aready has.

[*] what if the filesystem and the database is out of sync?
It WILL happen frequently for sure, because You HAVE to poke the files with other software.[/list]

make sure the catalogs write XMPs and re-import once you are done fiddling outside...

Copying files into a catalog is broken by design....
Again, check out dedicated programs, how hey work.

cheers
afx

[Zrubi]

Have you ever looked at how dedicated DAMs work?

I've only used f-spot for jpegs, and Bibble (copy to catalog style) for RAW files...

Just re-import. AS will know about the files it aready has.

I wonder if it will be done with acceptable speed... but sure will try it.

My directory structure (booth RAW and jpeg) looks like this:

[root catalogure]
-<YYYY>
--<MM>
---<DD>

Currently I have ~10 "root catalogues", and a sum of 20~30k photos in this structure... If I just put some new files inside and reimport it will take ages to complete....

Copying files into a catalog is broken by design....

Why if its mean that making a well defined directory structure, and building the db?

Again, check out dedicated programs, how hey work.

Can you suggest me any good one running on linux?

Thanks.

[afx]

Have you ever looked at how dedicated DAMs work?

I've only used f-spot for jpegs, and Bibble (copy to catalog style) for RAW files...

Well, f-spot is not really a DAM, just a toy in the picasa class.

Currently I have ~10 "root catalogues", and a sum of 20~30k photos in this structure... If I just put some new files inside and reimport it will take ages to complete....

No need to reimport from the root.
Us the directory that fits best.

Copying files into a catalog is broken by design....

Why if its mean that making a well defined directory structure, and building the db?

No need to copy into a DB for a well defined file structure. Been using the same structure for years. Much longer than any DAM. Still works with decent DAMs. I can swap out management tools at will and the files never change....
(YYYY/MM/Project)

Again, check out dedicated programs, how hey work.

Can you suggest me any good one running on linux?

No, that's why I still run Windows ;-(

But recent versions of Digikam start to look somewhat usable.

cheers
afx

[Zrubi]

So the answer for the first question: how to import files directly from the camera/Memory card?

a, we can use the slow and "not really for this task" feature: download queue.
b, who cares, use whatever u can but not ASP.

I'm not quiet happy with this.

[afx]

So the answer for the first question: how to import files directly from the camera/Memory card?

a, we can use the slow and "not really for this task" feature: download queue.

No idea what you consider slow, but here it runs definitely barely slower than a copy via the OS.
Are you browsing the card instead of just downloading it?

cheers
afx

[Zrubi]

No idea what you consider slow, but here it runs definitely barely slower than a copy via the OS.
Are you browsing the card instead of just downloading it?

Maybe I'm missed something before... but now I'm found out how to select a folder for a batch (download) without actually browsing it :)

Also found the way to import them into a catalogue in one go :)

I'm quiet happy now ;)

[Zrubi]

I'm quiet happy now ;)

But... in case of runnig this queue again for the same card:
I only have 1 coice to not overwrite the files, but in this case instead of skipping the files already exist, this batch will put a jobname after a filename -> duplicating the files in the filesystem and also in the catalogue too :(

so we need a "skip existing files" options too...

[afx]

I'm quiet happy now

Mission accomplished

cheers
afx