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