Migration problems - Digikam 1.8 to 2.0
Locked
12
12
 
|
Hi:
Can anybody help me with a detailed advice how to migrate from digikam 1.8 to digikam 2.0. I tried everything (almost) and had no luck. Either the tags are lost or I get the error message about some pid which is different from another pid. Nevertheless, I did migrations in the past, but in a way that I re-entered all the tags every time digikam got new major version. Now, the amount of pictures grew to much and I cannot do the job manually anymore. Thus, I am sure there is a way, I just need someone to show me how. Thanks. Bojan _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Migration problems - Digikam 1.8 to 2.0
|
|
Hi Bojan,
I know nothing about migration from 1.8 to 2.0. But if you have NO .RAW files in your collection I know a good work around. Write metadata to pictures, and after upgrade read metadata from pictures. This way you should have your tags back, but as said it does not work on raw. BTW. At wich point/action you get the message about PID? Rinus 2011/9/12 KrpaN <[hidden email]>
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Le Mon, 12 Sep 2011 11:26:48 +0200, Rinus Bakker
<[hidden email]> a écrit: > Hi Bojan, > I know nothing about migration from 1.8 to 2.0. But if you have NO .RAW > files in your collection I know a good work around. Write metadata to > pictures, and after upgrade read metadata from pictures. This way you > should > have your tags back, but as said it does not work on raw. > > BTW. At wich point/action you get the message about PID? > Rinus Metadata writing does work pretty correctly, even if it's presented as not recommended and experimental. After that, effectively some RAW extensions still aren't took in charge, but some others works well with metadata writing (as NEF in my case). Some bugs can occur with exiv2 which give you some frights about loosing your pictures (especially if you don't use only one software to work on your RAW), but in general cases, there's a way to get your pictures right back (it happens sometimes CaptureNX doesn't open anymore my digikam modified NEF, and after a patch applying, open their back correctly). The main thing is to make backups. -- Nicolas Boulesteix Photographe chasseur de lueurs http://www.photonoxx.fr _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Rinus Bakker
On 12. 09. 2011 11:26, Rinus Bakker wrote:
Hi Bojan,Hi: Thank you for your prompt reply. What I meant with migrating is merely an upgrade form let say digikam 1.8 to digikam 2.0. When I did such a digikam upgrade, all my tags related to the pictures I have, were lost in the new version of digikam. And it happened several times. What I want to know is how to preserve all the tags without entering upon every upgrade of the digikam software. Regards, Bojan _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Le Mon, 12 Sep 2011 11:42:57 +0200, KrpaN <[hidden email]> a écrit:
> Hi: > Thank you for your prompt reply. What I meant with migrating is merely > an upgrade form let say digikam 1.8 to digikam 2.0. When I did such a > digikam upgrade, all my tags related to the pictures I have, were lost > in the new version of digikam. And it happened several times. What I > want to know is how to preserve all the tags without entering upon every > upgrade of the digikam software. > > Regards, > Bojan What Rinus means is if you write your tag inside your pictures files (embedded in their), you don't need specifically to be able to read your old database. You just can start from scratch and digikam scans the embedded metadatas and recreates the database from this. For this you have to write the metadata in your pictures (it's mentioned as experimental for RAW files but it can work anyway depending of which kind of RAW files you use) -- -- Nicolas Boulesteix Photographe chasseur de lueurs http://www.photonoxx.fr _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by KrpaN
Il giorno 12/set/2011, alle ore 10.11, KrpaN ha scritto: > Hi: > > Can anybody help me with a detailed advice how to migrate from digikam 1.8 to digikam 2.0. I tried everything (almost) and had no luck. Either the tags are lost or I get the error message about some pid which is different from another pid. Nevertheless, I did migrations in the past, but in a way that I re-entered all the tags every time digikam got new major version. Now, the amount of pictures grew to much and I cannot do the job manually anymore. Thus, I am sure there is a way, I just need someone to show me how. Did you try to tell Digikam to save metadata inside the images? This way your tags are saved inside the images AND in you database, and you can migrate them just importing the images in the new version of the program: Digikam will re-populate your database with all your tags, Obviously writing all metadata to the images may take a lot of time (depends on the number of the images), but it's automatic and reliable, afaik. After that, you may decide to keep writing metadata to images (more security, a little less performance), or change the settings telling digikam to don't write themin images any more. good luck gerlos -- "Fairy tales are more than true, not because they tell us that dragons exist, but because they tell us that dragons can be beaten." G. K. Chesterton <http://gerlos.altervista.org> gerlos +- - - > gnu/linux registred user #311588 _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Migration problems - Digikam 1.8 to 2.0
|
|
In reply to this post by Photonoxx
On Monday, 12 September 2011 05:06:19 Photonoxx wrote:
> What Rinus means is if you write your tag inside your pictures files > (embedded in their), you don't need specifically to be able to read > your old database. > > You just can start from scratch and digikam scans the embedded > metadatas and recreates the database from this. If that is the _official_ method to upgrade, then what is the point of having a database in the first place? -- Philippe ------ The trouble with common sense is that it is so uncommon. <Anonymous> _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Migration problems - Digikam 1.8 to 2.0
|
|
This is not going to help but I'm just curious. (I might have missed
something in the conversation...) Do you really mean that you lose all your tags whenever you upgrade to a new version? I can't remember that I ever have had that problem when upgrading to a new version. /Anders 2011/9/12 Philippe Clérié <[hidden email]>: > On Monday, 12 September 2011 05:06:19 Photonoxx wrote: >> What Rinus means is if you write your tag inside your pictures files >> (embedded in their), you don't need specifically to be able to read >> your old database. >> >> You just can start from scratch and digikam scans the embedded >> metadatas and recreates the database from this. > > If that is the _official_ method to upgrade, then what is the point of having > a database in the first place? > > -- > > > Philippe > > ------ > The trouble with common sense is that it is so uncommon. > <Anonymous> > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Migration problems - Digikam 1.8 to 2.0
|
|
It has not been an issue yet, because I never bothered with tags. However, I
recently decided to bite the bullet and use them. I'm still trying to get them in my workflow. However, recent postings on the list have made me a little anxious about 2.0 or 2.1 (I am using 1.9). Hence my question. Apparently some people are having problems and the proposed work-arounds are not quite what I expected. Hope that helps. -- Philippe ------ The trouble with common sense is that it is so uncommon. <Anonymous> On Monday, 12 September 2011 14:04:29 Anders Stedtlund wrote: > This is not going to help but I'm just curious. (I might have missed > something in the conversation...) > > Do you really mean that you lose all your tags whenever you upgrade to > a new version? I can't remember that I ever have had that problem when > upgrading to a new version. > > /Anders > > 2011/9/12 Philippe Clérié <[hidden email]>: > > On Monday, 12 September 2011 05:06:19 Photonoxx wrote: > >> What Rinus means is if you write your tag inside your pictures files > >> (embedded in their), you don't need specifically to be able to read > >> your old database. > >> > >> You just can start from scratch and digikam scans the embedded > >> metadatas and recreates the database from this. > > > > If that is the _official_ method to upgrade, then what is the point of > > having a database in the first place? > > > > -- > > > > > > Philippe > > > > ------ > > The trouble with common sense is that it is so uncommon. > > <Anonymous> > > > > _______________________________________________ > > Digikam-users mailing list > > [hidden email] > > https://mail.kde.org/mailman/listinfo/digikam-users > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Migration problems - Digikam 1.8 to 2.0
|
|
2011/9/12 Philippe Clérié <[hidden email]> It has not been an issue yet, because I never bothered with tags. However, I I can not remember someone who said that.
to name one: you can have quick search, try that if all pictures have to be read while searching.
And the great happinez we all share is to think we have more of it than others do. Rinus
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Migration problems - Digikam 1.8 to 2.0
|
|
In reply to this post by Anders Stedtlund
Anders Stedtlund wrote:
> This is not going to help but I'm just curious. (I might have missed > something in the conversation...) > > Do you really mean that you lose all your tags whenever you upgrade to > a new version? I can't remember that I ever have had that problem when > upgrading to a new version. I think one of the best advantages of digital photos is that you can store data inside the image file, i.e. camera and lens information, but also comments, copyright, geo tags, etc. If you give those photos away to someone else then those people have all the information available, if you want. The advantage of using a database is that a program like digikam can search very much faster for photos which match certain criteria. In my opinion the best practice is to save all meta data inside the photos, so if your database gets corrupted for any reason you can always rebuild the database from the information inside the photos. This is also a good thing if you should sometimes decide to use a different photo management software than DK. OK, OK, this will never happen as long as DK is such an excellent program ;-)) Martin _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
CONTENTS DELETED
The author has deleted this message.
|
Re: Migration problems - Digikam 1.8 to 2.0
|
|
On Monday 12 September 2011, David Vincent-Jones wrote:
> There is however a school of thought that maintain that writing data > directly into an image file can be a source of corruption and that such > an approach to the raw image file is totally unacceptable. I am a member of this school of thought and would delete digikam immediately if it ever were to start writing such information to the original image file. If anything needs to be stored in addition to the original file it IMHO must be stored in a sidecar file with a well documented, standardized file format (XMP comes to mind) and nowhere else - a database may be a good idea as a cache but it IMHO never must become primary store for important information unless any necessary upgrade is properly managed and possible without ever losing the information in the database! regards Karl Günter _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Migration problems - Digikam 1.8 to 2.0
|
|
In reply to this post by Martin Burnicki
Hello, On Mon, 12 Sep 2011, David Vincent-Jones wrote: > There is however a school of thought that maintain that writing > data directly into an image file can be a source of corruption and > that such an approach to the raw image file is totally > unacceptable. Hum, is that a reason ? I think it's a general problem with any computer data and data handling software. From the moment one uses a software to handle data, there's always the risk the software be buggy and corrupt your data. That's sure. And the potential risk is there, whatever the data is, digital photo, text document, sound file, etc. The choice is either to do nothing with data, or to take a risk. I think raw files formats are useless if you don't produce, at one time or the other, another more useable file. What about a buggy raw converter, dcraw, ufraw, other, that produces corrupted jpeg ? Ok, you keep the raw file intact, but what else if you can't produce a jpeg ? My opinion is that the major risk of data corruption is data loss due to hard drives failures. This happens quite more often than by software corruption. (There's an excellent chapter in the digiKam handbook, "Digital Asset Management with digiKam", that states than hardware problems and human errors are far more often than software problems in data loss or corruption, in the section "What are then the main factors od digital data loss".) And the only safe workaround is backup, backup, backup... Having a file in some "read-only" mode on a disk is *not* a security. The only security is a backuped file. I don't agree with the mentionned school of thought because I think it's a wrong answer to a good question. The good question is "how can I assert my precious pictures will stay alive for a long time ?" And the wrong (IMHO) answer is "well, don't touch them". I prefer an answer such as "well, backup them and store in a safe place, then copy all on your drives and work with good software". Of course, you won't have risk zero, but you have your backups. And having a backup of raw files, as from the camera, plus a backup of hard drive directories with tagged images files doesn't appear to be a problem. Where would be the problem ? The cost of CD/DVD supports ? Tsss, how did you paid for your digital camera, lenses et al., to make your precious pictures... As for me, I don't care of data corruption on a raw file if I know my raw files, as from my SD cards, are burnt on CD/DVD. And even without writing data to my raw files, I'd do backups anyway because I reasonably trust the software I use, but I don't trust my hard drives. I *know* they will fail up in the next 3 or 4 years and I want my photos to last more than a few years. So... And, by the way, the very first metadata writer in raw images files is the camera manufacturer:-) Some camera firmware have happened to produce erroneous EXIF encoding. Should camera makers software be more trustable than digital photos management software ? Perhaps, but not sure; both are made by humans, and humans are never perfect. I fully agree with Martin when he says : > On Mon, 2011-09-12 at 23:27 +0200, Martin Burnicki wrote: > > I think one of the best advantages of digital photos is that you > > can store data inside the image file, i.e. camera and lens > > information, but also comments, copyright, geo tags, etc. Sure. And I'll go a little further, if files formats provide standards to embed metadata, EXIF, IPTC, XMP et al., it's to be used and it's useful. And keep CD/DVD backups of the original files, and work on copies on your hard drives, with metadata embedded. And you discover your software corrupts all your files because there's a severe bug in the "write metadata" routines, throw away the software and restore from backups:-) Personal or professional photos are worth a few CD/DVD supports, or even small USB drives used for archiving purposes. (And even CD/DVD supports are not eternal and should be rewritten every 3 or 4 years on fresh new supports. And USB drives should be replicated and stored in two different places, one at home and a copy at office, just in case you get fire at home. Etc.) Personal or professional data are precious, backup solutions are cheap. The only reason to refuse to write something into a raw file would be to refuse also to have a backup of the original raw file. Sounds dangerous... Martin said also : > > This is also a good thing if you should sometimes decide to use > > a different photo management software than DK. OK, OK, this will > > never happen as long as DK is such an excellent program ; -)) Right:-) But... One can also decide to use digiKam instead of another photo management software, and expect to get back images metadata. I did that, six months ago, importing into digiKam about 5000 photos with metadata. It's not straightforward because metadata standards describe very well fields formats and structure, but don't describe with the same accuracy what should be stored and where. And each software does different things. E.g. I had my images titles into the XMP Dublin Core title field, and a free text image description in the XMP DC description field. But digiKam uses the xmp.dc.description as caption for the images, and I had to move my titles from xmp.dc.title to xmp.dc.description, and save my descriptions into the unused field xmp.dc.coverage, juste because I don't want to loose it. So, having metadata in images files is a great thing, you keep information along with the image. But moving from software to software will probably always require a bit of work to extract data from some fields and rewrite into others. And it's the kind of work small shell scripts can do, using some command line metadata editors (exiftool, exiv2,... ) Even having to build such shell scripts takes far less time than reindexing, retagging hundreds or thousands of images by hand. Best, Jean-François _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Anders Stedtlund
On 12. 09. 2011 21:04, Anders Stedtlund wrote:
Yes, I always lose all My Tags when upgrading major version.This is not going to help but I'm just curious. (I might have missed something in the conversation...) Do you really mean that you lose all your tags whenever you upgrade to a new version? I can't remember that I ever have had that problem when upgrading to a new version. /Anders On the other hand, my question was probably not set properly. The real problem is: how to migrate/transfer the entire digikam scheme (pictures, My Tags etc.) from one computer to another, or in Linux, from one user to another 8same or different machines). Because, when I copy/move pictures and database from one machine to another, tags are lost. Which digikam files must be copied/moved in order to proceed further without any loss. Bojan _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Migration problems - Digikam 1.8 to 2.0
|
|
2011/9/13 KrpaN <[hidden email]>
Well, that is indeed a complete different question. I did many such migrations without any problem i.e. from one computer to another, not from user to user, but that should be not harder. I am taking here about linux, so I hope you are on linux too ############################################# locate your db´s: digikam4.db thumbnails-digikam.db and move them where you want them in your new computer open with gedit ~/.kde/shar/config/digikam.rc you will find two lines referring to your digikam database. Take care this point to the place where you moved them. do the same with your photos, store them on your new computer BUT VERY IMPORTANT take care the path looks EXCACTLY the same as on your old computer example /home/Bojan/media/photo/ this means that the name of your drive where your fotos are stored should be the same as in the former situation, else you would confuse your database. start digikam on your new computer. goto settings->configure digikam->database and point to the place where you stored it on the new computer and click ok Now it may complain about albums not found, because of a differen harddisk id or somthing. remove the albums, if they are there from settings->configure digikam->collections and re add them. Take care to add exacly the same albums as in the former situation. Now it start rereading everything, and you will probably end up with the same as you started with. Anyway it always works for me and it is easy to do. DONE! ##################################################### Now, is that common sense? Any more questions? Good luck, Rinus _______________________________________________ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
On 13. 09. 2011 10:49, Rinus Bakker wrote:
Yes, I am on Linux. And just copying directories with photos and digikam4.db never helped. There must be something else or in a different way. Writing metadata, as suggested by one guy, made no difference at all. So, any useful suggestion, that would help to keep My Tags intact, is appreciated. Bojan _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Migration problems - Digikam 1.8 to 2.0
|
|
2011/9/13 KrpaN <[hidden email]>
You should read my message more carefully, I was not talking about just copieing stuff, I explained a detailed verified procedure to you. If you encounter trouble to follow the procedure, you are invited to ask for specific help at each point. I guess, you hoped for a magic answer, there isn´t, you have just to follow the procedure. Best regards, Rinus
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
On 13. 09. 2011 11:27, Rinus Bakker wrote
OK, you are right. I somehow missed your explanation. Please accept my sincere apology. I'll try according to your instructions and let you know. Thanks, Bojan _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Rinus Bakker
On 13. 09. 2011 11:27, Rinus Bakker wrote:
Now, after doing some googleing I came across the following question. Is digikam in any weird way associated with akonadi. Because I have disabled akonadi, but whenever I run digikam the akonadi is up and running again. Bojan _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |