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