Warning, /documentation/digikam-doc/locale/de/LC_MESSAGES/asset_management/data_protection.po is written in an unsupported language. File is not indexed.
0001 # German translations for Digikam Manual package. 0002 # Copyright (C) licensed under the <a href="https://creativecommons.org/licenses/by-sa/4.0/">Creative Commons License SA 4.0</a> unless stated otherwise 0003 # This file is distributed under the same license as the Digikam Manual package. 0004 # Automatically generated, 2023. 0005 # 0006 msgid "" 0007 msgstr "" 0008 "Project-Id-Version: Digikam Manual 8.0.0\n" 0009 "Report-Msgid-Bugs-To: \n" 0010 "POT-Creation-Date: 2023-12-30 00:35+0000\n" 0011 "PO-Revision-Date: 2023-01-01 12:31+0100\n" 0012 "Last-Translator: Automatically generated\n" 0013 "Language-Team: none\n" 0014 "Language: de\n" 0015 "MIME-Version: 1.0\n" 0016 "Content-Type: text/plain; charset=UTF-8\n" 0017 "Content-Transfer-Encoding: 8bit\n" 0018 "Plural-Forms: nplurals=2; plural=(n != 1);\n" 0019 0020 #: ../../asset_management/data_protection.rst:1 0021 msgid "Protect Your Images from Data Corruption and Loss" 0022 msgstr "" 0023 0024 #: ../../asset_management/data_protection.rst:1 0025 msgid "" 0026 "digiKam, documentation, user manual, photo management, open source, free, " 0027 "learn, easy, disk errors, disk failures, power surges, ECC, transmission " 0028 "errors, storage media deterioration, recovery, redundancy, disaster " 0029 "prevention, lifetime, temperature, data size, common myths, metadata, IPTC " 0030 "stored in image files, XMP files associated, keep the originals, storage, " 0031 "scalability, media, retrieval of images and metadata, copying image data " 0032 "over to the next generation of media, applications, operating systems, " 0033 "virtualization, viewing device, use of the www, ZFS, BTRFS" 0034 msgstr "" 0035 0036 #: ../../asset_management/data_protection.rst:14 0037 msgid "Data Corruption and Loss" 0038 msgstr "" 0039 0040 #: ../../asset_management/data_protection.rst:16 0041 msgid "Contents" 0042 msgstr "" 0043 0044 #: ../../asset_management/data_protection.rst:19 0045 msgid "Main Factors of Digital Data Loss" 0046 msgstr "" 0047 0048 #: ../../asset_management/data_protection.rst:21 0049 msgid "" 0050 "Of course we're not talking about losing Blue-rays on the road or in a fire " 0051 "- that kind of loss is just the same as traditional paper copies or " 0052 "negatives. We are talking about problems with the so called *New Media*." 0053 msgstr "" 0054 0055 #: ../../asset_management/data_protection.rst:23 0056 msgid "" 0057 "Problems with digital data can roughly be categorized into the following " 0058 "areas of concern:" 0059 msgstr "" 0060 0061 #: ../../asset_management/data_protection.rst:25 0062 msgid "" 0063 "The physical deterioration of the media (all media deteriorate at different " 0064 "time scales)." 0065 msgstr "" 0066 0067 #: ../../asset_management/data_protection.rst:27 0068 msgid "Undetected transmission errors during data transfer." 0069 msgstr "" 0070 0071 #: ../../asset_management/data_protection.rst:29 0072 msgid "" 0073 "The lack of support for long-date, undoubtedly proprietary, digital formats." 0074 msgstr "" 0075 0076 #: ../../asset_management/data_protection.rst:31 0077 msgid "Ancient hardware." 0078 msgstr "" 0079 0080 #: ../../asset_management/data_protection.rst:33 0081 msgid "" 0082 "Kroll Ontrack, the worlds largest data recovery firm, have some interesting " 0083 "statistics on what actually causes data loss." 0084 msgstr "" 0085 0086 #: ../../asset_management/data_protection.rst:36 0087 msgid "Cause of data loss" 0088 msgstr "" 0089 0090 #: ../../asset_management/data_protection.rst:36 0091 msgid "Perception" 0092 msgstr "" 0093 0094 #: ../../asset_management/data_protection.rst:36 0095 msgid "Reality" 0096 msgstr "" 0097 0098 #: ../../asset_management/data_protection.rst:38 0099 msgid "Hardware or system problem" 0100 msgstr "" 0101 0102 #: ../../asset_management/data_protection.rst:38 0103 msgid "78%" 0104 msgstr "" 0105 0106 #: ../../asset_management/data_protection.rst:38 0107 msgid "56%" 0108 msgstr "" 0109 0110 #: ../../asset_management/data_protection.rst:39 0111 msgid "Human error" 0112 msgstr "" 0113 0114 #: ../../asset_management/data_protection.rst:39 0115 msgid "11%" 0116 msgstr "" 0117 0118 #: ../../asset_management/data_protection.rst:39 0119 msgid "26%" 0120 msgstr "" 0121 0122 #: ../../asset_management/data_protection.rst:40 0123 msgid "Software corruption or problem" 0124 msgstr "" 0125 0126 #: ../../asset_management/data_protection.rst:40 0127 msgid "7%" 0128 msgstr "" 0129 0130 #: ../../asset_management/data_protection.rst:40 0131 msgid "9%" 0132 msgstr "" 0133 0134 #: ../../asset_management/data_protection.rst:41 0135 msgid "Computer viruses" 0136 msgstr "" 0137 0138 #: ../../asset_management/data_protection.rst:41 0139 msgid "2%" 0140 msgstr "" 0141 0142 #: ../../asset_management/data_protection.rst:41 0143 msgid "4%" 0144 msgstr "" 0145 0146 #: ../../asset_management/data_protection.rst:42 0147 msgid "Disaster" 0148 msgstr "" 0149 0150 #: ../../asset_management/data_protection.rst:42 0151 msgid "1-2%" 0152 msgstr "" 0153 0154 #: ../../asset_management/data_protection.rst:45 0155 msgid "So let us analyze those cases step by step." 0156 msgstr "" 0157 0158 #: ../../asset_management/data_protection.rst:50 0159 msgid "Storage Deterioration" 0160 msgstr "" 0161 0162 #: ../../asset_management/data_protection.rst:52 0163 msgid "" 0164 "Devices listed below are sorted by data speed access feature, from the less " 0165 "faster to the most faster." 0166 msgstr "" 0167 0168 #: ../../asset_management/data_protection.rst:55 0169 msgid "Magnetic Media" 0170 msgstr "" 0171 0172 #: ../../asset_management/data_protection.rst:57 0173 msgid "" 0174 "Magnetic tapes are used in backup systems, much more in professional " 0175 "environments than in home use. Tapes have issues with data retention and " 0176 "changing technology, but they are safer in one aspect than optical drives: " 0177 "they are less exposed to scratches and dirt and writing deficiencies. On the " 0178 "other hand they are susceptible to magnetic fields. Throw a magnet next to a " 0179 "tape and it's gone. Tapes should be re-copied every 5-8 years, otherwise too " 0180 "many bits will fail and escape the checksum protection. The downside of " 0181 "magnetic tapes is often the recorder price and the restore time (20x longer " 0182 "than from HDD). Tape backup system have seen their best days." 0183 msgstr "" 0184 0185 #: ../../asset_management/data_protection.rst:60 0186 msgid "Optical Drives" 0187 msgstr "" 0188 0189 #: ../../asset_management/data_protection.rst:62 0190 msgid "" 0191 "Physical deterioration of the media happens more rapidly with paper and CD-" 0192 "Rs than the average of film. Yet while film lasts longer (sometimes decades " 0193 "longer) than other forms of media, the right kind of backup of digital media " 0194 "never loses anything. Film decays - digital 1's and 0's do not, and film " 0195 "starts to decay the moment it's created and developed. It will never have " 0196 "the same color, contrast, etc. that it did have a moment before. Digital " 0197 "doesn't do that. However, digital is susceptible to corruption. And yes, " 0198 "physical media such as floppies and magnetic hard drives are also " 0199 "susceptible to the decay of the medium, just like CDs are. They just last " 0200 "longer." 0201 msgstr "" 0202 0203 #: ../../asset_management/data_protection.rst:64 0204 msgid "" 0205 "To combat the problem of optical drives, they need to be properly cared for " 0206 "and not trusted for more than a few years. Thankfully you can purchase " 0207 "archive-quality CDs and DVDs which last longer, though they are much more " 0208 "difficult to obtain and are much more expensive. There are offers out there " 0209 "for gold-plated optical drive, few euros a piece claiming 100 years storage " 0210 "life (if you care to believe it)." 0211 msgstr "" 0212 0213 #: ../../asset_management/data_protection.rst:66 0214 msgid "" 0215 "Optical disks may become unreadable, but you can reduce the risk using good " 0216 "disks and a good recorder, and storing them in a correct way. The best " 0217 "optical drive recorders are not much more expensive than the cheapest, but " 0218 "they write in a much more reliable way. It's a matter of choosing the right " 0219 "one." 0220 msgstr "" 0221 0222 #: ../../asset_management/data_protection.rst:68 0223 msgid "" 0224 "Essentially, optical drives are very prone to errors, even in a freshly " 0225 "written state. That's why they are heavily protected with a checksum " 0226 "mechanism (75% of data are effective data, the rest is formatting and " 0227 "checksum overhead). But even with that massive amount of protection they " 0228 "will suffer deterioration from chemical aging, ultra-violet exposure, " 0229 "scratches, dust, etc." 0230 msgstr "" 0231 0232 #: ../../asset_management/data_protection.rst:70 0233 msgid "" 0234 "For damaged optical drives, Wikipedia `list all common applications <https://" 0235 "en.wikipedia.org/wiki/Data_recovery#List_of_data_recovery_software>`_ " 0236 "designed to get data from damaged floppies, hard drives, flash media such as " 0237 "camera memory and USB drives, and so forth." 0238 msgstr "" 0239 0240 #: ../../asset_management/data_protection.rst:72 0241 msgid "" 0242 "Dual-layer optical media Blu-ray disk can store 50 GB, almost six times the " 0243 "capacity of a dual layer DVD at 8.5 GB. Everything that has been said about " 0244 "CDs/DVDs applies to Blu-ray disks as well." 0245 msgstr "" 0246 0247 #: ../../asset_management/data_protection.rst:74 0248 msgid "" 0249 "Best practice: burn them slowly with a good recorder on archive quality " 0250 "media in an open, non-proprietary format, read the data back to verify, " 0251 "label them with some descriptive text + date & author, lock them away where " 0252 "it is clean, dark, animal safe and dry. And do not forget to copy them over " 0253 "to the next generation of media before you throw away your last piece of " 0254 "hardware or software able to read them." 0255 msgstr "" 0256 0257 #: ../../asset_management/data_protection.rst:77 0258 msgid "Hard Disks" 0259 msgstr "" 0260 0261 #: ../../asset_management/data_protection.rst:79 0262 msgid "" 0263 "Hard Disk (HDD) manufacturers keep their statistics to themselves. A " 0264 "manufacturer guaranty buys you a new disk, but no data. Google for One has " 0265 "done a large scale study on `HDD <https://en.wikipedia.org/wiki/" 0266 "Hard_disk_drive>`_ failure mechanisms: `Disk Failures study <https://" 0267 "research.google.com/archive/disk_failures.pdf>`_." 0268 msgstr "" 0269 0270 #: ../../asset_management/data_protection.rst:81 0271 msgid "" 0272 "In a nutshell: Disks run longest when operating between 35°C and 45°C, at " 0273 "lower temperatures the error rates increases dramatically. Controller parts " 0274 "(electronics) are the foremost sources of failure, SMART does not diagnose " 0275 "any of this. Some `SMART <https://en.wikipedia.org/wiki/Self-Monitoring," 0276 "_Analysis_and_Reporting_Technology>`_ errors are indicative of imminent " 0277 "failure, in particular scan errors and relocation counts. Lifetime " 0278 "expectancy is 4-5 years." 0279 msgstr "" 0280 0281 #: ../../asset_management/data_protection.rst:83 0282 msgid "" 0283 "In general and contrary to intuition or ecological considerations, running a " 0284 "hard drive permanently results in a longer lifetime than switching it on and " 0285 "off all the time. It has even been reported that aggressive power management " 0286 "spinning down the drive can harm it quickly. Making it working hard shortens " 0287 "the lifetime somewhat. The worst factors for HDD probably are vibrations, " 0288 "shocks, and cold temperatures." 0289 msgstr "" 0290 0291 #: ../../asset_management/data_protection.rst:85 0292 msgid "" 0293 "If your disk is making weird noises, normal file recovery software isn’t " 0294 "going to work. Do a quick backup if that is going to happen to you. (Use dd " 0295 "utility if possible, not a normal file backup since dd reads in a smooth, " 0296 "spiraling stream from beginning to end and doesn't stress the mechanics). " 0297 "There are specialist companies that can recover data from otherwise " 0298 "destroyed drive, but they are very expensive." 0299 msgstr "" 0300 0301 #: ../../asset_management/data_protection.rst:87 0302 msgid "" 0303 "Linux `SmartMonTools <https://en.wikipedia.org/wiki/Smartmontools>`_ suite " 0304 "allows to query the storage hardware devices for future failure. We highly " 0305 "recommend to use this kind of tool on your computer." 0306 msgstr "" 0307 0308 #: ../../asset_management/data_protection.rst:90 0309 msgid "Solid State Drives" 0310 msgstr "" 0311 0312 #: ../../asset_management/data_protection.rst:92 0313 msgid "" 0314 "`SSDs <https://en.wikipedia.org/wiki/Solid-state_drive>`_ are mechanically " 0315 "more robust than HDDs and suffer much less on that front when they are " 0316 "plugged into the computer. They will replace HDD in time as capacity, " 0317 "robustest, and price become more and more a good solution as permanent data " 0318 "storage devices." 0319 msgstr "" 0320 0321 #: ../../asset_management/data_protection.rst:94 0322 msgid "" 0323 "In case of use as external device, one major cause for data loss (often " 0324 "recoverable) is the unsafe removal of SSDs from a computer. Before data is " 0325 "saved from a computer memory to any attached device, it remains for some " 0326 "time in buffers. In hard drives this means seconds at most, whereas with " 0327 "SSDs it can be tens of minutes. Therefore, before you disconnect a flash " 0328 "device, always activate data flushing through software (often called *safely " 0329 "remove device*)." 0330 msgstr "" 0331 0332 #: ../../asset_management/data_protection.rst:97 0333 msgid "Non-Volatile Memory" 0334 msgstr "" 0335 0336 #: ../../asset_management/data_protection.rst:99 0337 msgid "" 0338 "`NVM Express (NVMe) <https://en.wikipedia.org/wiki/NVMe>`_ for Non-Volatile " 0339 "Memory is a logical-device interface for accessing a computer's non-volatile " 0340 "storage media attached PCI Express (PCIe) bus. It use same very fast NAND " 0341 "flash memory used in SSDs, but use the M.2 cards interface instead the " 0342 "slower mSATA used with older HDDs." 0343 msgstr "" 0344 0345 #: ../../asset_management/data_protection.rst:101 0346 msgid "" 0347 "NVMe allows host hardware and software to fully exploit the levels of " 0348 "parallelism possible in modern SSDs. NVMe reduces I/O overhead and brings " 0349 "various performance improvements relative to previous SSDs. mSATA interface " 0350 "protocols were developed for use with far slower HDDs where a very lengthy " 0351 "delay exists between a request and data transfer, where data speeds are much " 0352 "slower than RAM speeds." 0353 msgstr "" 0354 0355 #: ../../asset_management/data_protection.rst:103 0356 msgid "" 0357 "For a viability viewpoint, as NVMe devices uses the same hardware than SSDs " 0358 "to store data, the robustness must be the same." 0359 msgstr "" 0360 0361 #: ../../asset_management/data_protection.rst:107 0362 msgid "" 0363 "**In all cases SSDs or NVMe as internal devices are the more modern and " 0364 "efficient solution to host the digiKam databases and the collections.**" 0365 msgstr "" 0366 0367 #: ../../asset_management/data_protection.rst:110 0368 msgid "Power Supply Failures" 0369 msgstr "" 0370 0371 #: ../../asset_management/data_protection.rst:113 0372 msgid "Power Surges" 0373 msgstr "" 0374 0375 #: ../../asset_management/data_protection.rst:115 0376 msgid "" 0377 "As much as 1% of all computers are affected by lightning and power surges " 0378 "every year." 0379 msgstr "" 0380 0381 #: ../../asset_management/data_protection.rst:117 0382 msgid "" 0383 "This is about total data loss due to power surges. Of course you can have " 0384 "the occasional data loss due to power loss before saving files. But those " 0385 "losses can normally be restored without major difficulty." 0386 msgstr "" 0387 0388 #: ../../asset_management/data_protection.rst:119 0389 msgid "" 0390 "You don’t have to wait for the next thunderstorm to be concerned about how a " 0391 "sudden fluctuation in electric power may affect your computer system. Recent " 0392 "statistics have shown that as much as 63 percent of all electronics " 0393 "casualties are due to power problems, and most computers are subject to two " 0394 "or more power anomalies a day. Since power surges or blackouts can occur " 0395 "anywhere and at any time, it only makes sense to protect your computer by " 0396 "investing in some sort of surge protection device." 0397 msgstr "" 0398 0399 #: ../../asset_management/data_protection.rst:122 0400 msgid "How Surges Happen" 0401 msgstr "" 0402 0403 #: ../../asset_management/data_protection.rst:124 0404 msgid "" 0405 "A power surge occurs when the power line voltage increases over nominal " 0406 "values for more than 10 milliseconds. Sixty percent of all power surges are " 0407 "caused from within the home or office, generally when a device with a motor " 0408 "(such as a hair dryer, refrigerator, or water pump) shuts off and the power " 0409 "it was using is diverted elsewhere as excess voltage. The remaining 40 " 0410 "percent of power surges are generated by factors such as lightning, utility " 0411 "grid switching, line slapping, poor wiring, and so on." 0412 msgstr "" 0413 0414 #: ../../asset_management/data_protection.rst:126 0415 msgid "" 0416 "While most average electricity-using devices are not affected by power " 0417 "surges, devices relying on computer chips and high-speed microprocessors are " 0418 "susceptible to serious damage. For your computer, power anomalies can result " 0419 "in keyboard lockup, complete data loss, hardware degradation, damaged " 0420 "motherboards, and more. Failure to protect yourself from the inevitable can " 0421 "result in a loss of both time and money." 0422 msgstr "" 0423 0424 #: ../../asset_management/data_protection.rst:129 0425 msgid "Surge Protectors" 0426 msgstr "" 0427 0428 #: ../../asset_management/data_protection.rst:131 0429 msgid "" 0430 "The most common defense against power surges is a surge protector or " 0431 "suppressor, a device that works by absorbing some of the excess energy and " 0432 "diverting the rest of it to the ground. These are usually found in the form " 0433 "of a power strip (one of those long devices that have six or so outlets and " 0434 "a single, grounded plug). Bear in mind, however, that not every power strip " 0435 "serves as a surge protector." 0436 msgstr "" 0437 0438 #: ../../asset_management/data_protection.rst:133 0439 msgid "" 0440 "When selecting your surge protector, you want to be sure it is listed as " 0441 "meeting the UL 1449 standard, which guarantees a certain minimum of " 0442 "protection. You should also look for one that offers protection against " 0443 "lightning (not every one does) and provides insurance for equipment that is " 0444 "properly attached." 0445 msgstr "" 0446 0447 #: ../../asset_management/data_protection.rst:135 0448 msgid "" 0449 "Because a power surge can follow any path to your computer, be sure that " 0450 "each peripheral connected to your system is protected. This includes your " 0451 "phone line or cable modem, as power can surge through these routes as well. " 0452 "A number of manufacturers are now producing surge suppressors that feature a " 0453 "phone jack for your modem along with the electrical outlets, while others " 0454 "have coaxial cable jacks for those who use a cable modem or TV tuner card." 0455 msgstr "" 0456 0457 #: ../../asset_management/data_protection.rst:137 0458 msgid "" 0459 "If you have a notebook computer, you will want to carry a surge suppressor " 0460 "as well. A variety of suppressors designed specifically for notebooks are " 0461 "available, small in size and possessing both electric and phone outlets that " 0462 "make them ideal for use on the road." 0463 msgstr "" 0464 0465 #: ../../asset_management/data_protection.rst:140 0466 msgid "Uninterruptible Power Supply" 0467 msgstr "" 0468 0469 #: ../../asset_management/data_protection.rst:142 0470 msgid "" 0471 "While a surge suppressor will protect your system from minor fluctuations in " 0472 "the power lines, it won’t help you if the power should black out completely. " 0473 "Even an outage of just a few seconds can result in the loss of valuable " 0474 "data, so you might find it worthwhile to invest in an **Uninterruptible " 0475 "Power Supply** (UPS)." 0476 msgstr "" 0477 0478 #: ../../asset_management/data_protection.rst:144 0479 msgid "" 0480 "Besides serving as surge suppressors, these devices automatically switch to " 0481 "battery power when a power outage occurs, giving you the opportunity to save " 0482 "data and shut down your system. Some models will even allow you to keep " 0483 "working until power is restored. When purchasing a UPS, be sure that it has " 0484 "the same qualities that you would seek in a surge suppressor, but also check " 0485 "out the battery life and included software." 0486 msgstr "" 0487 0488 #: ../../asset_management/data_protection.rst:146 0489 msgid "" 0490 "Considering the potential risk to your computing system, ensuring its safety " 0491 "from power disturbances is a worthwhile investment. A quality surge " 0492 "suppressor or a 500W UPS are not too expensive for the peace of mind you’ll " 0493 "gain knowing your computer is well protected. In the very least pull all " 0494 "lines to your computer when you go on holidays." 0495 msgstr "" 0496 0497 #: ../../asset_management/data_protection.rst:149 0498 msgid "Safeguarding Policy" 0499 msgstr "" 0500 0501 #: ../../asset_management/data_protection.rst:152 0502 msgid "Web Storage Services" 0503 msgstr "" 0504 0505 #: ../../asset_management/data_protection.rst:154 0506 msgid "" 0507 "Amazon Web Services includes S3 - Simple Storage Service. With appropriate " 0508 "configuration, you can mount S3 as a drive on Linux, Mac, and Windows " 0509 "systems, allowing you to use it as a backup destination for your favorite " 0510 "software. Google Shared Storage is another popular offer where one can store " 0511 "infinite amount of data." 0512 msgstr "" 0513 0514 #: ../../asset_management/data_protection.rst:156 0515 msgid "" 0516 "It is expensive compared to hard drives at home. And you have to transfer " 0517 "the images over the (a comparatively slow) Internet." 0518 msgstr "" 0519 0520 #: ../../asset_management/data_protection.rst:158 0521 msgid "" 0522 "We think as a safeguard against localized data loss of the most essential " 0523 "images it's not a bad idea at all, but it is not a general backup solution, " 0524 "much too slow for that." 0525 msgstr "" 0526 0527 #: ../../asset_management/data_protection.rst:160 0528 msgid "" 0529 "Google Photo, and Flickr provide online storage services specialist on " 0530 "photographie. Their free space is limited and you don't want to have full " 0531 "resolution images online. But the pro-accounts offer more." 0532 msgstr "" 0533 0534 #: ../../asset_management/data_protection.rst:162 0535 msgid "" 0536 "In terms of data retention the web space solution is probably pretty safe. " 0537 "Transmission errors are corrected (thanks to the TCP protocol) and the big " 0538 "companies usually have backup included plus distributed storage so that they " 0539 "are disaster proof within themselves." 0540 msgstr "" 0541 0542 #: ../../asset_management/data_protection.rst:168 0543 msgid "digiKam Provide a Tool to Export Items to iNaturalist Web Service" 0544 msgstr "" 0545 0546 #: ../../asset_management/data_protection.rst:171 0547 msgid "Transmission Errors" 0548 msgstr "" 0549 0550 #: ../../asset_management/data_protection.rst:173 0551 msgid "" 0552 "Data does not only get lost from storage devices, it also gets lost when " 0553 "traveling inside the computer or across networks (although the network " 0554 "traffic itself via TCP is error protected). Errors occur on buses and in " 0555 "memory spaces. Consumer hardware has no protection against those bit errors, " 0556 "whereas it is worthwhile to look into such. You can buy ECC (error code " 0557 "correction) protected memory (which is expensive, granted). With `ECC RAM " 0558 "<https://en.wikipedia.org/wiki/ECC_memory>`_ at least the memory will be " 0559 "scrubbed for single bit errors and corrected. Double bit errors would escape " 0560 "that scheme but they occur too infrequently." 0561 msgstr "" 0562 0563 #: ../../asset_management/data_protection.rst:179 0564 msgid "The Data Workflow Between Application and Storage Media" 0565 msgstr "" 0566 0567 #: ../../asset_management/data_protection.rst:181 0568 msgid "" 0569 "This diagram depicts the transmission chain elements in a computer, all " 0570 "transitions are susceptible to transmission errors. The Linux `ZFS <https://" 0571 "en.wikipedia.org/wiki/ZFS>`_ and `BTRFS <https://en.wikipedia.org/wiki/" 0572 "Btrfs>`_ file system at least ensure the OS to disk path of data integrity " 0573 "under Linux." 0574 msgstr "" 0575 0576 #: ../../asset_management/data_protection.rst:183 0577 msgid "" 0578 "The Byte Error Rate (BER) for memory and transmission channels is in the " 0579 "order of 1 in 10 Million (10E-7 bit). That just means that 1 in 3000 images " 0580 "has an error only due to transmission problems. Now how dramatic that is for " 0581 "an image is left to chance, it could mean that the image is destroyed or " 0582 "that a pixel somewhere changed its value, due to the compression used on " 0583 "almost all images one cannot predict the gravity of a single bit error " 0584 "impact. Often one sees some partial images instead of the full image." 0585 msgstr "" 0586 0587 #: ../../asset_management/data_protection.rst:185 0588 msgid "" 0589 "The worst of all that is that nobody tells you when a transmission error " 0590 "occurs, not your hardware. All those glitches go down unheard until one day " 0591 "you open the photograph, and to your surprise it's broken. It is quite " 0592 "worrisome that there should be no protection within a computer, nobody seems " 0593 "to have thought of it. The Internet (TCP protocol) is much saver as a data " 0594 "path than inside a computer." 0595 msgstr "" 0596 0597 #: ../../asset_management/data_protection.rst:187 0598 msgid "" 0599 "Flaky power supplies are another source of transmission losses because they " 0600 "create interference with the data streams. With normal files systems those " 0601 "errors go unnoticed." 0602 msgstr "" 0603 0604 #: ../../asset_management/data_protection.rst:193 0605 msgid "The Storage Media Number of Failure Per Year" 0606 msgstr "" 0607 0608 #: ../../asset_management/data_protection.rst:195 0609 msgid "" 0610 "Even if you are not overly concerned today with transmission problems, have " 0611 "a look into the future at illustration. Already in 2010 we'll see thousands " 0612 "of errors per year." 0613 msgstr "" 0614 0615 #: ../../asset_management/data_protection.rst:198 0616 msgid "Future of File-systems" 0617 msgstr "" 0618 0619 #: ../../asset_management/data_protection.rst:200 0620 msgid "" 0621 "`ZFS <https://en.wikipedia.org/wiki/ZFS>`_ from Oracle seems to be one of " 0622 "two candidates to deal with disk errors on a low level, and it is highly " 0623 "scalable. It is Open Source, heavily patented, comes with an GPL " 0624 "incompatible license, and is available on Linux and macOS." 0625 msgstr "" 0626 0627 #: ../../asset_management/data_protection.rst:202 0628 msgid "" 0629 "Oracle has also started an initiative with its `BTRFS <https://en.wikipedia." 0630 "org/wiki/Btrfs>`_ file system. It employs the same protection technique as " 0631 "**ZFS** does, and it's available on Linux." 0632 msgstr "" 0633 0634 #: ../../asset_management/data_protection.rst:205 0635 msgid "Human Errors" 0636 msgstr "" 0637 0638 #: ../../asset_management/data_protection.rst:208 0639 msgid "Theft And Accidents" 0640 msgstr "" 0641 0642 #: ../../asset_management/data_protection.rst:210 0643 msgid "" 0644 "Do not underestimate it. Those two factor account for 86% of notebook and " 0645 "46% for desktop system data losses. For notebooks, theft counts for 50% " 0646 "alone." 0647 msgstr "" 0648 0649 #: ../../asset_management/data_protection.rst:213 0650 msgid "Malware" 0651 msgstr "" 0652 0653 #: ../../asset_management/data_protection.rst:215 0654 msgid "" 0655 "Data loss due to viruses is less grave than common wisdom make you believe. " 0656 "It accounts for less damage than theft or re-installations, for example. And " 0657 "it is limited to Microsoft OS users. Apple users experience very few viruses " 0658 "and under Linux they haven't been around for quite some time now." 0659 msgstr "" 0660 0661 #: ../../asset_management/data_protection.rst:218 0662 msgid "Human and Data Loss" 0663 msgstr "" 0664 0665 #: ../../asset_management/data_protection.rst:220 0666 msgid "" 0667 "Human error, as in everything, is a major problem in data loss. Take a deep " 0668 "breath and stop. Panic is a common reaction, and people do really stupid " 0669 "things. Experienced users will pull the wrong drive from a `RAID <https://en." 0670 "wikipedia.org/wiki/RAID>`_ array or reformat a drive, destroying all their " 0671 "information. Acting without thinking is dangerous to your data. Stop " 0672 "stressing about the loss and don’t do anything to the disk. Better yet, stop " 0673 "using the computer until you have a plan. Sit down and explain you plan to a " 0674 "laymen or better, laywoman. You will be amazed how many stupid ideas you'll " 0675 "discover yourself in such an exercise." 0676 msgstr "" 0677 0678 #: ../../asset_management/data_protection.rst:222 0679 msgid "" 0680 "If your disk is making weird noises, normal file recovery software isn’t " 0681 "going to work. Do a quick backup if that is going to happen to you. If the " 0682 "drive is still spinning and you can’t find your data, look for a data " 0683 "recovery utility and backup to another computer or drive. An Universal and " 0684 "powerful solution can be to use `CloneZilla open-source suite <https://en." 0685 "wikipedia.org/wiki/Clonezilla>`_. The important thing is to download them " 0686 "onto another drive, either on another computer, or onto a USB thumb drive or " 0687 "hard disk. It is good practice to save the recovered data to another disk. " 0688 "`dd tool <https://en.wikipedia.org/wiki/Dd_(Unix)>`_ is your friend on Linux " 0689 "systems." 0690 msgstr "" 0691 0692 #: ../../asset_management/data_protection.rst:225 0693 msgid "Common Myths Dispelled" 0694 msgstr "" 0695 0696 #: ../../asset_management/data_protection.rst:227 0697 msgid "We would like to dispel some common myths:" 0698 msgstr "" 0699 0700 #: ../../asset_management/data_protection.rst:229 0701 msgid "" 0702 "Open Source file systems are less prone to data loss than proprietary " 0703 "systems: Wrong, NTFS is rather a tiny notch better than ext4, ReiserFs, JFS, " 0704 "XFS, to name just the most popular file systems that often come as default " 0705 "storage format disk used by distributions." 0706 msgstr "" 0707 0708 #: ../../asset_management/data_protection.rst:231 0709 msgid "" 0710 "Journalize files systems prevent data corruption/loss: Wrong, they only " 0711 "speed up the scan process in case of a sudden interrupt during operation and " 0712 "prevent ambiguous states. But if a file was not entirely saved before the " 0713 "mishap, it'll be lost." 0714 msgstr "" 0715 0716 #: ../../asset_management/data_protection.rst:233 0717 msgid "" 0718 "`RAID <https://en.wikipedia.org/wiki/RAID>`_ systems prevent data corruption/" 0719 "loss: Mostly wrong, **RAID 0 and 1** prevent you from nothing, **RAID 5** " 0720 "can prevent data loss due to disk-failures (but not from disk or file system " 0721 "errors). Many low-end RAID controllers (most mother board controllers are) " 0722 "don’t report problems, figuring you’ll never notice. If you do notice, " 0723 "months later, what is the chance that you’ll know it was the controller’s " 0724 "fault? One insidious problem is corruption of **RAID 5** parity data. It is " 0725 "pretty simple to check a file by reading it and matching the metadata. " 0726 "Checking parity data is much more difficult, so you typically won’t see " 0727 "parity errors until a rebuild. Then, of course, it is too late." 0728 msgstr "" 0729 0730 #: ../../asset_management/data_protection.rst:235 0731 msgid "" 0732 "Viruses are the biggest thread to digital data: Wrong. Theft, and human " 0733 "errors are the primary cause of data loss." 0734 msgstr "" 0735 0736 #: ../../asset_management/data_protection.rst:238 0737 msgid "Storage Volume Estimation" 0738 msgstr "" 0739 0740 #: ../../asset_management/data_protection.rst:240 0741 msgid "" 0742 "Digital camera sensors are 1-2 aperture stops away from fundamental physical " 0743 "limitations. What we mean is this: as technology evolves, there is a natural " 0744 "limit to its progress. Sensitivity and noise characteristics for any kind of " 0745 "light sensor are not far from that limit." 0746 msgstr "" 0747 0748 #: ../../asset_management/data_protection.rst:242 0749 msgid "" 0750 "Today's cameras tend towards 50 mega pixels sensors, although this " 0751 "resolution is already too high for compact cameras and deteriorates the end " 0752 "result. Given the sensor size and quality of optics, 12 mega pixels are " 0753 "optimum for compact cameras. Even DSLR cameras run into their limits at " 0754 "20-24 mega pixels, for higher resolutions one has to go for full frame " 0755 "sensors (24x36mm) or even bigger formats." 0756 msgstr "" 0757 0758 #: ../../asset_management/data_protection.rst:244 0759 msgid "" 0760 "So, taking into account the manufacturer mega pixel propaganda it seems save " 0761 "to say that the bulk of future cameras will see less than 30 mega pixels. " 0762 "This gives us an estimation for the necessary storage space per photograph " 0763 "in the long run: <40 MB per image. Even if file versioning will be " 0764 "introduced (grouping of variations of a photograph under one file " 0765 "reference), the trend is to implement scripting of changes so that a small " 0766 "overhead will be recorded only and not a whole different image per version. " 0767 "With faster hardware this concept will see it's maturity quite soon." 0768 msgstr "" 0769 0770 #: ../../asset_management/data_protection.rst:246 0771 msgid "" 0772 "In order to estimate the amount of storage space you have to plan for, " 0773 "simply determine the number of photographs you take per year (easy with :ref:" 0774 "`digiKam's timeline sidebar tab <timeline_view>`) and multiply it by 40 MB. " 0775 "Most users will keep less than 2000 pictures per year which requires less " 0776 "than 80 GB/year. Assuming that you will change your hard disk (or whatever " 0777 "media in the future) every 4-5 years, the natural increase in storage " 0778 "capacity will suffice to keep you afloat." 0779 msgstr "" 0780 0781 #: ../../asset_management/data_protection.rst:248 0782 msgid "" 0783 "The more ambitious ones out there will need more space, much more maybe. " 0784 "Think of buying a file server, Giga-Ethernet comes integrated into " 0785 "motherboards today and it's a flick to fetch the files over the local " 0786 "network. Speaking about modern mobos: they now the capability to SATA media " 0787 "through an USB connectors. This makes it really a trifle to buy an external " 0788 "SATA drive and hook it up to your machine. 4000 GB drives will hit the " 0789 "market in 2020. These are terrific compact storage containers for backup " 0790 "swapping: keep one drive at home and one somewhere else." 0791 msgstr "" 0792 0793 #: ../../asset_management/data_protection.rst:251 0794 msgid "Backup and Recover" 0795 msgstr "" 0796 0797 #: ../../asset_management/data_protection.rst:253 0798 msgid "" 0799 "A 4 TB HDD is not very expensive today. Do not blame anybody else for data " 0800 "loss. 6% of all PCs will suffer an episode of data loss in any given year. " 0801 "Backup your data often according to a plan, and back it up and test the " 0802 "backup before you do anything dramatic like re-installing your OS, changing " 0803 "disks, resizing partitions and so on." 0804 msgstr "" 0805 0806 #: ../../asset_management/data_protection.rst:256 0807 msgid "Disaster Prevention" 0808 msgstr "" 0809 0810 #: ../../asset_management/data_protection.rst:258 0811 msgid "" 0812 "Say, you religiously do your backups every day on a external SATA drive. " 0813 "Then comes the day where lightning strikes. Happy you if the external drive " 0814 "was not connected at that moment." 0815 msgstr "" 0816 0817 #: ../../asset_management/data_protection.rst:260 0818 msgid "" 0819 "Disasters strike locally and destroy a lot. Forget about airplane crashes: " 0820 "fire, water, electricity, kids and theft are dangerous enough to our data. " 0821 "They usually cover a whole room or house." 0822 msgstr "" 0823 0824 #: ../../asset_management/data_protection.rst:262 0825 msgid "" 0826 "Therefore disaster control means de-localized storage. Move your backups " 0827 "upstairs, next house, to your bureau (and vise versa), whatever." 0828 msgstr "" 0829 0830 #: ../../asset_management/data_protection.rst:264 0831 msgid "" 0832 "There is another good aspect to the physical separation: as said above, " 0833 "panic is often the cause of destroying data, even the backup data. Having a " 0834 "backup not at hand right away may safe your ass one day." 0835 msgstr "" 0836 0837 #: ../../asset_management/data_protection.rst:267 0838 msgid "Backup Technicalities" 0839 msgstr "" 0840 0841 #: ../../asset_management/data_protection.rst:269 0842 msgid "" 0843 "**Full Backup**: A complete backup of all the files being backed up. It is a " 0844 "snapshot without history, it represents a full copy at one point in time." 0845 msgstr "" 0846 0847 #: ../../asset_management/data_protection.rst:271 0848 msgid "" 0849 "**Differential Backup**: A backup of only the files that have changed since " 0850 "the last full backup. Constitutes a full snapshot of two points in time: the " 0851 "full backup and the last differential one." 0852 msgstr "" 0853 0854 #: ../../asset_management/data_protection.rst:273 0855 msgid "" 0856 "**Incremental Backup**: A backup of only the files that have changed since " 0857 "last whatever backup. Constitutes multiple snapshots. You can recreate the " 0858 "original state at any point in time such a backup was made. This comes " 0859 "closest to a versioning system except that it is only sampled and not " 0860 "continuous." 0861 msgstr "" 0862 0863 #: ../../asset_management/data_protection.rst:276 0864 msgid "Backup The Data" 0865 msgstr "" 0866 0867 #: ../../asset_management/data_protection.rst:278 0868 msgid "The Best practice at all is to backup the data:" 0869 msgstr "" 0870 0871 #: ../../asset_management/data_protection.rst:280 0872 msgid "Do a **full backup** in a external storage device." 0873 msgstr "" 0874 0875 #: ../../asset_management/data_protection.rst:282 0876 msgid "Verify its **data integrity** and put it away (disaster control)." 0877 msgstr "" 0878 0879 #: ../../asset_management/data_protection.rst:284 0880 msgid "Have another storage device for **frequent backups**." 0881 msgstr "" 0882 0883 #: ../../asset_management/data_protection.rst:286 0884 msgid "" 0885 "**Swap the devices** every other month after having verified data integrity." 0886 msgstr "" 0887 0888 #: ../../asset_management/data_protection.rst:289 0889 msgid "A Useful Tool to Backups" 0890 msgstr "" 0891 0892 #: ../../asset_management/data_protection.rst:291 0893 msgid "" 0894 "Linux `rsync <https://en.wikipedia.org/wiki/Rsync>`_ is a wonderful little " 0895 "utility that's amazingly easy to set up on your machines. Rather than have a " 0896 "scripted FTP session, or some other form of file transfer script - rsync " 0897 "copies only the differences of files that have actually changed, compressed " 0898 "and through ssh if you want to for security. That's a mouthful." 0899 msgstr "" 0900 0901 #: ../../asset_management/data_protection.rst:293 0902 msgid "A reasonable backup approach for images could be this one:" 0903 msgstr "" 0904 0905 #: ../../asset_management/data_protection.rst:295 0906 msgid "" 0907 "Backup important images right away (after dumping them to a computer) to " 0908 "optical media." 0909 msgstr "" 0910 0911 #: ../../asset_management/data_protection.rst:297 0912 msgid "Do daily incremental backup of the work space." 0913 msgstr "" 0914 0915 #: ../../asset_management/data_protection.rst:299 0916 msgid "" 0917 "Do a weekly differential backup and delete integral backups of week-2 (two " 0918 "weeks ago)." 0919 msgstr "" 0920 0921 #: ../../asset_management/data_protection.rst:301 0922 msgid "Do a monthly differential backup and delete backup of month-2." 0923 msgstr "" 0924 0925 #: ../../asset_management/data_protection.rst:303 0926 msgid "" 0927 "If not physically separated already, separate it now (swapping-in another " 0928 "backup drive)." 0929 msgstr "" 0930 0931 #: ../../asset_management/data_protection.rst:305 0932 msgid "" 0933 "This protocol tries to leave you enough time to spot losses and to recover " 0934 "fully at the same time keeping the backup volume at <130% of the working " 0935 "space. You end up with a daily version of the last 7-14 days, a weekly " 0936 "snapshot for at least one month, and a snapshot of every month. Any more " 0937 "thinning should be done by hand after a full verification. Preserve your " 0938 "images through the changes of technology and owners" 0939 msgstr "" 0940 0941 #: ../../asset_management/data_protection.rst:308 0942 msgid "" 0943 "In order for your valuable images to **survive the next 40 years** or so " 0944 "(because that's about the time that you will become really interested to " 0945 "revisit those nice old photographs of you as a child, adolescent etc.) there " 0946 "are two strategies to be observed:" 0947 msgstr "" 0948 0949 #: ../../asset_management/data_protection.rst:310 0950 msgid "" 0951 "**Keep up with technology**, don't lag behind more than a couple of years." 0952 msgstr "" 0953 0954 #: ../../asset_management/data_protection.rst:312 0955 msgid "Save your photos in an open, **non-proprietary standard**." 0956 msgstr "" 0957 0958 #: ../../asset_management/data_protection.rst:315 0959 msgid "Keep Up With Technology" 0960 msgstr "" 0961 0962 #: ../../asset_management/data_protection.rst:317 0963 msgid "" 0964 "As the future is unforeseeable by nature, everything said today is to be " 0965 "taken with caution, and to be reviewed as we advance. Unfortunately there is " 0966 "no shortcut possible to some basic vigilance. Every 5-8 years at least one " 0967 "should ask oneself the question of backwards compatibility of current " 0968 "systems. The less variants we used in the past the less questions are to be " 0969 "answered in the future." 0970 msgstr "" 0971 0972 #: ../../asset_management/data_protection.rst:319 0973 msgid "" 0974 "Of course every time you change your computer system (machine, operating " 0975 "system, applications, DRM) you have to ask yourself the same questions. " 0976 "Today, if you want to switch to Windows, you have to ask yourself three " 0977 "times if you still can import your pictures, and, more important so, if you " 0978 "are ever able to move them onto some other system or machine. Chances are " 0979 "good that you cannot. We see many people struggling around us, because " 0980 "Windows enforces a strict DRM regime. How can you proof to Windows that you " 0981 "are actually the owner of your pictures copyright?" 0982 msgstr "" 0983 0984 #: ../../asset_management/data_protection.rst:321 0985 msgid "" 0986 "Basically the questions should be answered along the line explained in this " 0987 "document: use and change to open standards supported by a manifold of " 0988 "applications." 0989 msgstr "" 0990 0991 #: ../../asset_management/data_protection.rst:323 0992 msgid "" 0993 "Virtualization becomes available now for everybody. So if you have an old " 0994 "system that is important for reading your images, keep it, install it as a " 0995 "virtual machine for later." 0996 msgstr "" 0997 0998 #: ../../asset_management/data_protection.rst:325 0999 msgid "" 1000 "Otherwise the advice is quite simple: every time you change your computer " 1001 "architecture, your storage and backup technology, your file format, check it " 1002 "out, go through your library and convert to a newer standard if necessary. " 1003 "And keep to open standards." 1004 msgstr "" 1005 1006 #: ../../asset_management/data_protection.rst:328 1007 msgid "Scalability" 1008 msgstr "" 1009 1010 #: ../../asset_management/data_protection.rst:330 1011 msgid "" 1012 "Scalability is the tech-geek expression of the (easy) capability of a system " 1013 "to be resized, which always means up-sized." 1014 msgstr "" 1015 1016 #: ../../asset_management/data_protection.rst:332 1017 msgid "" 1018 "Lets assume you planned for scalability and dedicated the container you want " 1019 "to increase to a separate disk or partition. On Linux system you then can " 1020 "copy and resize the container to the new disk." 1021 msgstr "" 1022 1023 #: ../../asset_management/data_protection.rst:337 1024 msgid "Use Open File Formats" 1025 msgstr "" 1026 1027 #: ../../asset_management/data_protection.rst:339 1028 msgid "" 1029 "The short history of the digital era in the past 20 years has proven over " 1030 "and over again that proprietary formats are not the way to go when you want " 1031 "your data to be intelligible 10 years into the future. Microsoft is " 1032 "certainly the well known culprit of that sort because of its domineering " 1033 "market share. But other companies are actually (if inadvertently) worse " 1034 "since they may not stay long enough in the market at all or have a small " 1035 "user/contributor base only. In the case of Microsoft one has at least the " 1036 "advantage of many people sharing the same problems. Finding a solution has " 1037 "therefore much more success. Still, in some cases Microsoft is using Open " 1038 "Source documentation to understand their own systems, so badly maintained " 1039 "have been their own documentation. Usually with any given MSoffice suite one " 1040 "cannot properly read a document created with the same application two major " 1041 "versions earlier." 1042 msgstr "" 1043 1044 #: ../../asset_management/data_protection.rst:341 1045 msgid "" 1046 "Image formats have had a longer live time than office documents and are a " 1047 "bit less affected by obsolescence." 1048 msgstr "" 1049 1050 #: ../../asset_management/data_protection.rst:343 1051 msgid "" 1052 "Open Source standards have the huge advantage of having an open " 1053 "specification. Even if one day in the future there'll be no software to read " 1054 "it anymore, one can recreate such software, a task becoming simpler every " 1055 "year." 1056 msgstr "" 1057 1058 #: ../../asset_management/data_protection.rst:349 1059 msgid "digiKam Image Editor Default Save Settings For Common Image Formats" 1060 msgstr "" 1061 1062 #: ../../asset_management/data_protection.rst:351 1063 msgid "" 1064 "**JPEG** has been around for a while now, and whilst it's a lossy format " 1065 "losing a bit every time you make a modification and save it, it is " 1066 "ubiquitous, supports JFIF, Exif, IPTC and XMP metadata, has good compression " 1067 "ratios and can be read by all imaging software. Because of its metadata " 1068 "limitation, lossy nature, absence of transparency and 8 bit color channel " 1069 "depth, we do not recommend it. JPEG2000 is better, can be employed lossless, " 1070 "but lacks in user base." 1071 msgstr "" 1072 1073 #: ../../asset_management/data_protection.rst:353 1074 msgid "" 1075 "**GIF** is a proprietary. patented format and slowly disappearing from the " 1076 "market. Don't use it." 1077 msgstr "" 1078 1079 #: ../../asset_management/data_protection.rst:355 1080 msgid "" 1081 "**PNG** has been invented as a Open Source standard to replace GIF, but it " 1082 "does much more. It is lossless, supports XMP, Exif and IPTC metadata, 16 bit " 1083 "color encoding and full transparency. PNG can store gamma and chromaticity " 1084 "data for improved color matching on heterogeneous platforms. Its drawback " 1085 "are a relatively big footprints (but smaller than TIFF) and slow " 1086 "compression. We recommend it." 1087 msgstr "" 1088 1089 #: ../../asset_management/data_protection.rst:357 1090 msgid "" 1091 "**TIFF** has been widely accepted as an image format. TIFF can exist in " 1092 "uncompressed form or in a container using a lossless compression algorithm " 1093 "(Deflate). It maintains high image quality but at the expense of much larger " 1094 "file sizes. Some cameras let you save your images in this format. The " 1095 "problem is that the format has been altered by so many people that there are " 1096 "now 50 or more flavors and not all are recognizable by all applications." 1097 msgstr "" 1098 1099 #: ../../asset_management/data_protection.rst:359 1100 msgid "" 1101 "**PGF** for Progressive Graphics File is another not so known but open file " 1102 "image format. Wavelet-based, it allows lossless and lossy data compression. " 1103 "PGF compares well with **JPEG 2000** but it was developed for speed " 1104 "(compression/decompression) rather than to be the best at compression ratio. " 1105 "At the same file size a PGF file looks significantly better than a JPEG one, " 1106 "while remaining very good at progressive display too. PGF format is used " 1107 "internally in digiKam to store compressed thumbnails in the database. For " 1108 "more information about the PGF format see the `libPGF homepage <https://" 1109 "libpgf.org/>`_" 1110 msgstr "" 1111 1112 #: ../../asset_management/data_protection.rst:365 1113 msgid "digiKam Image Editor Raw Import Tool" 1114 msgstr "" 1115 1116 #: ../../asset_management/data_protection.rst:367 1117 msgid "" 1118 "**RAW** format. Some, typically more expensive, cameras support RAW format " 1119 "shooting. The RAW format is not really an image standard at all, it is a " 1120 "container format which is different for every brand and camera model. RAW " 1121 "format images contain minimally processed data from the image sensor of a " 1122 "digital camera or image scanner. Raw image files are sometimes called " 1123 "digital negatives, as they fulfill the same role as film negatives in " 1124 "traditional chemical photography: that is, the negative is not directly " 1125 "usable as an image, but has all of the information needed to create an " 1126 "image. Storing photographs in a camera's RAW format provides for higher " 1127 "dynamic range and allows you to alter settings, such as white balance, after " 1128 "the photograph has been taken. Most professional photographers use RAW " 1129 "format, because it offers them maximum flexibility. The downside is that RAW " 1130 "image files can be very large indeed." 1131 msgstr "" 1132 1133 #: ../../asset_management/data_protection.rst:369 1134 msgid "" 1135 "We recommend clearly to **abstain from archiving in RAW format** (as opposed " 1136 "to shooting in RAW format, which we recommend). It has all bad ingredients: " 1137 "many varieties and proprietary nature. It is clear that in a few years time " 1138 "you cannot use your old RAW files anymore. We have already seen people " 1139 "changing camera, losing their color profiles and having great difficulty to " 1140 "treat their old RAW files correctly. Better change to DNG format." 1141 msgstr "" 1142 1143 #: ../../asset_management/data_protection.rst:371 1144 msgid "" 1145 "**DNG** or Digital Negative file format is a royalty free and open RAW image " 1146 "format designed by Adobe Systems. DNG was a response to demand for a " 1147 "unifying camera raw file format. It is based on the TIFF/EP format, and " 1148 "mandates use of metadata. A handful of camera manufacturers have adopted DNG " 1149 "already, let's hope that the main contenders Canon and Nikon will use it one " 1150 "day. `Apple ProRAW <https://support.apple.com/en-us/HT211965>`_ format " 1151 "available since the iPhone 12 Pro Max is based on DNG." 1152 msgstr "" 1153 1154 #: ../../asset_management/data_protection.rst:377 1155 msgid "" 1156 "digiKam Provide a Tool to Convert in Batch RAW to DNG in :ref:`Batch Queue " 1157 "Manager <dng_converter>`" 1158 msgstr "" 1159 1160 #: ../../asset_management/data_protection.rst:379 1161 msgid "" 1162 "We strongly recommend converting RAW files to DNG for archiving. Despite the " 1163 "fact that DNG was created by Adobe, it is an open standard and widely " 1164 "embraced by the Open Source community (which is usually a good indicator of " 1165 "perennial properties). Some manufacturers have already adopted DNG as RAW " 1166 "format. And last not least, Adobe is the most important source of graphical " 1167 "software today, and they of course support their own invention. It is an " 1168 "ideal archival format, the raw sensor data will be preserved as such in TIFF " 1169 "format inside DNG, so that the risk associated with proprietary RAW formats " 1170 "is alleviated. All of this makes migration to another operating system a no-" 1171 "brainer." 1172 msgstr "" 1173 1174 #: ../../asset_management/data_protection.rst:385 1175 msgid "" 1176 "digiKam Provide Tools to Convert RAW to DNG during :ref:`Download from " 1177 "Camera <camera_dngconvert>`" 1178 msgstr "" 1179 1180 #: ../../asset_management/data_protection.rst:387 1181 msgid "" 1182 "**XML** for Extensible Mark-up Language or **RDF** for Resource Description " 1183 "Framework. XML is like HTML, but where HTML is mostly concerned with the " 1184 "presentation of data, XML is concerned with the *representation* of data. On " 1185 "top of that, XML is non-proprietary, operating-system-independent, fairly " 1186 "simple to interpret, text-based and cheap. RDF is the WC3's solution to " 1187 "integrate a variety of different applications such as library catalogs, " 1188 "world-wide directories, news feeds, software, as well as collections of " 1189 "music, images, and events using XML as an interchange syntax. Together the " 1190 "specifications provide a method that uses a lightweight ontology based on " 1191 "the Dublin Core which also supports the \"Semantic Web\" (easy exchange of " 1192 "knowledge on the Web)." 1193 msgstr "" 1194 1195 #: ../../asset_management/data_protection.rst:390 1196 msgid "IPTC Goes XMP" 1197 msgstr "" 1198 1199 #: ../../asset_management/data_protection.rst:392 1200 msgid "" 1201 "That's probably one of the reasons why, around 2001, that Adobe introduced " 1202 "its XML based XMP technology to replace the *Image Resource Block* " 1203 "technology of the nineties. XMP stands for **Extensible Metadata Platform**, " 1204 "a mixture of XML and RDF. It is a labeling technology that lets users embed " 1205 "data about a file in the file itself, the file info is saved using the " 1206 "extension :file:`*.xmp*` (signifying the use of XML/RDF)." 1207 msgstr "" 1208 1209 #: ../../asset_management/data_protection.rst:394 1210 msgid "" 1211 "`XMP <https://en.wikipedia.org/wiki/Extensible_Metadata_Platform>`_: As much " 1212 "as ODF will be readable forever (since its containing text is written in " 1213 "clear text), XMP will preserve your metadata in a clearly understandable " 1214 "format XML. No danger here of not being able to read it later. It can be " 1215 "embedded into the image files or as a separate accompanying file " 1216 "(**Sidecar** concept). XMP can be used in PDF, JPEG, JPEG2000, GIF, PNG, " 1217 "HTML, TIFF, Adobe Illustrator, PSD, Postscript, Encapsulated Postscript, and " 1218 "video files. In a typical edited JPEG file, XMP information is typically " 1219 "included alongside Exif and IPTC data." 1220 msgstr "" 1221 1222 #: ../../asset_management/data_protection.rst:400 1223 msgid "digiKam can display XMP Contents from Image and Video" 1224 msgstr "" 1225 1226 #: ../../asset_management/data_protection.rst:402 1227 msgid "" 1228 "Embedding metadata in files allows easy sharing and transfer of files across " 1229 "products, vendors, platforms, customers, without metadata getting lost. The " 1230 "most common metadata tags recorded in XMP data are those from the Dublin " 1231 "Core Metadata Initiative, which include things like title, description, " 1232 "creator, and so on. The standard is designed to be extensible, allowing " 1233 "users to add their own custom types of metadata into the XMP data. XMP " 1234 "generally does not allow binary data types to be embedded. This means that " 1235 "any binary data one wants to carry in XMP, such as thumbnail images, must be " 1236 "encoded in some XML-friendly format, such as Base-64." 1237 msgstr "" 1238 1239 #: ../../asset_management/data_protection.rst:404 1240 msgid "" 1241 "Many photographers prefer keeping an original of their shots (mostly RAW) " 1242 "for the archive. XMP suits that approach as it keeps metadata separate from " 1243 "the image file. We do not share this point of view. There could be problems " 1244 "linking metadata file and image file, and as said above, RAW formats will " 1245 "become obsolete. We recommend using DNG as a container and putting " 1246 "everything inside." 1247 msgstr "" 1248 1249 #: ../../asset_management/data_protection.rst:406 1250 msgid "" 1251 "The `Dublin Core Metadata Initiative <https://www.dublincore.org/>`_ is an " 1252 "open organization engaged in the development of interoperable online " 1253 "metadata standards that support a broad range of purposes and business " 1254 "models. DCMI's activities include work on architecture and modeling, " 1255 "discussions and collaborative work in DCMI Communities and DCMI Task Groups, " 1256 "annual conferences and workshops, standards liaison, and educational efforts " 1257 "to promote widespread acceptance of metadata standards and practices." 1258 msgstr "" 1259 1260 #: ../../asset_management/data_protection.rst:412 1261 msgid "digiKam Support Sidecar Files With many Options From Settings Panel" 1262 msgstr "" 1263 1264 #: ../../asset_management/data_protection.rst:415 1265 msgid "Protect Your Data" 1266 msgstr "" 1267 1268 #: ../../asset_management/data_protection.rst:417 1269 msgid "Use surge protectors (UL 1449 standard), possibly combined with a UPS." 1270 msgstr "" 1271 1272 #: ../../asset_management/data_protection.rst:419 1273 msgid "" 1274 "Use ECC memory to verify correct data transmission (even just saving files)." 1275 msgstr "" 1276 1277 #: ../../asset_management/data_protection.rst:421 1278 msgid "Watch your hard drives (temperature, noise...), make backups." 1279 msgstr "" 1280 1281 #: ../../asset_management/data_protection.rst:423 1282 msgid "Keep backups at another location, locked up, use web storage space." 1283 msgstr "" 1284 1285 #: ../../asset_management/data_protection.rst:425 1286 msgid "Use archival media and burners." 1287 msgstr "" 1288 1289 #: ../../asset_management/data_protection.rst:427 1290 msgid "" 1291 "Don't panic in case of data loss, explain your recovery plan to a layperson." 1292 msgstr "" 1293 1294 #: ../../asset_management/data_protection.rst:429 1295 msgid "" 1296 "Choose you file system, partitions, folders to cater for easy scalability." 1297 msgstr "" 1298 1299 #: ../../asset_management/data_protection.rst:431 1300 msgid "Use open, non-proprietary standards to manage and save photographs." 1301 msgstr "" 1302 1303 #: ../../asset_management/data_protection.rst:433 1304 msgid "Do a technology/migration review at least every 5 years." 1305 msgstr ""