Timeline for Saving metadata in images vs. in an external database
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 31, 2018 at 14:34 | comment | added | Sherwood Botsford | And how I wish we had a selection of good DAMs to work with. I don't know of any that come close to meeting my needs. | |
| Feb 11, 2014 at 16:29 | comment | added | Murat - Daminion Software | #1. Part of your database might be corrupted and you will not see this issue immediatelly (let's say after a week). If your backups run in the night and you'll have a problem with your database at the evening, you will loss a day work. #2. Yep, but this is an additional info about your rights, and some photo sharing sites will extract and publish your copyrights along with some other metadata information. #3. Your current DAM solution might not be in the import list of your future DAM solution let's say after 5 years. While all serious DAMs must be able to extract metadata from documents. | |
| Feb 11, 2014 at 8:56 | comment | added | user | Out of your list of advantages to storing metadata in the image file proper: #1 is covered by backups, which you'll need anyway in any sensible work flow. (Just include the database/catalog/whateveritiscalled.) #2 is moot, as metadata can easily be removed and by itself does not prevent unauthorized use (although it might make it easier to prove an image is yours if you come across it). #3 can be handled by metadata import/export functionality or third-party tools. #4 is a possible advantage. | |
| Feb 10, 2014 at 14:36 | history | answered | Murat - Daminion Software | CC BY-SA 3.0 |