[digikam-doc] digikam: separate dam section
Gilles Caulier
caulier.gilles at gmail.com
Tue Aug 23 10:44:36 UTC 2016
Git commit d53eb6e4d98e102e30bbb3452a608c1dd6dd9010 by Gilles Caulier.
Committed on 23/08/2016 at 10:44.
Pushed by cgilles into branch 'master'.
separate dam section
M +2 -468 digikam/index.docbook
M +1 -1 digikam/intro-background.docbook
C +99 -1135 digikam/using-dam.docbook [from: digikam/index.docbook - 050% similarity]
http://commits.kde.org/digikam-doc/d53eb6e4d98e102e30bbb3452a608c1dd6dd9010
diff --git a/digikam/index.docbook b/digikam/index.docbook
index f42d180..5beee16 100644
--- a/digikam/index.docbook
+++ b/digikam/index.docbook
@@ -17,6 +17,7 @@
<!ENTITY doc-using-mainwindow SYSTEM "using-mainwindow.docbook">
<!ENTITY doc-using-sidebar SYSTEM "using-sidebar.docbook">
<!ENTITY doc-using-lighttable SYSTEM "using-lighttable.docbook">
+ <!ENTITY doc-using-dam SYSTEM "using-dam.docbook">
<!-- image editor -->
<!ENTITY doc-photo-editing SYSTEM "photo-editing.docbook">
<!ENTITY doc-editor-color SYSTEM "editor-color.docbook">
@@ -115,474 +116,7 @@
&doc-using-sidebar;
- <sect1 id="dam"> <title>Digital Asset Management (DAM) with &digikam;</title>
-
- <para><link linkend="build-dam">Build a system to organize and find your photographs</link></para>
- <itemizedlist>
- <listitem><para><link linkend="case-for-digikam">A case for doing DAM with &digikam;</link></para></listitem>
- <listitem><para><link linkend="build-archive">Build the archive: Folder organization, physical layout as information</link></para></listitem>
- <listitem><para><link linkend="automatic-metadata">Automatic metadata generation</link></para></listitem>
- <listitem><para><link linkend="ranking">Rating/Ranking</link></para></listitem>
- <listitem><para><link linkend="keywords">Tagging, Keyword assignment</link></para></listitem>
- <listitem><para><link linkend="captions">Captions/Comments</link></para></listitem>
- <listitem><para><link linkend="geotagging">Geolocation (geo-tagging)</link></para></listitem>
- </itemizedlist>
- <para><link linkend="copyright-protect">Protect your authorship and copyright/left</link></para>
- <itemizedlist>
- <listitem><para><link linkend="watermarking">Digital Watermarking (DW)</link></para></listitem>
- </itemizedlist>
- <para><link linkend="data-corruption">Protect your images from data corruption and loss</link></para>
- <itemizedlist>
- <listitem><para><link linkend="physical-deterioation">Physical deterioation</link></para></listitem>
- <listitem><para><link linkend="logical-errors">Logical errors</link></para></listitem>
- <listitem><para><link linkend="human-errors">Human errors</link></para></listitem>
- <listitem><para><link linkend="myths-dispelled">Common myths dispelled</link></para></listitem>
- <listitem><para><link linkend="storage-budget">Make your budget: Data size, required storage volume estimation</link></para></listitem>
- <listitem><para><link linkend="backup">Back it up, backup, backup, recover!</link></para></listitem>
- <listitem><para><link linkend="technology-review">Preserve your images through the changes of technology and owners</link></para></listitem>
- <listitem><para><link linkend="best-practice">Best practice: Data protection</link></para></listitem>
- </itemizedlist>
- <para><link linkend="dam-workflow">A typical DAM workflow</link></para>
-
- <sect2 id="dam-introduction"> <title>Introduction</title>
- <epigraph><para><emphasis>...in the end, photographs need a lot of care.</emphasis> I hope it's you who said this.</para></epigraph>
-
- <para>Can you find your digital photographs when you need them? Or do you spend more time sifting through your hard drive and file cabinets than you would like? Do you have a systematic approach for assigning and tracking content data on your photos? If you make a living as a photographer, do your images bear your copyright and contact information, or do they circulate in the marketplace unprotected? Do you want your future grandchildren to admire your photographs you have taken yesterday? How do you ensure backup and the correctness of your data? How to prepare to change your computer, your hard disk, the software, the operating system and still manage to find your pictures or movies?</para>
- <para>What is digital asset management - apart from a buzz word? Digital Asset Management (DAM) refers to every part of the process that follows the taking of the picture, all the way through the final output and permanent storage. Anyone who shoots, scans or stores digital photographs is practicing some form of DAM, but most of us are not doing so in a systematic or efficient way.</para>
- <para>We present a tool, a plan and practical advice on how to file, find, protect and re-use photographs, focusing on best practices for digital photographers using &digikam;. We cover downloading, renaming, culling, converting, grouping, backing-up, rating, tagging, archiving, optimizing, maintaining and exporting image files.</para>
- <para>A generic definition: <blockquote><para>"<emphasis>Digital Asset Management</emphasis> ingests, indexes, categorizes, secures, searches, transforms, assembles and exports content that has monetary or cultural value."</para></blockquote></para>
- <para>And since we're at it another important one: <blockquote><para>Metadata is defined as <emphasis>data about data</emphasis>. Metadata is definitional data that provides information about or documentation of other data managed within an application or environment.</para></blockquote></para>
- <para>In our context here it stands for all information <emphasis>about</emphasis> a photograph.</para>
- <para>&digikam; with its libraries and plugins is a unique and comprehensive tool to cover most of DAM tasks, and it does it fast and transparently. Based on open standards on all fronts it will not confine you to a platform or application, rather it puts you into a fast track to manage and find your photographs and to move on if you so please to any other platform, application, system without losing any of your work be it as an occasional user, enthusiast or professional.</para>
- <para>The one thing that differentiates the archiving capabilities of film vs digital is that with digital you can make as many new originals as you want. With film you only have one original. All copies will have a slightly lower quality, and both originals and copies are more or less slowly aging and disappearing. The only way to keep it "forever fresh" is to make a digital copy of it. And that is also the only way to protect it from all hazards. </para>
- <para>Even if digital media today may last shorter than film it is just up to you to make new copies every year, 5, 10 years or whenever necessary, and to always keep at least 2-3 copies of the files, preferably in different physical locations. You never had that opportunity with film. It could always be damaged in a fire, floods or similar - or even be stolen. The good and bad news then is this: if you lose digital images/data it is only your own laxity. </para>
- </sect2>
-
- <sect2 id="build-dam"><title>Build a system to organize and find your photographs</title>
- <para> Themes: hierarchy, tags, rating, captions, geolocation, date, albums, filenames, versioning, exporting</para>
- <para>I dare-say if you have more than 1000 photographs on your computer in no-DAM fashion it takes you too long to find any particular image. And if you don't know how many images are in your files you're surely not using &digikam;. The dual approach to store metadata in a database<emphasis> and </emphasis>in the image files guarantees ultra fast searching and secure archiving freely accessible to other applications, platforms and formats.</para>
- <para>But as much as there is no such thing as a free lunch, there is no free cataloging or DAM - those who spend the initial time of building a systematic method of their own will be better off as time passes and the number of photographs multiplies. The ROI (return on investment) of DAM has been estimated in different studies to be better than 10. Keep in mind to be <command>concise, plan for the future (30-50y), do it once</command>. The upcoming semantic web will totally integrate into and add value to a DAM environment.</para>
-
- <sect3 id="case-for-digikam"> <title>A case for doing DAM with &digikam;</title>
- <para>&digikam; provides a number of methods to classify photographs: filenames, albums, collections, date + time, tags, rating, GPS position and captions. As if this was not enough, you can search many standard metadata items like camera model, lens, coordinates, image size and many more. Metadata categories as listed here are in fact different 'views' of your photo library. Combining these views is<emphasis> the </emphasis>very powerful method to narrow down the search for a file and to find it quickly. Imagine having 800 photos of your loved one. Searching for 'Mary', having more than '***' rating, shot in 'France' will surely leave you with very few candidates. In terms of selection criteria for a DAM system, &digikam; fares very well in terms of completeness, versatility, speed, scalability, accuracy and openness.</para>
- <para>The key thing to remember is that you don't know how you or somebody else will try to find an image 2 years ahead of our time. You will remember past events in a different context, it's a fact of life. So if can narrow down your search by remembering place or time or camera or theme or rating or owner you stand an infinitely better chance to find it quickly than by just one of those criteria or none. At the beginning, at the time of taking a photograph, all metadata is in your head (except for the EXIF data). If you do not transcribe some of it into your DAM system, it will be lost eventually as much as every event fades into oblivion over time.</para>
- <para>One distinction has to be interjected here between <command>private</command> and <command>public metadata</command>. One could say that all file-embedded attributes are potentially public since the images may be exported, sold, and copied to other places and people. On the other hand all non-embedded metadata in the database can be considered private as they stay in the database and go nowhere else. By adjusting &digikam;'s settings accordingly you can control what kind of data remains private and what will be embedded and eventually become public.</para>
- </sect3>
-
- <sect3 id="build-archive"> <title>Build the archive: Folder organization, physical layout as information</title>
- <para>The first thing to do and to know before you put anything onto your system is a to build an information structure (as opposed to data structure). Your image files have to be somehow organized within the computer, you have to decide if others should have access to your photographs (sharing), if you put them on a dedicated drive, on a network drive &etc; Keep in mind that you have to migrate one day onto some bigger volume. </para>
- <para>The organization should be simple, unified and scalable, and it should be independent of the storage medium on which you host them. Do not make the folders too small, several thousand images in one folder is not too much to ask for, but keep them small enough so that they can fit into a backup medium like a DVD 4.7 or 9.4 GB for double sided ones. Remember that the archive will grow all the time! The concrete type of structure depends on your use case of course: Lets take a simple yet frequent example: you are a casual photographer taking pictures of your private life, your family, holidays and so on. It could be efficient to create a structure based on years plus some holiday and export containers. It could look like this:</para>
-<blockquote><screen>2006
-2007
-2008
-Holidays
- - A
- - B
- - C
-Export
-Fun stuff
-</screen></blockquote>
-
- <para>Maybe you'll be happy with this structure. Holiday pictures can be quickly found by its location (unless you go to the same place every year), the rest will be organized by date. If you shoot enough pictures you want to create sub folders below the years as months ⪚ 2008-01, 2008-02 &etc; 'Export' would be a container for images to print or to put onto a website.</para>
- <para>The more professional photographer will have very different needs as there will be versions of photographs, archives, workflows, a constant influx of images of diverging themes, and a large quantity of everything. Within 10 year you'll have 95% archives and 5% work space files and you don't want to organize your structure around content!</para>
- <para>The consideration are these:</para>
-<itemizedlist>
- <listitem><para>what kind of files go together? Segregation of file type makes batch processing easier. Keep new and old files separate.</para></listitem>
- <listitem><para>How can you make that structure scalable?</para></listitem>
- <listitem><para>Segregation of original and working files makes it easier to allocate the backup strategy and migration. You will always know if you look for an original or a derivative.</para></listitem>
-</itemizedlist>
- <para>TBC</para>
- </sect3>
-
- <sect3 id="automatic-metadata"> <title>Automatic metadata generation</title>
- <para>How to go about all this metadata business? Firstly, there are already a lot of <command>automatically generated metadata</command>: EXIF data and Makernotes. If you have configured &digikam; with your identity section all imported images will be imprinted with this data set which includes copyrights, all automatic. If you have a GPS track recorded in parallel to your taking the photographs, you can geolocate those images in a single action using the Geolocation plugin. Even if you brought back 1000 images from a shooting session, so far you'll not have spent more than 10 minutes to do all that. And by now you have all camera settings of every shot, lens data like zoom, focus, aperture &etc;, date and time, shooting location, copyrights, authorship, program used, and more. Not bad, isn't it? But we could have done more during the importing, we could have changed the file names to include the date, or place or theme, we could have changed the format to a lossless 16 bit per channel format, we could have automatically separated JPEG and RAW files into their folders. I actually recommend to auto-rename to match an event, a place or a theme. &digikam; provides all date/calendar related grouping so that there's hardly a need for coding the date into the file name. Unless you'd like to do just that to browse your albums with another application that is not calendar savvy. You will buy a new camera one day or you have a second one already, sooner than you believe. The numbering scheme of that new camera will start over at typically IMG_0001.JPG again, creating identical file names to the ones you have already if you do not rename them. By renaming you lessen the chance of inadvertently overwriting them at a later date. Keep the new names clean, use alphanumerics, dashes, underscores and a single period prior to the file extension.</para>
- <para>I also recommend to switch-on the 'save metadata' options in the &digikam; settings page for metadata. This will ensure that EXIF and IPTC data is written into the file. If you forgot to do that you can always catch up by copying the metadata in the database to the files in one go (from the album menu).</para>
- <para>Now we have a lot of stuff already in our database, but what if I need to change some of it? &digikam; provides a metadata editor for a selected number of attributes, the most important ones of course. </para>
- <para>The real works begins here as we will apply tags, captions and a rating to every photograph. Of course, all images requiring the same attribute can be treated as a selection in one action. Lets start with rating or ranking. It's best to start with ranking because for further work you can concentrate on the good shots.</para>
-
- </sect3>
-
- <sect3 id="ranking"> <title>Rating/Ranking</title>
- <para>A ranking systematic is implemented in &digikam; by the 5 star rating tool. In fact there are 6 levels, zero through five stars (*) can be attributed (when saving them into IPTC metadata a translation of levels ensures compatibility with other programs). Rating is rapidly applied with &digikam; using keyboard shortcuts or the mouse on single photographs or whole selections. The rating can then be entered as a search criterion or directly from the status bar quick filters. However, before you start attributing stars everywhere take a moment to establish personal criteria for ranking. Best practice is to write down your personal match of stars to some qualitative expression, that will define what you actually mean when giving 5 stars. Generally there should be much less images rated with increasing star assignment. A ratio of 3-10 between each level has proven useful. That will get you quite far in distinguishing your rating pyramid. Say, you choose a ratio of 7 between levels. For every 5 star image you'll then have 7 4 stars, 49 3 stars and so on, resulting in almost 20000 pictures. Amazing? Yes, and 16807 of them you didn't have to rate at all! You even can define a different rating scheme depending on the kind of use, 2 stars for commercial use, may mean something else than 2 stars holiday photos. It is also a good practice to define a neutral rating, everything below is actually a negative rating. This will help you culling and thinning your collection very efficiently. Or you could define purposes to ratings, say 0 stars for 'can throw away', 1 star for images in quarantine (decide later), 2 stars for gallery export, 3 stars for printing, 4 stars for selling, 5 stars for 'have to work on', as you please. It must suit<emphasis> your </emphasis>needs. The following table illustrates a possible evolution for a professional photographer using a ranking ratio of roughly 7 over the next 12 years. It is evident that the good shots can be easily found, even within millions of photos.</para>
- <para>
- <inlinemediaobject>
- <imageobject><imagedata fileref="&path;DAM-pyramid.png" format="PNG"/></imageobject>
- <textobject> <phrase>Ranking</phrase> </textobject>
- </inlinemediaobject>
- </para>
-
-
- <para>Lets continue with tags (or keywords as called by other applications, or categories, they are all synonymous).</para>
- </sect3>
-
- <sect3 id="keywords"> <title>Tagging, Keyword assignment</title>
- <para>Tags are a hierarchical labeling system that you create as you add to it. The important thing to do is to create a system that suits your needs and habits. Are you a (semi)professional who wants to sell photographs to agencies, do you want to publish on a web gallery, or are you just the occasional amateur managing the visual family memory? For all these different use cases you want to design a tag structure that is adapted to it. If you configure it so, &digikam; will write the whole hierarchy into IPTC fields so that they can be used by your photographic agency using a different application of to automatically create title and caption for web exports. In any case it will serve you well to quickly find a specific picture again.</para>
- <para>The hierarchy will provide you with automatic groupings. For example, if you start a typical private use hierarchy with 'Activities', 'People', 'Places', 'Themes' and 'Projects' on the top level, everything you tag with a sub-tag of these will be grouped together into a virtual album. &digikam; has a dedicated view in the left sidebar for these virtual albums. But it comes even better! As you continue adding sub-tags into the hierarchies, not only will you be able to search and quick-filter for them, the right sidebar tag filter allows you to select combinations of tag groups. Lets say in the left sidebar tag panel you select the virtual album 'People' and you have 12 different tags for people in there, then you can combine it with the right sidebar and just choose 'Peter', 'Paul' and 'Mary' out of the 12.</para>
- <para>In the long run you will not remember the details of your pictures and their subject (essentially the metadata in you brain will break down). It is therefore paramount that you <command>choose general and generic categories</command>. You will aways remember that a particular shot was set at a river bank in a country or continent (-> river, continent), but you'll have forgotten which river it was. Instead of only tagging it with 'Okavango' you tag it with river/Africa or river/South Africa. The details you can either put into a tag as well or into the captions. A trick may help you: How would you search for that river with an Internet search engine? That's the way to go!</para>
- <para>Another categorization might be task-oriented as in 'print jobs', 'web export', 'personal', 'galleryXYZ', 'clients', 'slideshow' &etc; Create groups as you need them but not more, you should be able to remember by heart the top level tags at least, otherwise the differentiation will become useless. Don't forget that you have all the other attributes to narrow down the search. The right sidebar tag filter combines with any view of left sidebar (albums, calendar, timeline, tag and search).</para>
- <para>When you import cataloged images from other sources having embedded tags already, &digikam; will automatically create the trees for you, respectively insert it into the right place. Rearranging the hierarchy within the tree is no problem, you can do that easily by dragging and dropping a sub-tree to another place in the hierarchy. The changed tags will be updated as &digikam; ripples down the branches.</para>
- <para>The graphics here shows how different metadata overlap. This is a very coarse representation, as each block of metadata will in itself be subdivided into many sections. File names and calendar data are properties of all images.</para>
- <para>
- <inlinemediaobject>
- <imageobject><imagedata fileref="&path;DAM-Metadata.png" format="PNG"/></imageobject>
- <textobject> <phrase>Ranking</phrase> </textobject>
- </inlinemediaobject>
- </para>
-
- <para>Enough of tags - lets move on to captions or comments, the third major tool for metadata cataloging. </para>
- </sect3>
-
- <sect3 id="captions"> <title>Captions/Comments</title>
- <para>This is already the 4th kind of metadata we present here. What is the distinction of captions compared to tags (comments can be used synonymously, but the IPTC vocabulary stipulates the term 'caption'), keywords? Where tags owe to a hierarchical and generalized description, captions are the opposite: prose description, details, anecdotal stuff. Tags foremostly serve the finding, retrieval and grouping of assets, whereas captions shall entertain, inform, touch the beholder. Naturally they can also be used to filter the catalog, but this is just a byproduct. Captions are to remember the story, the event, the emotions, it's what makes photographs much more interesting to look at, captions put photographs into a context and meaning. If the pictures are an aesthetic statement, caption should be the emotional and informational complement.</para>
- <para>You rarely want nobody to see your photographs. You rather want to share them with friends, your family, other photographers, agencies, put them onto the Internet. And don't tell me you're not interested as to how your photos are being received! </para>
- <para>So you might have to most beautiful portrait, sunset or landscape and nobody seems to care. Why is that? Look at some good photographs yourself without reading the title, comment or background information. How many of you are interested in depth of field, exposure time, white balance &etc;? Some, of course. But anybody will be interested in the story the pictures tell, you want to remember a photograph, meaningless images bombard us too much anyways. You have to give the viewer something that explains it all.</para>
- <para>Lets look at this panorama. From far it is not even a nice beach panorama. If you go closer you start to see some details, people, the space.</para>
- <para>
- <inlinemediaobject>
- <imageobject><imagedata fileref="&path;DAM-story.png" format="PNG"/></imageobject>
- <textobject> <phrase>Ranking</phrase> </textobject>
- </inlinemediaobject>
- </para>
-
- <para>And now I tell you that this is the Allies landing site "Omaha Beach" in the French Normandie 60 years after the disembarkation. Wow! One starts to dream, have associations, memories, the historical time span is present, you may hear the silence. The caption has totally reframed to perception of this panorama. </para>
- <para>For others to appreciate your photographs, the title is probably more important than the image itself for the interest it creates. When you show pictures, tell a story. Remember that the key is to convey the meaning to viewers, to help them understand what you understand about the subject and what moved you.</para>
-<itemizedlist>
- <listitem><para>let people know what you understand about the subject, why you love it</para></listitem>
- <listitem><para>create a red line between the photographs</para></listitem>
- <listitem><para>oppose or relate them to different epochs</para></listitem>
- <listitem><para>take notes shortly after shooting to remember</para></listitem>
- <listitem><para>contemplate, research, watch, and talk - but mostly listen.</para></listitem>
- <listitem><para> it's okay if the image is less than perfect because it has the strength to stand on its own merit described in the caption.</para></listitem>
-</itemizedlist>
- <para>With &digikam; you can enter unlimited amounts of text using internationalized alphabet (UTF-8) as caption. You can enter it for a selection of photos at the same time. When you export images to web services, the captions will be exported at choice into either/or/and caption/title of the web gallery system, no need to re-write the story for publishing.</para>
- </sect3>
-
- <sect3 id="geotagging"> <title>Geolocation (geo-tagging)</title>
- <para>Do you still remember the times before GPS? When you would find your way to another city without navigation system? Wasn't the earth a dull blue ball before GoogleEarth? Well then, with images, the train of spatial representation is running at cruising speed alright. </para>
- <para>A few cameras have a GPS receiver built-in, the images come tagged with 3-dimensional coordinates. And with almost any GPS device you're able to extract a trace (of course the receiver needs to be switched-on and carried with you whilst taking the photographs, and for good matching the camera time must be accurately set) and save it onto a computer. You have to store it in gpx format, that's easily done with gpsbabel, gpsman and other tools. You then can automatically match a whole bunch of photos with that track using &digikam;. The coordinates are written into the JFIF part of JPG files (settings choice) and into the database. &digikam; will enable searches based on locations and coordinates, you can create virtual albums of geographical areas! In the right sidebar under the metadata tab you'll find your image located on a local zoom of the world map. A further click brings on anyone of several mapping services on the web, zooming in on details. Even if you don't have a GPS trace you can geo-tag multiple images with a geo-editor. Just navigate on the map to the spot of shooting and click to fix it as a geo-tag. </para>
- <para>e.g. conversion of a Garmin track with file name 'xyz':</para>
-<blockquote><screen>$ gpsbabel -w -i mapsource -f xyz.mps -o gpx -F xyz.gpx</screen></blockquote>
- <para>The possibilities of exploiting this geolocation are already innumerable and will become pervasive in the future. I'm sure one day not too far away we can revisit in a virtual reality our travels through geo-tagged pictures. The &digikam; features include exporting to kml files that can be opened by GoogleEarth (which in turn will show the photos on their shooting site), exporting to gallery2, picasaweb, flickr &etc; with GoogleMaps viewer and more.</para>
- </sect3>
- </sect2>
-
- <sect2 id="copyright-protect"> <title>Protect your authorship and copyleft/right</title>
- <para>Themes: watermarking, IPTC and XMP authorship data, export size</para>
- <para>This will be the last chapter and step to mark your digital library with authorship, ownership and copyright or -left information. More than in 'the good(?) old days' of paper copies, the ubiquitous Internet makes it just too easy to 'steal' a picture from a web site. At the very least, for all images that will be exported and/or published in any form, the authorship and copyright information should be part of their metadata. Nothing more simple to do with &digikam;: you can setup the default identity, and any images ingested be &digikam; will be automatically informed. I put copyleft in the title for a reason (citation from wikipedia):</para>
-<blockquote><para>"Copyleft is a play on the word copyright and is the practice of using copyright law to remove restrictions on distributing copies and modified versions of a work for others and requiring that the same freedoms be preserved in modified versions.</para>
- <para>Copyleft is a form of licensing and may be used to modify copyrights for works such as ... music, and art. In general, copyright law allows an author to prohibit others from reproducing, adapting, or distributing copies of the author's work. In contrast, an author may, through a copyleft licensing scheme, give every person who receives a copy of a work permission to reproduce, adapt or distribute the work as long as any resulting copies or adaptations are also bound by the same copyleft licensing scheme. A widely used and originating copyleft license is the GNU General Public License. Similar licenses are available through Creative Commons - called Share-alike."</para></blockquote>
- <para>And here follows a description of what should be supplied to &digikam;'s setup page as information:</para>
- <para><command>Author</command> (synonymous with Creator and By-line): This field should contain your name, or the name of the person who created the photograph. If it is not appropriate to add the name of the photographer (for example, if the identity of the photographer needs to be protected) the name of a company or organization can also be used. Once saved, this field should not be changed by anyone. This field does not support the use of commas or semi-colons as separator.</para>
- <para><command>Author title</command> (synonymous with By-line title): Linked to Author. This field should contain the job title of the photographer. Examples might include titles such as: Staff Photographer, Freelance Photographer, or Independent Commercial Photographer. Since this is a qualifier for the Author field, the Author field must also be filled out.</para>
- <para><command>Credit</command> (synonymous to Provider): Use the Provider field to identify who is providing the photograph. This does not necessarily have to be the author. If a photographer is working for a news agency such as Reuters or the Associated Press, these organizations could be listed here as they are 'providing' the image for use by others. If the image is a stock photograph, then the group (agency) involved in supplying the image should be listed here.</para>
- <para><command>Source</command>: The Source field should be used to identify the original owner or copyright holder of the photograph. The value of this field should never be changed after the information is entered following the image's creation. You should consider this to be a write-once field. The source could be an individual, an agency, or a member of an agency. To aid in later searches, I suggest to separate any slashes '/' with a blank space. Use the form 'photographer / agency' rather than 'photographer/agency.' Source may also be different from Creator and from the names listed in the Copyright Notice.</para>
- <para><command>Copyright Notice</command>: The Copyright Notice should contain any necessary copyright notice for claiming the intellectual property, and should identify the current owner(s) of the copyright for the photograph. Usually, this would be the photographer, but if the image was done by an employee or as work-for-hire, then the agency or company should be listed. Use the form appropriate to your country. For the United States you would typically follow the form of © {date of first publication} name of copyright owner, as in 'copr 2005 John Doe.' The word 'copyright' or the abbreviation 'copr' shall be used in place of the © symbol as ASCII characters only are allowed. In some foreign countries only the copyright symbol is recognized and the abbreviation does not work. Using something like (c) where the parentheses form a partial circle is not sufficient. For additional protection worldwide, use of the phrase, 'all rights reserved' following the notice above is encouraged. In Europe you would use: Copyright {Year} {copyright owner}, all rights reserved. In Japan, for maximum protection, the following three items should appear in the copyright field of the IPTC Core: (a) the word, Copyright; (b) year of the first publication; and (c) name of the author. You may also wish to include the phrase 'all rights reserved.'</para>
- <para>Whereas it is paramount to fill-in the author and copyright sections, they represent no protection against fraud. Anyone with a bit more than basic computer knowledge is able to delete or modify image embedded metadata. The solution to this problem is called 'digital watermarking'. To private persons this might be of little interest for the majority of photographs, but for professionals ans semi-professionals this protection is really important.</para>
- <sect3 id="watermarking"> <title>Digital Watermarking (DW)</title>
- <para>Digital Watermarking refers to an invisible digital watermark that is being impressed on photographs as an element of digital rights management (DRM). The watermark contains the same information of authorship and copyright as described above, but the metadata is encrypted and saved in the actual image data (as opposed to the metadata section which is a separate section within the image file). This invisible imprint has holographic properties so that modifications done to an image (size, color, crop, up to a certain limit) will not destroy the copyright information. Only when an image is resized to a very small fraction like a thumbnail will the embedded information be lost, but then the image is of no value anymore to the copyright infringing party. </para>
- <para>The digital watermark will be unique per image. &digikam; will provide a plugin for DW in the near future that features batch processing.</para>
- </sect3>
- </sect2>
-
- <sect2 id="data-corruption"> <title>Protect your images from data corruption and loss</title>
- <para>Themes: disk errors, disk failures, power surges, ECC, transmission errors, storage media deterioration, recovery, redundancy, disaster prevention, lifetime, temperature, data size, common myths</para>
-
- <sect3> <title>What are then the main factors of digital data loss?</title>
- <para>Of course we're not talking about losing CDs on the road or in a fire - that kind of loss is just the same as traditional paper copies or negatives. We are talking about problems with the so called "New Media".</para>
- <para>Problems with digital data can roughly be categorized into the following areas of concern:</para>
- <orderedlist>
- <listitem><para>the physical deterioration of the media (all media deteriorate at different time scales)</para></listitem>
- <listitem><para>undetected transmission errors during data transfer</para></listitem>
- <listitem><para>the lack of support for long-date, undoubtedly proprietary, digital formats</para></listitem>
- <listitem><para>ancient hardware. </para></listitem>
- </orderedlist>
- <para>Kroll Ontrack, the worlds largest data recovery firm, have some interesting statistics on what actually causes data loss.</para>
-<informaltable>
-<tgroup cols="3">
-<tbody>
-<row>
-<entry>Cause of data loss</entry>
-<entry>Perception</entry>
-<entry>Reality</entry>
-</row>
-<row>
-<entry>Hardware or system problem</entry>
-<entry>78%</entry>
-<entry>56%</entry>
-</row>
-<row>
-<entry>Human error</entry>
-<entry>11%</entry>
-<entry>26%</entry>
-</row>
-<row>
-<entry>Software corruption or problem </entry>
-<entry>7%</entry>
-<entry>9%</entry>
-</row>
-<row>
-<entry>Computer viruses</entry>
-<entry>2%</entry>
-<entry>4%</entry>
-</row>
-<row>
-<entry>Disaster</entry>
-<entry>1-2%</entry>
-<entry>1-2%</entry>
-</row>
-</tbody>
-</tgroup>
-</informaltable>
- <para>So let us analyze those cases step by step!</para>
- </sect3>
-
- <sect3 id="physical-deterioation"> <title>Physical deterioration</title>
- <sect4> <title>CD, DVD, optical drives</title>
- <para>Physical deterioration of the media happens more rapidly with paper and CD-Rs than the average of film. Yet while film lasts longer (sometimes decades longer) than other forms of media, the right kind of backup of digital media never loses anything. Film decays - digital 1's and 0's do not, and film starts to decay the moment it's created and developed. It will never have the same color, contrast, &etc; that it did have a moment before. Digital doesn't do that. However, digital is susceptible to corruption! And yes, physical media such as floppies and magnetic hard drives are also susceptible to the decay of the medium, just like CDs are. They just last longer. </para>
- <para>To combat the problem of CDs/DVDs, they need to be properly cared for and not trusted for more than a few years. Thankfully you can purchase archive-quality CDs and DVDs which last longer, though they are much more difficult to obtain and are much more expensive. There are offers out there for gold-plated DVDs, $2 a piece claiming 100 years storage life (if you care to believe it).</para>
- <para>CD/DVD disks may become unreadable, but you can reduce the risk using good disks and a good recorder, and storing them in a correct way. The best DVD recorders are not much more expensive than the cheapest, but they write in a much more reliable way. It's a matter of choosing the right one.</para>
- <para>Essentially, CDs and DVDs are very prone to errors, even in a freshly written state. That's why they are heavily protected with a checksum mechanism (75% of data are effective data, the rest is formatting and checksum overhead). But even with that massive amount of protection they will suffer deterioration from chemical aging, ultra-violet exposure, scratches, dust, &etc;</para>
- <para>For damaged CDs and DVDs, there is an inexpensive program called <ulink url="http://www.isobuster.com/">IsoBuster</ulink> from which will do seeming miracles on CDs and DVDs. It runs on Windows and &Linux;; but not (yet) on Macs. Similarly, there are applications designed to get data from damaged floppies, hard drives, flash media such as camera memory and USB drives, and so forth. </para>
- <para>Optical media: Blu-ray disks seem to win the format war against 'HD DVD'. A dual-layer Blu-ray disc can store 50 GB, almost six times the capacity of a dual layer DVD at 8.5 GB. Everything that has been said about CDs/DVDs applies to Blu-ray disks as well.</para>
- <para>Best practice:</para>
- <para>Burn them slowly with a good recorder on archive quality media in an open, non-proprietary format, read the data back to verify, label them with some descriptive text + date & author, lock them away where it is clean, dark, animal safe and dry. And do not forget to copy them over to the next generation of media before you throw away your last piece of hardware or software able to read them.</para>
- </sect4>
- <sect4> <title>Hard disks (hard drives, HDD)</title>
- <para>Disk manufacturers keep their statistics to themselves. A manufacturer guaranty buys you a new disk, but no data. Google for one has done a large scale study on HDD failure mechanisms: <ulink url="http://research.google.com/archive/disk_failures.pdf">Disk Failures study</ulink></para>
- <para>In a nutshell: Disks run longest when operating between 35°C and 45°C, at lower temperatures the error rates increases dramatically. Controller parts (electronics) are the foremost sources of failure, SMART does not diagnose any of this. Some SMART errors are indicative of imminent failure, in particular scan errors and relocation counts. Lifetime expectancy is 4-5 years. </para>
- <para>But all depends much on the real use case and some luck. For example I have a Fujitsu notebook that is running 24/7 since 1998, almost ten years without the slightest hick up. Just luck? In general and contrary to intuition or ecological considerations, running a hard drive permanently results in a longer lifetime than switching it on and off all the time. It has even been reported that aggressive power management spinning down the drive can harm it quickly. Making it working hard shortens the lifetime somewhat. The worst factors for HDD probably are vibrations, shocks, and cold temperatures.</para>
- <para>If your disk is making weird noises, normal file recovery software isn’t going to work. Do a quick backup if that is going to happen to you. (Use dd utility if possible, not a normal file backup since dd reads in a smooth, spiraling stream from beginning to end and doesn't stress the mechanics). There are specialist companies that can recover data from otherwise destroyed drive, but they are costly, plan for 2000$ minimum charge.</para>
- </sect4>
- <sect4> <title>Power surges</title>
- <para>As much as 1% of all computers are affected by lightning and power surges every year.</para>
- <para>(This is about total data loss due to power surges. Of course you can have the occasional data loss due to power loss before saving files. But those losses can normally be restored without major difficulty.)</para>
- <para>You don’t have to wait for the next thunderstorm to be concerned about how a sudden fluctuation in electric power may affect your computer system. Recent statistics have shown that as much as 63 percent of all electronics casualties are due to power problems, and most computers are subject to two or more power anomalies a day. Since power surges or blackouts can occur anywhere and at any time, it only makes sense to protect your computer by investing in some sort of surge protection device.</para>
- </sect4>
-
- <sect4> <title>How surges happen</title>
- <para>A power surge occurs when the power line voltage increases over nominal values for more than 10 milliseconds. Sixty percent of all power surges are caused from within the home or office, generally when a device with a motor (such as a hair dryer, refrigerator, or water pump) shuts off and the power it was using is diverted elsewhere as excess voltage. The remaining 40 percent of power surges are generated by factors such as lightning, utility grid switching, line slapping, poor wiring, and so on.</para>
- <para>While most average electricity-using devices are not affected by power surges, devices relying on computer chips and high-speed microprocessors are susceptible to serious damage. For your computer, power anomalies can result in keyboard lockup, complete data loss, hardware degradation, damaged motherboards, and more. Failure to protect yourself from the inevitable can result in a loss of both time and money.</para>
- </sect4>
- <sect4> <title>Surge protectors</title>
- <para>The most common defense against power surges is a surge protector or suppressor, a device that works by absorbing some of the excess energy and diverting the rest of it to the ground. These are usually found in the form of a power strip (one of those long devices that have six or so outlets and a single, grounded plug). Bear in mind, however, that not every power strip serves as a surge protector. </para>
- <para>When selecting your surge protector, you want to be sure it is listed as meeting the UL 1449 standard, which guarantees a certain minimum of protection. You should also look for one that offers protection against lightning (not every one does) and provides insurance for equipment that is properly attached.</para>
- <para>Because a power surge can follow any path to your computer, be sure that each peripheral connected to your system is protected. This includes your phone line or cable modem, as power can surge through these routes as well. A number of manufacturers are now producing surge suppressors that feature a phone jack for your modem along with the electrical outlets, while others have coaxial cable jacks for those who use a cable modem or TV tuner card.</para>
- <para>If you have a notebook computer, you will want to carry a surge suppressor as well. A variety of suppressors designed specifically for notebooks are available, small in size and possessing both electric and phone outlets that make them ideal for use on the road.</para>
- </sect4>
- <sect4> <title>Uninterruptible power supply (UPS)</title>
- <para>While a surge suppressor will protect your system from minor fluctuations in the power lines, it won’t help you if the power should black out completely. Even an outage of just a few seconds can result in the loss of valuable data, so you might find it worthwhile to invest in an uninterruptible power supply. </para>
- <para>Besides serving as surge suppressors, these devices automatically switch to battery power when a power outage occurs, giving you the opportunity to save data and shut down your system. Some models will even allow you to keep working until power is restored. When purchasing a UPS, be sure that it has the same qualities that you would seek in a surge suppressor, but also check out the battery life and included software.</para>
- <para>Considering the potential risk to your computing system, ensuring its safety from power disturbances is a worthwhile investment. A quality surge suppressor will cost you upward of €20, a 500W UPS can be had for less than €40. It’s a small cost to pay for the peace of mind you’ll gain knowing your computer is well protected. In the very least pull all lines to your computer when you go on holidays.</para>
- </sect4>
- <sect4> <title>Solid state drives: USB sticks, memory cards, flash disks</title>
- <para>SSDs are mechanically more robust than HDDs and suffer much less on that front when they are plugged into the computer. But since they are mostly mobile devices, their exposure to drops, accidents and electrostatic discharges is much higher. So, for different reasons, SDDs are as likely to fail if not more than hard drives. Add the danger of theft and longevity and limited capacity, and SDDs will become prohibitive as permanent data storage devices.</para>
- <para>One major cause for data loss (often recoverable) is the unsafe removal of SDDs from a computer. Before data is saved from a computer memory to any attached device, it remains for some time in buffers. In hard drives this means seconds at most, whereas with SDDs it can be tens of minutes. Therefore, before you disconnect a flash device, always activate data flushing through software (often called "safely remove device").</para>
- <para>There is a new technology trend coming up, to replace hard drives with SSD flash drives. By 2010 they may be competitive in price to HDDs. Data retention is an issue with SDDs, it cannot be overwritten an infinite amount of times. SDDs wear in use. Wear then depends much on the location data is written, and how often it is written. &Linux; has developed a special driver avoiding writing to the same spot too often. But this is all premature information. Keep your eyes and ears open.</para>
- </sect4>
- <sect4> <title>Magnetic media</title>
- <para>Magnetic tapes are used in backup systems, much more in professional environments than in home use. Tapes have issues with data retention and changing technology, but they are safer in one aspect than CDs and DVDs: they are less exposed to scratches and dirt and writing deficiencies. On the other hand they are susceptible to magnetic fields. Throw a magnet next to a tape and it's gone! Tapes should be re-copied every 5-8 years, otherwise too many bits will fail and escape the checksum protection. The downside of magnetic tapes is often the recorder price and the restore time (20x longer than from HDD). Tape backup system have seen their best days. </para>
- </sect4>
- </sect3>
-
- <sect3 id="logical-errors"> <title>Saveguarding against logical errors</title>
- <sect4> <title>Web storage services</title>
- <para>Amazon Web Services includes S3 - Simple Storage Service. With appropriate configuration, you can mount S3 as a drive on &Linux;, Mac, and Windows systems, allowing you to use it as a backup destination for your favorite software. Google Shared Storage is another popular offer where one can store infinite amount of data.</para>
- <para>It is expensive compared to hard drives at home - 40 GB cost $75 a year, 400 GB cost $500. And you have to transfer the images over the (a comparatively slow) Internet.</para>
- <para>I think as a safeguard against localized data loss of the most essential images it's not a bad idea at all, but it is not a general backup solution, much too slow for that.</para>
- <para>Picasaweb (Google), Flickr (Yahoo) and Foto-Community 23hq.com provide online storage services specialist on photographie. Their free space is limited to 1 GB and you don't want to have full resolution images online. But the pro-accounts offer more, in the case of Flickr, dramatically more. For a mere 25$ a year you get unlimited (sic! reality check needed here) space.</para>
- <para>In terms of data retention the web space solution is probably pretty safe. Transmission errors are corrected (thanks to the TCP protocol) and the big companies usually have backup included plus distributed storage so that they are disaster proof within themselves.</para>
- </sect4>
- <sect4> <title>Transmission Errors</title>
- <para>Data does not only get lost from storage devices, it also gets lost when traveling inside the computer or across networks (although the network traffic itself via TCP is error protected). Errors occur on buses and in memory spaces. Consumer hardware has no protection against those bit errors, whereas it is worthwhile to look into such. You can buy ECC (error code correction) protected memory (which is expensive, granted). With ECC RAM at least the memory will be scrubbed for single bit errors and corrected. Double bit errors would escape that scheme but they occur too infrequently. </para>
- <para>
- <inlinemediaobject>
- <imageobject><imagedata fileref="&path;DAM-transmission.png" format="PNG"/></imageobject>
- <textobject> <phrase>Transmission errors</phrase> </textobject>
- </inlinemediaobject>
- </para>
-
- <para>This diagram depicts the transmission chain elements in a computer, all transitions are susceptible to transmission errors. The zfs and btrfs file system at least ensure the OS to disk path of data integrity.</para>
- <para>The Byte Error Rate (BER) for memory and transmission channels is in the order of 1 in 10 Million (10E-7 bit). That just means that <command>1 in 3000 images has an error only due to transmission problems</command>. Now how dramatic that is for an image is left to chance, it could mean that the image is destroyed or that a pixel somewhere changed its value, due to the compression used on almost all images one cannot predict the gravity of a single bit error impact. Often one sees some partial images instead of the full image.</para>
- <para>The worst of all that is that nobody tells you when a transmission error occurs, not your hardware. All those glitches go down unheard until one day you open the photograph, and to your surprise it's broken. It is quite worrisome that there should be no protection within a computer, nobody seems to have thought of it. The Internet (TCP protocol) is much saver as a data path than inside a computer.</para>
- <para>Flaky power supplies are another source of transmission losses because they create interference with the data streams. With normal files systems those errors go unnoticed. </para>
- <para>
- <inlinemediaobject>
- <imageobject><imagedata fileref="&path;DAM-errors.png" format="PNG"/></imageobject>
- <textobject> <phrase>Expected error rate increasing with complexity</phrase> </textobject>
- </inlinemediaobject>
- </para>
- <para>Even if you are not overly concerned today with transmission problems, have a look into the future at illustration. Already in 2010 we'll see thousands of errors per year!</para>
- </sect4>
-
- <sect4> <title>'Oracle' or 'Rising Sun' at the file system horizon?</title>
- <para>ZFS from Sun Microsystems seems to be one of two candidates to deal with disk errors on a low level, and it is highly scalable. It is Open Source, heavily patented, comes with an GPL incompatible license, and is available on Solaris and Leopard. Let us hope that it will soon be available for &Linux; and Windows <ulink url="http://blogs.zdnet.com/storage/?p=169"> (article)</ulink>.</para>
- <para>This is for the courageous ones. <ulink url="http://www.wizy.org/wiki/ZFS_on_FUSE">Fuse ZFS</ulink></para>
- <para>Oracle has also started an initiative with its btrfs file system, which still is in an alpha stage. It employs the same protection technique as zfs does, and it's available on &Linux;, although it is not yet part of the stock kernel.</para>
- </sect4>
- </sect3>
-
- <sect3 id="human-errors"> <title>Human errors</title>
- <sect4> <title>Theft and accidents</title>
- <para>Do not underestimate it! Those two factor account for 86% of notebook and 46% for desktop system data losses. For notebooks, theft counts for 50% alone.</para>
- </sect4>
- <sect4> <title>Malware</title>
- <para>Data loss due to viruses is less grave than common wisdom make you believe. It accounts for less damage than theft or re-installations, for example. And it is limited to Microsoft OS users. Apple users experience very few viruses and under &Linux; they haven't been around for quite some time now.</para>
- </sect4>
- <sect4> <title>Panic is a factor in data loss</title>
- <para>Human error, as in everything, is a major problem in data loss. Take a deep breath and stop! Panic is a common reaction, and people do really stupid things. Experienced users will pull the wrong drive from a RAID array or reformat a drive, destroying all their information. Acting without thinking is dangerous to your data. Stop stressing about the loss and don’t do anything to the disk. Better yet, stop using the computer until you have a plan. Sit down and explain you plan to a laymen or better, laywoman. You will be amazed how many stupid ideas you'll discover yourself in such an exercise.</para>
- <para>If your disk is making weird noises, normal file recovery software isn’t going to work. Do a quick backup if that is going to happen to you. If the drive is still spinning and you can’t find your data, look for a data recovery utility and backup to another computer or drive. (Non-&Linux; users: Google for "free data recovery software" for some options, including one from Ontrack). The important thing is to download them onto another drive, either on another computer, or onto a USB thumb drive or hard disk. It is good practice to save the recovered data to another disk. dd is your friend on *nix systems.</para>
- </sect4>
- </sect3>
-
- <sect3 id="myths-dispelled"> <title>Common myths dispelled</title>
- <para>I'd like to dispel some common myths:</para>
- <itemizedlist>
- <listitem><para>Open Source file systems are less prone to data loss than proprietary systems: Wrong, NTFS is rather a tiny notch better than ext3, ReiserFs, JFS, XFS, to name just the most popular file systems that often come as default FS with distributions. A brilliant article about it is here: <ulink url="http://www.cs.wisc.edu/~vijayan/vijayan-thesis.pdf">link</ulink></para></listitem>
- <listitem><para>Journaling files systems prevent data corruption/loss: Wrong, they only speed up the scan process in case of a sudden interrupt during operation and prevent ambiguous states. But if a file was not entirely saved before the mishap, it'll be lost.</para></listitem>
- <listitem><para>RAID systems prevent data corruption/loss: Mostly wrong, RAID0 and 1 prevent you from nothing, RAID5 can prevent data loss due to disk-failures (but not from disk or file system errors). Many low-end RAID controllers (most mother board controllers are) don’t report problems, figuring you’ll never notice. If you do notice, months later, what is the chance that you’ll know it was the controller’s fault? One insidious problem is corruption of RAID 5 parity data. It is pretty simple to check a file by reading it and matching the metadata. Checking parity data is much more difficult, so you typically won’t see parity errors until a rebuild. Then, of course, it is too late.</para></listitem>
- <listitem><para>Viruses are the biggest thread to digital data: Wrong. Theft, and human errors are the primary cause of data loss.</para></listitem>
- </itemizedlist>
- </sect3>
-
- <sect3 id="storage-budget"> <title>Make your budget: Data size, required storage volume estimation</title>
- <para>Digital camera sensors are 1-2 aperture stops away from fundamental physical limitations. What I mean is this: as technology evolves, there is a natural limit to its progress. Sensitivity and noise characteristics for any kind of light sensor are not far from that limit. </para>
- <para>Today's cameras tend towards 10 mega pixels sensors, although this resolution is already too high for compact cameras and deteriorates the end result. Given the sensor size and quality of optics, 6 mega pixels are optimum for compact cameras. Even DSLR cameras run into their limits at 10-12 mega pixels, for higher resolutions one has to go for full frame sensors (24x36mm) or even bigger formats.</para>
- <para>So, taking into account the manufacturer mega pixel propaganda it seems save to say that the bulk of future cameras will see less than 20 mega pixels. This gives us an estimation for the necessary storage space per photograph in the long run: <15 MB per image. Even if file versioning will be introduced (grouping of variations of a photograph under one file reference), the trend is to implement scripting of changes so that a small overhead will be recorded only and not a whole different image per version. With faster hardware this concept will see it's maturity quite soon.</para>
- <para>In order to estimate the amount of storage space you have to plan for, simply determine the number of photographs you take per year (easy with &digikam;'s timeline sidebar) and multiply it by 15 MB. Most users will keep less than 2000 pictures per year which requires less than 30 GB/year. Assuming that you will change your hard disk (or whatever media in the future) every 4-5 years, the natural increase in storage capacity will suffice to keep you afloat.</para>
- <para>The more ambitious ones out there will need more space, much more maybe. Think of buying a file server, Giga-Ethernet comes integrated into motherboards today and it's a flick to fetch the files over the local network. Speaking about modern mobos: they now have external SATA connectors. This makes it really a trifle to buy an external SATA drive and hook it up to your machine. 1000 GB drives will hit the market this year (2008). These are terrific compact storage containers for backup swapping: keep one drive at home and one somewhere else.</para>
- </sect3>
-
- <sect3 id="backup"> <title>Back it up, backup, backup, recover!</title>
- <para>A 750GB HD costs €100 today. Do not blame anybody else for data loss! 6% of all PCs will suffer an episode of data loss in any given year. Backup your data often according to a plan, and back it up and test the backup before you do anything dramatic like re-installing your OS, changing disks, resizing partitions and so on.</para>
-
- <sect4> <title>Disaster prevention</title>
- <para>Say, you religiously do your backups every day on a external SATA drive. Then comes the day where lightning strikes. Happy you if the external drive was not connected at that moment!</para>
- <para>Disasters strike locally and destroy a lot. Forget about airplane crashes: fire, water, electricity, kids and theft are dangerous enough to our data. They usually cover a whole room or house. </para>
- <para>Therefore disaster control means de-localized storage. Move your backups upstairs, next house, to your bureau (and vise versa), whatever.</para>
- <para>There is another good aspect to the physical separation: as said above, panic is often the cause of destroying data, even the backup data. Having a backup not at hand right away may safe your ass one day.</para>
- </sect4>
- <sect4> <title>Some backup technicalities explained for laymen.</title>
-<itemizedlist>
- <listitem><para>Full Backup: A complete backup of all the files being backed up. It is a snapshot without history, it represents a full copy at one point in time. </para></listitem>
- <listitem><para>Differential Backup: A backup of only the files that have changed since the last full backup. Constitutes a full snapshot of two points in time: the full backup and the last differential one.</para></listitem>
- <listitem><para>Incremental Backup: A backup of only the files that have changed since last whatever backup. Constitutes multiple snapshots. You can recreate the original state at any point in time such a backup was made. This comes closest to a versioning system except that it is only sampled and not continuous.</para></listitem>
-</itemizedlist>
- </sect4>
- <sect4> <title>Best practice: The IT-layman's backup cookbook</title>
-<orderedlist>
- <listitem><para>do a full backup in a external storage device.</para></listitem>
- <listitem><para>verify its data integrity and put it away (disaster control)</para></listitem>
- <listitem><para>have another storage device for frequent backups</para></listitem>
- <listitem><para>swap the devices every other month after having verified data integrity</para></listitem>
-</orderedlist>
- </sect4>
- <sect4> <title>A useful rsync recipe to backups</title>
- <para>Rsync is a wonderful little utility that's amazingly easy to set up on your machines. Rather than have a scripted FTP session, or some other form of file transfer script - rsync copies only the differences of files that have actually changed, compressed and through ssh if you want to for security. That's a mouthful.</para>
- <para>A reasonable backup approach for images could be this one:</para>
-<orderedlist>
- <listitem><para>backup important images right away (after dumping them to a computer) to DVD/optical media</para></listitem>
- <listitem><para>do daily incremental backup of the work space</para></listitem>
- <listitem><para>do a weekly differential backup and delete integral backups of week-2 (two weeks ago)</para></listitem>
- <listitem><para>do a monthly differential backup and delete backup of month-2</para></listitem>
- <listitem><para>if not physically separated already, separate it now (swapping-in another backup drive)</para></listitem>
-</orderedlist>
- <para>This protocol tries to leave you enough time to spot losses and to recover fully at the same time keeping the backup volume at <130% of the working space. You end up with a daily version of the last 7-14 days, a weekly snapshot for at least one month, and a snapshot of every month. Any more thinning should be done by hand after a full verification.</para>
- <para>For German speaking *nix users: <ulink url="http://www.heinlein-support.de/web/rsync-backup/"> link</ulink></para>
- </sect4>
- </sect3>
-
- <sect3 id="technology-review"> <title>Preserve your images through the changes of technology and owners</title>
- <para>Themes: metadata, IPTC stored in image files, XMP files associated, keep the originals, storage, scalability, media, retrieval of images and metadata, copying image data over to the next generation of media, applications, operating systems, virtualization, viewing device... use of the www.</para>
- <para>In order for your valuable images to survive the next 40 years or so (because that's about the time that you will become really interested to revisit those nice old photographs of you as a child, adolescent &etc;) there are two strategies to be observed:</para>
- <orderedlist>
- <listitem><para>Keep up with technology, don't lag behind more than a couple of years.</para></listitem>
- <listitem><para>Save your photos in an open, non-proprietary standard.</para></listitem>
- </orderedlist>
-
- <sect4> <title>How to keep up with technology?</title>
- <para>As the future is unforeseeable by nature, everything said today is to be taken with caution, and to be reviewed as we advance. Unfortunately there is no shortcut possible to some basic vigilance. Every 5-8 years at least one should ask oneself the question of backwards compatibility of current systems. The less variants we used in the past the less questions are to be answered in the future. </para>
- <para>Of course every time you change your computer system (machine, operating system, applications, DRM) you have to ask yourself the same questions. Today, if you want to switch to Windows Vista, you have to ask yourself three times if you still can import your pictures, and, more important so, if you are ever able to move them onto some other system or machine. Chances are good that you cannot. I see many people struggling around me, because Vista enforces a strict DRM regime. How can you proof to Vista that you are actually the owner of your pictures copyright?</para>
- <para>Basically the questions should be answered along the line explained in this document: use and change to open standards supported by a manifold of applications.</para>
- <para>Virtualization becomes available now for everybody. So if you have an old system that is important for reading your images, keep it, install it as a virtual machine for later.</para>
- <para>Otherwise the advice is quite simple: every time you change your computer architecture, your storage and backup technology, your file format, check it out, go through your library and convert to a newer standard if necessary. And keep to open standards.</para>
- </sect4>
-
- <sect4> <title>Scalability</title>
- <para>Scalability is the tech-geek expression of the (easy) capability of a system to be resized, which always means up-sized. </para>
- <para>EMVS /LVM Todo</para>
- <para>Lets assume you planned for scalability and dedicated the container you want to increase to a separate disk or partition. On *nix systems like &Linux; you then can copy and resize the container to the new disk:</para>
- <para>Check with dmesg if your new disk is recognized by the system, but don't mount it.</para>
-<blockquote><screen>
-$ dd if=/dev/sdb[#] of=/dev/sdc # source is /dev/sdb, new disk is /dev/sdc
-$ parted resize /dev/sdc1 0 <disk size in MB> # works on ext2,3, fat16, 32 and reiserfs
-$ resize2fs /dev/sadc1 #resize_reiserfs in case
-</screen></blockquote>
- <para>Todo</para>
- </sect4>
-
- <sect4> <title>Use open, non-proprietary standards as file formats</title>
- <para>The short history of the digital era in the past 20 years has proven over and over again that proprietary formats are not the way to go when you want your data to be intelligible 10 years into the future. Microsoft is certainly the well known culprit of that sort because of its domineering market share. But other companies are actually (if inadvertently) worse since they may not stay long enough in the market at all or have a small user/contributor base only. In the case of Microsoft one has at least the advantage of many people sharing the same problems. Finding a solution has therefore much more success. Still, in some cases Microsoft is using Open Source documentation to understand their own systems, so badly maintained have been their own documentation. Usually with any given MSoffice suite one cannot properly read a document created with the same application two major versions earlier.</para>
- <para>Image formats have had a longer live time than office documents and are a bit less affected by obsolescence.</para>
- <para>Open Source standards have the huge advantage of having an open specification. Even if one day in the future there'll be no software to read it anymore, one can recreate such software, a task becoming simpler every year.</para>
- <para><command>JPEG</command> has been around for a while now, and whilst it's a lossy format losing a bit every time you make a modification and save it, it is ubiquitous, supports JFIF, EXIF, IPTC and XMP metadata, has good compression ratios and can be read by all imaging software. Because of its metadata limitation, lossy nature, absence of transparency and 8 bit color channel depth, we do not recommend it. JPEG2000 is better, can be employed lossless, but lacks in user base.</para>
- <para><command>GIF</command> is a proprietary. patented format and slowly disappearing from the market. Don't use it.</para>
- <para><command>PNG</command> has been invented as a Open Source standard to replace GIF, but it does much more. It is lossless, supports XMP, EXIF and IPTC metadata, 16 bit color encoding and full transparency. PNG can store gamma and chromaticity data for improved color matching on heterogeneous platforms. Its drawback are a relatively big footprints (but smaller than TIFF) and slow compression. We recommend it.</para>
- <para><command>TIFF</command> has been widely accepted as an image format. TIFF can exist in uncompressed form or in a container using a lossless compression algorithm (Deflate). It maintains high image quality but at the expense of much larger file sizes. Some cameras let you save your images in this format. The problem is that the format has been altered by so many people that there are now 50 or more flavors and not all are recognizable by all applications.</para>
- <para><command>PGF</command> "Progressive Graphics File" is another not so known but open file image format. Wavelet-based, it allows lossless and lossy data compression. PGF compares well with JPEG 2000 but it was developed for speed (compression/decompression) rather than to be the best at compression ratio. At the same file size a PGF file looks significantly better than a JPEG one, while remaining very good at progressive display too. Thus it should be well-suited to the web but at the moment few browsers can display it. For more information about the PGF format see the <ulink url="http://www.libpgf.org/">libPGF homepage</ulink>.</para>
- <para><command>RAW</command> format. Some, typically more expensive, cameras support RAW format shooting. The RAW format is not really an image standard at all, it is a container format which is different for every brand and camera model. RAW format images contain minimally processed data from the image sensor of a digital camera or image scanner. Raw image files are sometimes called digital negatives, as they fulfill the same role as film negatives in traditional chemical photography: that is, the negative is not directly usable as an image, but has all of the information needed to create an image. Storing photographs in a camera's RAW format provides for higher dynamic range and allows you to alter settings, such as white balance, after the photograph has been taken. Most professional photographers use RAW format, because it offers them maximum flexibility. The downside is that RAW image files can be very large indeed.</para>
- <para>My recommendation is clearly to <command>abstain from archiving in RAW format</command> (as opposed to shooting in RAW format, which I recommend). It has all bad ingredients: many varieties and proprietary nature. It is clear that in a few years time you cannot use your old RAW files anymore. I have already seen people changing camera, losing their color profiles and having great difficulty to treat their old RAW files correctly. Better change to DNG format!</para>
- <para><command>DNG</command> Digital Negative file format is a royalty free and open RAW image format designed by Adobe Systems. DNG was a response to demand for a unifying camera raw file format. It is based on the TIFF/EP format, and mandates use of metadata. A handful of camera manufacturers have adopted DNG already, let's hope that the main contenders Canon and Nikon will use it one day.</para>
- <para>I strongly recommend converting RAW files to DNG for archiving. Despite the fact that DNG was created by Adobe, it is an open standard and widely embraced by the Open Source community (which is usually a good indicator of perennial properties). Some manufacturers have already adopted DNG as RAW format. And last not least, Adobe is the most important source of graphical software today, and they of course support their own invention. It is an ideal archival format, the raw sensor data will be preserved as such in TIFF format inside DNG, so that the risk associated with proprietary RAW formats is alleviated. All of this makes migration to another operating system a no-brainer. In the near future we'll see 'non-destructive editing', where files are not changed anymore but rather all editing steps will be recorded (into the DNG as it were). When you open such a file again, the editing script will be replayed. This takes computation power, but it is promising as it leaves the original intact and computing power increases all the time. </para>
- <para><command>XML</command> (Extensible Mark-up Language) or <command>RDF</command> (Resource Description Framework). XML is like HTML, but where HTML is mostly concerned with the presentation of data, XML is concerned with the "representation" of data. On top of that, XML is non-proprietary, operating-system-independent, fairly simple to interpret, text-based and cheap. RDF is the WC3's solution to integrate a variety of different applications such as library catalogs, world-wide directories, news feeds, software, as well as collections of music, images, and events using XML as an interchange syntax. Together the specifications provide a method that uses a lightweight ontology based on the Dublin Core which also supports the "Semantic Web" (easy exchange of knowledge on the Web).</para>
-
- <para>IPTC goes XMP</para>
- <para>That's probably one of the reasons why, around 2001, that Adobe introduced its XML based XMP technology to replace the "Image resource block" technology of the nineties. XMP stands for "Extensible Metadata Platform", a mixture of XML and RDF. It is a labeling technology that lets users embed data about a file in the file itself, the file info is saved using the extension".xmp" (signifying the use of XML/RDF). </para>
- <para><command>XMP</command>. As much as ODF will be readable forever (since its containing text is written in clear text), XMP will preserve your metadata in a clearly understandable format XML. No danger here of not being able to read it later. It can be embedded into the image files or as a separate accompanying file (sidecar concept). XMP can be used in PDF, JPEG, JPEG2000, GIF, PNG, HTML, TIFF, Adobe Illustrator, PSD, PostScript, and Encapsulated PostScript. In a typical edited JPEG file, XMP information is typically included alongside Exif and IPTC data.</para>
- <para>Embedding metadata in files allows easy sharing and transfer of files across products, vendors, platforms, customers, without metadata getting lost. The most common metadata tags recorded in XMP data are those from the Dublin Core Metadata Initiative, which include things like title, description, creator, and so on. The standard is designed to be extensible, allowing users to add their own custom types of metadata into the XMP data. XMP generally does not allow binary data types to be embedded. This means that any binary data one wants to carry in XMP, such as thumbnail images, must be encoded in some XML-friendly format, such as Base64.</para>
- <para>Many photographers prefer keeping an original of their shots (mostly RAW) for the archive. XMP suits that approach as it keeps metadata separate from the image file. I do not share this point of view. There could be problems linking metadata file and image file, and as said above, RAW formats will become obsolete. I recommend using DNG as a container and putting everything inside.</para>
- <para><ulink url="http://dublincore.org/">The Dublin Core Metadata Initiative</ulink> is an open organization engaged in the development of interoperable online metadata standards that support a broad range of purposes and business models. DCMI's activities include work on architecture and modeling, discussions and collaborative work in DCMI Communities and DCMI Task Groups, annual conferences and workshops, standards liaison, and educational efforts to promote widespread acceptance of metadata standards and practices.</para>
- </sect4>
- </sect3>
-
- <sect3 id="best-practice"> <title>Best practice: Data protection</title>
- <itemizedlist>
- <listitem><para>Use surge protectors (UL 1449 standard), possibly combined with a UPS</para></listitem>
- <listitem><para>use ECC memory to verify correct data transmission (even just saving files)</para></listitem>
- <listitem><para>watch your hard drives (temperature, noise...), make backups</para></listitem>
- <listitem><para>Keep backups at another location, locked up, use web storage space</para></listitem>
- <listitem><para>use archival media and burners</para></listitem>
- <listitem><para>Don't panic in case of data loss, explain your recovery plan to a layperson</para></listitem>
- <listitem><para>choose you file system, partitions, folders to cater for easy scalability</para></listitem>
- <listitem><para>Use open, non-proprietary standards to manage and save photographs</para></listitem>
- <listitem><para>Do a technology/migration review at least every 5 years</para></listitem>
- </itemizedlist>
- </sect3>
-
- </sect2>
-
- <sect2 id="dam-workflow"> <title>A typical DAM workflow with &digikam;</title>
- <orderedlist>
- <listitem><para>import images from camera, card reader or scanner. As long as the images are stored on the camera media, you can use that as temporary backup.</para></listitem>
- <listitem><para>RAW are converted to DNG and stored away into an RAW archive (not yet implemented)</para></listitem>
- <listitem><para>rate and cull, write-back metadata to the DNG archive</para></listitem>
- <listitem><para>make a backup ⪚ on DVD, optical drive or tape</para></listitem>
- <listitem><para>tag, comment, geo-locate</para></listitem>
- <listitem><para>edit and improve photographs</para></listitem>
- <listitem><para>For layered editing use external applications. Back in &digikam;, re-apply the metadata, which was probably lost or curtailed by the other applications.</para></listitem>
- <listitem><para>run the routine backup with following data-integrity checks</para></listitem>
- <listitem><para>protect processed images for copyrights with Digital Watermarking. Export to web galleries, slide shows, MPEG encode, contact sheets, printing &etc;</para></listitem>
- </orderedlist>
- <para>
- <inlinemediaobject>
- <imageobject><imagedata fileref="&path;DAM-Workflow.png" format="PNG"/></imageobject>
- <textobject> <phrase>Workflow</phrase> </textobject>
- </inlinemediaobject>
- </para>
-
- </sect2>
-
-
- </sect1>
+ &doc-using-dam;
<sect1 id="using-camera"> <title>Using a Digital Camera With &digikam;</title>
<anchor id="camerainterface.anchor"/>
diff --git a/digikam/intro-background.docbook b/digikam/intro-background.docbook
index faf3e4c..0c92270 100644
--- a/digikam/intro-background.docbook
+++ b/digikam/intro-background.docbook
@@ -4,7 +4,7 @@
<title>About &digikam;</title>
<para>
- &digikam; is an advanced digital photo management application for Linux, MacOS and Windows desktop. It provides a simple interface which makes importing and organizing digital photographs a "snap". &digikam; enables you to manage large numbers of digital photographs in Albums and to organize these photographs for easy retrieval using tags (keywords), captions, collections, dates, geolocation and searches. It has many features for viewing, organizing, processing and sharing your images. Thus, &digikam; is a formidable <link linkend="dam">Digital Asset Management</link> (DAM) software including powerful image editing functions.
+ &digikam; is an advanced digital photo management application for Linux, MacOS and Windows desktop. It provides a simple interface which makes importing and organizing digital photographs a "snap". &digikam; enables you to manage large numbers of digital photographs in Albums and to organize these photographs for easy retrieval using tags (keywords), captions, collections, dates, geolocation and searches. It has many features for viewing, organizing, processing and sharing your images. Thus, &digikam; is a formidable <link linkend="using-dam">Digital Asset Management</link> (DAM) software including powerful image editing functions.
</para>
<para>
diff --git a/digikam/index.docbook b/digikam/using-dam.docbook
similarity index 50%
copy from digikam/index.docbook
copy to digikam/using-dam.docbook
index f42d180..8a6233c 100644
--- a/digikam/index.docbook
+++ b/digikam/using-dam.docbook
@@ -1,123 +1,7 @@
-<?xml version="1.0" ?>
-<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.5-Based Variant V1.1//EN" "dtd/kdedbx45.dtd" [
- <!ENTITY kappname "&digikam;"><!-- replace kapp here, do *not* replace kappname-->
- <!ENTITY package "extragear-graphics">
- <!ENTITY % addindex "IGNORE">
- <!ENTITY % English "INCLUDE"><!-- change language only here -->
- <!ENTITY digikam '<application>digiKam</application>'>
-<!-- relative path to snapshots for digikam and showfoto -->
- <!ENTITY path "">
-<!-- introduction -->
- <!ENTITY doc-intro-background SYSTEM "intro-background.docbook">
- <!ENTITY doc-intro-firstrun SYSTEM "intro-firstrun.docbook">
- <!ENTITY doc-intro-fileformats SYSTEM "intro-fileformats.docbook">
- <!ENTITY doc-intro-camerasupport SYSTEM "intro-camerasupport.docbook">
- <!ENTITY doc-intro-pluginsupport SYSTEM "intro-pluginsupport.docbook">
-<!-- using application -->
- <!ENTITY doc-using-mainwindow SYSTEM "using-mainwindow.docbook">
- <!ENTITY doc-using-sidebar SYSTEM "using-sidebar.docbook">
- <!ENTITY doc-using-lighttable SYSTEM "using-lighttable.docbook">
-<!-- image editor -->
- <!ENTITY doc-photo-editing SYSTEM "photo-editing.docbook">
- <!ENTITY doc-editor-color SYSTEM "editor-color.docbook">
- <!ENTITY doc-editor-enhance SYSTEM "editor-enhance.docbook">
- <!ENTITY doc-editor-transform SYSTEM "editor-transform.docbook">
- <!ENTITY doc-editor-filters SYSTEM "editor-filters.docbook">
- <!ENTITY doc-editor-decorate SYSTEM "editor-decorate.docbook">
- <!ENTITY doc-color-management SYSTEM "color-management.docbook">
-<!-- batch queue manager -->
- <!ENTITY doc-bqm-mainwindow SYSTEM "bqm-mainwindow.docbook">
- <!ENTITY doc-bqm-rawconverter SYSTEM "bqm-rawconverter.docbook">
-<!-- tools -->
- <!ENTITY doc-tool-acquireimages SYSTEM "tool-acquireimages.docbook">
- <!ENTITY doc-tool-geolocationeditor SYSTEM "tool-geolocationeditor.docbook">
- <!ENTITY doc-tool-presentation SYSTEM "tool-presentation.docbook">
- <!ENTITY doc-tool-advrename SYSTEM "tool-advrename.docbook">
- <!ENTITY doc-tool-metadataeditor SYSTEM "tool-metadataeditor.docbook">
-<!-- menus -->
- <!ENTITY doc-menu-descriptions SYSTEM "menu-descriptions.docbook">
- <!ENTITY doc-ie-menu SYSTEM "ie-menu.docbook">
- <!ENTITY doc-credits-annexes SYSTEM "credits-annex.docbook">
-
- <!-- Do not define any other entities; instead, use the entities
- from kde-genent.entities and $LANG/user.entities. -->
-]>
-
-<book id="digikam" lang="&language;">
-
-<bookinfo>
-
-<title>The &digikam; Handbook</title>
-
-<copyright>
- <year>2001</year>
- <year>2016</year>
- <holder>The &digikam; developers team</holder>
-</copyright>
-
-<!-- Translators: put here the copyright notice of the translation -->
-<!-- Put here the FDL notice. Read the explanation in fdl-notice.docbook
- and in the FDL itself on how to use it. -->
-<legalnotice>&FDLNotice;</legalnotice>
-
-<date>2016-08-21</date>
-<releaseinfo>5.0</releaseinfo>
-
-<abstract>
-
- <para>
- <inlinemediaobject>
- <imageobject><imagedata fileref="&path;digikamlogo.png" format="PNG"/></imageobject>
- <textobject> <phrase>&digikam; logo</phrase> </textobject>
- </inlinemediaobject>
- </para>
-
- <para>
- &digikam; is a Photo Management Application with support for Digital Cameras.
- </para>
-
-</abstract>
-
-<keywordset>
- <keyword>Digital Camera</keyword>
- <keyword>digiKam</keyword>
- <keyword>Graphics</keyword>
- <keyword>Color Management</keyword>
- <keyword>Metadata</keyword>
- <keyword>RAW format</keyword>
-</keywordset>
-
-</bookinfo>
-
-<!-- *********************************************************************** -->
-
-<chapter id="introduction"> <title>Introduction</title>
-
- &doc-intro-background;
-
- &doc-intro-firstrun;
-
- &doc-intro-fileformats;
-
- &doc-intro-camerasupport;
-
- &doc-intro-pluginsupport;
-
- </chapter>
-
-<!-- *********************************************************************** -->
-
-<chapter id="using-digikam"> <title>Using &digikam;</title>
-
- &doc-using-mainwindow;
-
- &doc-using-lighttable;
-
- &doc-using-sidebar;
-
- <sect1 id="dam"> <title>Digital Asset Management (DAM) with &digikam;</title>
+<sect1 id="using-dam"> <title>Digital Asset Management (DAM) with &digikam;</title>
<para><link linkend="build-dam">Build a system to organize and find your photographs</link></para>
+
<itemizedlist>
<listitem><para><link linkend="case-for-digikam">A case for doing DAM with &digikam;</link></para></listitem>
<listitem><para><link linkend="build-archive">Build the archive: Folder organization, physical layout as information</link></para></listitem>
@@ -127,11 +11,15 @@
<listitem><para><link linkend="captions">Captions/Comments</link></para></listitem>
<listitem><para><link linkend="geotagging">Geolocation (geo-tagging)</link></para></listitem>
</itemizedlist>
+
<para><link linkend="copyright-protect">Protect your authorship and copyright/left</link></para>
+
<itemizedlist>
<listitem><para><link linkend="watermarking">Digital Watermarking (DW)</link></para></listitem>
</itemizedlist>
+
<para><link linkend="data-corruption">Protect your images from data corruption and loss</link></para>
+
<itemizedlist>
<listitem><para><link linkend="physical-deterioation">Physical deterioation</link></para></listitem>
<listitem><para><link linkend="logical-errors">Logical errors</link></para></listitem>
@@ -142,10 +30,11 @@
<listitem><para><link linkend="technology-review">Preserve your images through the changes of technology and owners</link></para></listitem>
<listitem><para><link linkend="best-practice">Best practice: Data protection</link></para></listitem>
</itemizedlist>
+
<para><link linkend="dam-workflow">A typical DAM workflow</link></para>
- <sect2 id="dam-introduction"> <title>Introduction</title>
- <epigraph><para><emphasis>...in the end, photographs need a lot of care.</emphasis> I hope it's you who said this.</para></epigraph>
+ <sect2 id="dam-introduction"> <title>Introduction</title>
+ <epigraph><para><emphasis>...in the end, photographs need a lot of care.</emphasis> I hope it's you who said this.</para></epigraph>
<para>Can you find your digital photographs when you need them? Or do you spend more time sifting through your hard drive and file cabinets than you would like? Do you have a systematic approach for assigning and tracking content data on your photos? If you make a living as a photographer, do your images bear your copyright and contact information, or do they circulate in the marketplace unprotected? Do you want your future grandchildren to admire your photographs you have taken yesterday? How do you ensure backup and the correctness of your data? How to prepare to change your computer, your hard disk, the software, the operating system and still manage to find your pictures or movies?</para>
<para>What is digital asset management - apart from a buzz word? Digital Asset Management (DAM) refers to every part of the process that follows the taking of the picture, all the way through the final output and permanent storage. Anyone who shoots, scans or stores digital photographs is practicing some form of DAM, but most of us are not doing so in a systematic or efficient way.</para>
@@ -172,25 +61,25 @@
<sect3 id="build-archive"> <title>Build the archive: Folder organization, physical layout as information</title>
<para>The first thing to do and to know before you put anything onto your system is a to build an information structure (as opposed to data structure). Your image files have to be somehow organized within the computer, you have to decide if others should have access to your photographs (sharing), if you put them on a dedicated drive, on a network drive &etc; Keep in mind that you have to migrate one day onto some bigger volume. </para>
<para>The organization should be simple, unified and scalable, and it should be independent of the storage medium on which you host them. Do not make the folders too small, several thousand images in one folder is not too much to ask for, but keep them small enough so that they can fit into a backup medium like a DVD 4.7 or 9.4 GB for double sided ones. Remember that the archive will grow all the time! The concrete type of structure depends on your use case of course: Lets take a simple yet frequent example: you are a casual photographer taking pictures of your private life, your family, holidays and so on. It could be efficient to create a structure based on years plus some holiday and export containers. It could look like this:</para>
-<blockquote><screen>2006
-2007
-2008
-Holidays
- - A
- - B
- - C
-Export
-Fun stuff
-</screen></blockquote>
+ <blockquote><screen>2006
+ 2007
+ 2008
+ Holidays
+ - A
+ - B
+ - C
+ Export
+ Fun stuff
+ </screen></blockquote>
<para>Maybe you'll be happy with this structure. Holiday pictures can be quickly found by its location (unless you go to the same place every year), the rest will be organized by date. If you shoot enough pictures you want to create sub folders below the years as months ⪚ 2008-01, 2008-02 &etc; 'Export' would be a container for images to print or to put onto a website.</para>
<para>The more professional photographer will have very different needs as there will be versions of photographs, archives, workflows, a constant influx of images of diverging themes, and a large quantity of everything. Within 10 year you'll have 95% archives and 5% work space files and you don't want to organize your structure around content!</para>
<para>The consideration are these:</para>
-<itemizedlist>
+ <itemizedlist>
<listitem><para>what kind of files go together? Segregation of file type makes batch processing easier. Keep new and old files separate.</para></listitem>
<listitem><para>How can you make that structure scalable?</para></listitem>
<listitem><para>Segregation of original and working files makes it easier to allocate the backup strategy and migration. You will always know if you look for an original or a derivative.</para></listitem>
-</itemizedlist>
+ </itemizedlist>
<para>TBC</para>
</sect3>
@@ -246,14 +135,14 @@ Fun stuff
<para>And now I tell you that this is the Allies landing site "Omaha Beach" in the French Normandie 60 years after the disembarkation. Wow! One starts to dream, have associations, memories, the historical time span is present, you may hear the silence. The caption has totally reframed to perception of this panorama. </para>
<para>For others to appreciate your photographs, the title is probably more important than the image itself for the interest it creates. When you show pictures, tell a story. Remember that the key is to convey the meaning to viewers, to help them understand what you understand about the subject and what moved you.</para>
-<itemizedlist>
+ <itemizedlist>
<listitem><para>let people know what you understand about the subject, why you love it</para></listitem>
<listitem><para>create a red line between the photographs</para></listitem>
<listitem><para>oppose or relate them to different epochs</para></listitem>
<listitem><para>take notes shortly after shooting to remember</para></listitem>
<listitem><para>contemplate, research, watch, and talk - but mostly listen.</para></listitem>
<listitem><para> it's okay if the image is less than perfect because it has the strength to stand on its own merit described in the caption.</para></listitem>
-</itemizedlist>
+ </itemizedlist>
<para>With &digikam; you can enter unlimited amounts of text using internationalized alphabet (UTF-8) as caption. You can enter it for a selection of photos at the same time. When you export images to web services, the captions will be exported at choice into either/or/and caption/title of the web gallery system, no need to re-write the story for publishing.</para>
</sect3>
@@ -261,7 +150,7 @@ Fun stuff
<para>Do you still remember the times before GPS? When you would find your way to another city without navigation system? Wasn't the earth a dull blue ball before GoogleEarth? Well then, with images, the train of spatial representation is running at cruising speed alright. </para>
<para>A few cameras have a GPS receiver built-in, the images come tagged with 3-dimensional coordinates. And with almost any GPS device you're able to extract a trace (of course the receiver needs to be switched-on and carried with you whilst taking the photographs, and for good matching the camera time must be accurately set) and save it onto a computer. You have to store it in gpx format, that's easily done with gpsbabel, gpsman and other tools. You then can automatically match a whole bunch of photos with that track using &digikam;. The coordinates are written into the JFIF part of JPG files (settings choice) and into the database. &digikam; will enable searches based on locations and coordinates, you can create virtual albums of geographical areas! In the right sidebar under the metadata tab you'll find your image located on a local zoom of the world map. A further click brings on anyone of several mapping services on the web, zooming in on details. Even if you don't have a GPS trace you can geo-tag multiple images with a geo-editor. Just navigate on the map to the spot of shooting and click to fix it as a geo-tag. </para>
<para>e.g. conversion of a Garmin track with file name 'xyz':</para>
-<blockquote><screen>$ gpsbabel -w -i mapsource -f xyz.mps -o gpx -F xyz.gpx</screen></blockquote>
+ <blockquote><screen>$ gpsbabel -w -i mapsource -f xyz.mps -o gpx -F xyz.gpx</screen></blockquote>
<para>The possibilities of exploiting this geolocation are already innumerable and will become pervasive in the future. I'm sure one day not too far away we can revisit in a virtual reality our travels through geo-tagged pictures. The &digikam; features include exporting to kml files that can be opened by GoogleEarth (which in turn will show the photos on their shooting site), exporting to gallery2, picasaweb, flickr &etc; with GoogleMaps viewer and more.</para>
</sect3>
</sect2>
@@ -269,7 +158,7 @@ Fun stuff
<sect2 id="copyright-protect"> <title>Protect your authorship and copyleft/right</title>
<para>Themes: watermarking, IPTC and XMP authorship data, export size</para>
<para>This will be the last chapter and step to mark your digital library with authorship, ownership and copyright or -left information. More than in 'the good(?) old days' of paper copies, the ubiquitous Internet makes it just too easy to 'steal' a picture from a web site. At the very least, for all images that will be exported and/or published in any form, the authorship and copyright information should be part of their metadata. Nothing more simple to do with &digikam;: you can setup the default identity, and any images ingested be &digikam; will be automatically informed. I put copyleft in the title for a reason (citation from wikipedia):</para>
-<blockquote><para>"Copyleft is a play on the word copyright and is the practice of using copyright law to remove restrictions on distributing copies and modified versions of a work for others and requiring that the same freedoms be preserved in modified versions.</para>
+ <blockquote><para>"Copyleft is a play on the word copyright and is the practice of using copyright law to remove restrictions on distributing copies and modified versions of a work for others and requiring that the same freedoms be preserved in modified versions.</para>
<para>Copyleft is a form of licensing and may be used to modify copyrights for works such as ... music, and art. In general, copyright law allows an author to prohibit others from reproducing, adapting, or distributing copies of the author's work. In contrast, an author may, through a copyleft licensing scheme, give every person who receives a copy of a work permission to reproduce, adapt or distribute the work as long as any resulting copies or adaptations are also bound by the same copyleft licensing scheme. A widely used and originating copyleft license is the GNU General Public License. Similar licenses are available through Creative Commons - called Share-alike."</para></blockquote>
<para>And here follows a description of what should be supplied to &digikam;'s setup page as information:</para>
<para><command>Author</command> (synonymous with Creator and By-line): This field should contain your name, or the name of the person who created the photograph. If it is not appropriate to add the name of the photographer (for example, if the identity of the photographer needs to be protected) the name of a company or organization can also be used. Once saved, this field should not be changed by anyone. This field does not support the use of commas or semi-colons as separator.</para>
@@ -297,42 +186,44 @@ Fun stuff
<listitem><para>ancient hardware. </para></listitem>
</orderedlist>
<para>Kroll Ontrack, the worlds largest data recovery firm, have some interesting statistics on what actually causes data loss.</para>
-<informaltable>
-<tgroup cols="3">
-<tbody>
-<row>
-<entry>Cause of data loss</entry>
-<entry>Perception</entry>
-<entry>Reality</entry>
-</row>
-<row>
-<entry>Hardware or system problem</entry>
-<entry>78%</entry>
-<entry>56%</entry>
-</row>
-<row>
-<entry>Human error</entry>
-<entry>11%</entry>
-<entry>26%</entry>
-</row>
-<row>
-<entry>Software corruption or problem </entry>
-<entry>7%</entry>
-<entry>9%</entry>
-</row>
-<row>
-<entry>Computer viruses</entry>
-<entry>2%</entry>
-<entry>4%</entry>
-</row>
-<row>
-<entry>Disaster</entry>
-<entry>1-2%</entry>
-<entry>1-2%</entry>
-</row>
-</tbody>
-</tgroup>
-</informaltable>
+
+ <informaltable>
+ <tgroup cols="3">
+ <tbody>
+ <row>
+ <entry>Cause of data loss</entry>
+ <entry>Perception</entry>
+ <entry>Reality</entry>
+ </row>
+ <row>
+ <entry>Hardware or system problem</entry>
+ <entry>78%</entry>
+ <entry>56%</entry>
+ </row>
+ <row>
+ <entry>Human error</entry>
+ <entry>11%</entry>
+ <entry>26%</entry>
+ </row>
+ <row>
+ <entry>Software corruption or problem </entry>
+ <entry>7%</entry>
+ <entry>9%</entry>
+ </row>
+ <row>
+ <entry>Computer viruses</entry>
+ <entry>2%</entry>
+ <entry>4%</entry>
+ </row>
+ <row>
+ <entry>Disaster</entry>
+ <entry>1-2%</entry>
+ <entry>1-2%</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+
<para>So let us analyze those cases step by step!</para>
</sect3>
@@ -462,30 +353,32 @@ Fun stuff
<para>There is another good aspect to the physical separation: as said above, panic is often the cause of destroying data, even the backup data. Having a backup not at hand right away may safe your ass one day.</para>
</sect4>
<sect4> <title>Some backup technicalities explained for laymen.</title>
-<itemizedlist>
- <listitem><para>Full Backup: A complete backup of all the files being backed up. It is a snapshot without history, it represents a full copy at one point in time. </para></listitem>
- <listitem><para>Differential Backup: A backup of only the files that have changed since the last full backup. Constitutes a full snapshot of two points in time: the full backup and the last differential one.</para></listitem>
- <listitem><para>Incremental Backup: A backup of only the files that have changed since last whatever backup. Constitutes multiple snapshots. You can recreate the original state at any point in time such a backup was made. This comes closest to a versioning system except that it is only sampled and not continuous.</para></listitem>
-</itemizedlist>
+ <itemizedlist>
+ <listitem><para>Full Backup: A complete backup of all the files being backed up. It is a snapshot without history, it represents a full copy at one point in time. </para></listitem>
+ <listitem><para>Differential Backup: A backup of only the files that have changed since the last full backup. Constitutes a full snapshot of two points in time: the full backup and the last differential one.</para></listitem>
+ <listitem><para>Incremental Backup: A backup of only the files that have changed since last whatever backup. Constitutes multiple snapshots. You can recreate the original state at any point in time such a backup was made. This comes closest to a versioning system except that it is only sampled and not continuous.</para></listitem>
+ </itemizedlist>
</sect4>
- <sect4> <title>Best practice: The IT-layman's backup cookbook</title>
-<orderedlist>
- <listitem><para>do a full backup in a external storage device.</para></listitem>
- <listitem><para>verify its data integrity and put it away (disaster control)</para></listitem>
- <listitem><para>have another storage device for frequent backups</para></listitem>
- <listitem><para>swap the devices every other month after having verified data integrity</para></listitem>
-</orderedlist>
+
+ <sect4> <title>Best practice: The IT-layman's backup cookbook</title>
+ <orderedlist>
+ <listitem><para>do a full backup in a external storage device.</para></listitem>
+ <listitem><para>verify its data integrity and put it away (disaster control)</para></listitem>
+ <listitem><para>have another storage device for frequent backups</para></listitem>
+ <listitem><para>swap the devices every other month after having verified data integrity</para></listitem>
+ </orderedlist>
</sect4>
- <sect4> <title>A useful rsync recipe to backups</title>
+
+ <sect4> <title>A useful rsync recipe to backups</title>
<para>Rsync is a wonderful little utility that's amazingly easy to set up on your machines. Rather than have a scripted FTP session, or some other form of file transfer script - rsync copies only the differences of files that have actually changed, compressed and through ssh if you want to for security. That's a mouthful.</para>
<para>A reasonable backup approach for images could be this one:</para>
-<orderedlist>
- <listitem><para>backup important images right away (after dumping them to a computer) to DVD/optical media</para></listitem>
- <listitem><para>do daily incremental backup of the work space</para></listitem>
- <listitem><para>do a weekly differential backup and delete integral backups of week-2 (two weeks ago)</para></listitem>
- <listitem><para>do a monthly differential backup and delete backup of month-2</para></listitem>
- <listitem><para>if not physically separated already, separate it now (swapping-in another backup drive)</para></listitem>
-</orderedlist>
+ <orderedlist>
+ <listitem><para>backup important images right away (after dumping them to a computer) to DVD/optical media</para></listitem>
+ <listitem><para>do daily incremental backup of the work space</para></listitem>
+ <listitem><para>do a weekly differential backup and delete integral backups of week-2 (two weeks ago)</para></listitem>
+ <listitem><para>do a monthly differential backup and delete backup of month-2</para></listitem>
+ <listitem><para>if not physically separated already, separate it now (swapping-in another backup drive)</para></listitem>
+ </orderedlist>
<para>This protocol tries to leave you enough time to spot losses and to recover fully at the same time keeping the backup volume at <130% of the working space. You end up with a daily version of the last 7-14 days, a weekly snapshot for at least one month, and a snapshot of every month. Any more thinning should be done by hand after a full verification.</para>
<para>For German speaking *nix users: <ulink url="http://www.heinlein-support.de/web/rsync-backup/"> link</ulink></para>
</sect4>
@@ -512,12 +405,11 @@ Fun stuff
<para>EMVS /LVM Todo</para>
<para>Lets assume you planned for scalability and dedicated the container you want to increase to a separate disk or partition. On *nix systems like &Linux; you then can copy and resize the container to the new disk:</para>
<para>Check with dmesg if your new disk is recognized by the system, but don't mount it.</para>
-<blockquote><screen>
-$ dd if=/dev/sdb[#] of=/dev/sdc # source is /dev/sdb, new disk is /dev/sdc
-$ parted resize /dev/sdc1 0 <disk size in MB> # works on ext2,3, fat16, 32 and reiserfs
-$ resize2fs /dev/sadc1 #resize_reiserfs in case
-</screen></blockquote>
- <para>Todo</para>
+ <blockquote><screen>
+ $ dd if=/dev/sdb[#] of=/dev/sdc # source is /dev/sdb, new disk is /dev/sdc
+ $ parted resize /dev/sdc1 0 <disk size in MB> # works on ext2,3, fat16, 32 and reiserfs
+ $ resize2fs /dev/sadc1 #resize_reiserfs in case
+ </screen></blockquote>
</sect4>
<sect4> <title>Use open, non-proprietary standards as file formats</title>
@@ -581,940 +473,12 @@ Fun stuff
</sect2>
-
- </sect1>
-
- <sect1 id="using-camera"> <title>Using a Digital Camera With &digikam;</title>
- <anchor id="camerainterface.anchor"/>
-
- <sect2> <title>Introduction to Camera Interface</title>
-
- <para>
- The Camera Tool allows you to download your photographs directly from your camera into a &digikam; Album. You can access the Camera Tool by clicking on the Camera menu and selecting from the list of configured cameras. See the <link linkend="setup-camera">Setup Camera Section</link> of the manual for instructions on how to setup &digikam; to work with your camera. If you want to have more information about how &digikam; supports digital cameras, please a take a look at <link linkend="intro-camerasupport">this section</link>.
- </para>
-
- <para>
- The Camera Interface is not the only way to get your photographs into &digikam;. See the <link linkend="using-addphototoalbum">Adding a photograph to an Album</link> section for a description of how to add photographs that are already on your hard disk. But Camera Interface provides a lots of advanced settings to import images into your albums database.
- </para>
-
- <para>
- To be able to use your digital camera with &digikam;, connect the camera to your computer, switch the camera to the image display mode and turn it on. See you camera's user manual if you need more information.
- </para>
-
- <para>
- When you start the Camera Interface, it will try to connect to the Camera. For some cameras this connection phase can take a little while. When connected, a <guilabel>Ready</guilabel> indicator will appear on the bottom and thumbnails of any photographs on the camera will be displayed. Some cameras cannot provide thumbnails of the photographs. If this is the case, you will only see the filenames and a mime-type icon for each item stored by your camera (photograph, movies, sounds, etc).
- </para>
-
- <example> <title>The Camera Client Window</title>
- <screenshot><screeninfo>The Camera Client Window</screeninfo> <mediaobject><imageobject><imagedata fileref="&path;cameraclient.png" format="PNG" /> </imageobject></mediaobject></screenshot>
- </example>
-
- </sect2>
-
- <sect2>
- <title>Getting information about photographs from the Camera</title>
-
- <para>
- Before downloading photographs to your computer, you may wish to see camera item information. Using the
- <menuchoice><guimenuitem>Properties</guimenuitem></menuchoice> and <menuchoice><guimenuitem>Metadata</guimenuitem></menuchoice> side bar tabs from Camera Interface will launch camera item properties and metadata information.
- </para>
-
- <example> <title>The Camera Item Properties Sidebar Tab</title>
- <screenshot><screeninfo>The camera item properties sidebar Tab</screeninfo><mediaobject><imageobject><imagedata fileref="&path;cameraclientitemproperties.png" format="PNG" /> </imageobject></mediaobject></screenshot>
- </example>
-
- <para>
- The Properties tab displays file information recorded by the camera and a resume of photographer information to describe how the image has been taken. A flag indicates if the image has not yet been downloaded to the computer. Note, all this information may be unavailable with some digital cameras.
- </para>
-
- <para>
- The Metadata tab displays an internal picture's metadata like EXIF, Makernotes, GPS, &etc; This information is the same as <link linkend="using-sidebarmetadata">sidebar Meta-Data</link> from the &digikam; main interface or image editor. Note, all these metadata can be unavailable with some digital cameras.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Downloading photographs to your computer</title>
-
- <para>
- The simplest way to download photographs from your camera to your computer is to click the <guilabel>Download</guilabel> button and then click <guilabel>Download All</guilabel>. This will download all of the photographs on the camera to a single Album in &digikam;. The download process will not remove the photographs from the camera. It is always advisable to check that the photographs have downloaded safely into the Album you were expecting before deleting them from the camera.
- </para>
-
- <para>
- If you do not want to download all of the photographs you can select just those that you need using the standard selection methods. Once you have the photographs selected, click <guilabel>Download</guilabel> and then <guilabel>Download Selected</guilabel>. The <guilabel>Download Selected</guilabel> button will be grayed out until you have selected some photographs.
- </para>
-
- <note><para>
- If supported by your camera an option <guilabel>Download new</guilabel> is available. Those are images not yet downloaded by &digikam;. In that case the new images are already marked with a star in the thumbnail window. Obviously if you choose this handy option, it will download the new images only.
- </para></note>
-
- </sect2>
-
- <sect2>
- <title>Selecting a Target Album</title>
- <anchor id="targetalbumdialog.anchor"/>
-
- <para>
- Using <guilabel>Download All</guilabel> or <guilabel>Download Selected</guilabel> buttons will bring up a dialog, that allows you to select a target Album into which the photographs will be downloaded. The list of existing Albums is displayed, ordered by the Folder method (see the <link linkend="using-myalbumsview">Albums View</link> for details of Album ordering). You can select the target Album from this list and then click OK.
- </para>
-
- <example> <title>The Target Album Selection Dialog</title>
- <screenshot><screeninfo>The Target Album Selection Dialog</screeninfo><mediaobject><imageobject><imagedata fileref="&path;cameratargetalbumdialog.png" format="PNG" /> </imageobject></mediaobject></screenshot>
- </example>
-
- <para>
- If you want to create a new Album, into which you could download the photographs, click the <guilabel>New Album</guilabel> button. The new Album will be created as a sub-folder of the Album that is currently selected in the existing Album list. This means that, if you do not want your new Album to be a sub-folder of an existing folder, you must first select the "My Albums" entry from the very top of the existing Albums list before creating a new Album.
- </para>
-
- <para>
- When you have selected the target Album, click OK and &digikam; will download the photographs from the camera to that album.
- </para>
-
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;cameraclientdownload.png" format="PNG" /> </imageobject><textobject><phrase>The Downloading in Progress</phrase></textobject></inlinemediaobject>
- </para>
-
- </sect2>
-
- <sect2>
- <title>Deleting photographs from the camera</title>
-
- <para>
- Once you are happy with the downloaded photographs that you wanted, you are ready to delete photographs from the Camera. You can delete all of the photographs at once by clicking the
- <menuchoice>
- <guimenu>Delete</guimenu>
- <guimenuitem>Delete All</guimenuitem>
- </menuchoice>
- button. If you just want to delete a selection of the photographs, you have to select those that you want to delete and click
- <menuchoice><guimenu>Delete</guimenu>
- <guimenuitem>Delete Selected</guimenuitem></menuchoice>
- </para>
-
- <caution><para>
- Please note that there is no way to restore a photo that you have deleted from the camera. The photographs are not moved to the internal Trash Can, they are removed completely. It is best to double check that you have successfully downloaded a photograph into a &digikam; Album before you delete it from the camera. Anyway, if you plan to empty the camera card, you better do that from the camera menu because it is much quicker.
- </para></caution>
-
- </sect2>
-
- <sect2 id="using-cameraclientrenaming">
- <title>Automatic Renaming</title>
-
- <para>
- Cameras often do not use very meaningful filenames for photographs. The filenames are usually reused once the photographs have been deleted from the camera. This can lead to filename clashes if you download photographs from many shootings into the same Album. It can also be useful to include the date and time that an image was taken into the filename.
- </para>
-
- <example> <title>Files Renaming Options</title>
- <screenshot><screeninfo>Files Renaming Options</screeninfo><mediaobject><imageobject><imagedata fileref="&path;cameraclientsetting1.png" format="PNG" /> </imageobject></mediaobject></screenshot>
- </example>
-
- <para>
- &digikam; can automatically rename your photographs using the date and time information included by the camera in the photograph. To use this feature, click the <guilabel>Settings</guilabel> button on the Camera Interface. The Camera Interface window will expand to reveal some extra features. Select <guilabel>Customize</guilabel> and then enter any filename prefix you would like. As an option you can add many information independently or by combination including : date, time, original file name, file extension, directory, owner, group, camera name, a sequence number or any other metadata from the photograph.
- </para>
- <para>
- </para>
- <para>
- In the next box you find the options for rotating/flipping the image and for date based subalbums. If you check the latter option, folder per day will be automatically generated.
- </para>
- <para>
- The 'On the fly operations' open three more options that act on the photos before storing them on disk. The first two relate to the authors data in <link linkend="author-identity">Default Author Identity</link> settings. If checked, the respective items will be copied into the EXIF tags and IPTC fields. The last option allows a date & time for all downloaded photographs to be set.
- </para>
-
- <tip>
- <para>
- <itemizedlist>
-
- <listitem><para>The sequence number may be needed if you have a camera with a very fast multi-shoot mode where it is possible to get two photographs with exactly the same data and time.
- </para></listitem>
-
- <listitem><para>If you want another date format then the default date format, click on <guilabel>Date & Time...</guilabel>, choose <guilabel>Custom</guilabel> in <guilabel>Format</guilabel> drop-down list and fill in for example "dd.MM.yyyy hh:mm:ss". For more information, read <ulink url="http://doc.qt.digia.com/qt/qdatetime.html#toString">QdateTime</ulink> class reference.</para></listitem>
-
- <listitem><para>When you select <guilabel>Camera filenames</guilabel>, you have the option to change the filenames to lowercase when downloading. Or use uppercase if you prefer.</para></listitem>
-
- </itemizedlist>
- </para>
- </tip>
-
- <para>
- The new filename that &digikam; will use for the photographs when they are downloaded is shown underneath the name provided by the camera in the thumbnail view. The renaming settings will be remembered the next time you use the camera interface.
- </para>
-
- </sect2>
-
- <sect2>
- <title>Camera Information Based Operations</title>
-
- <sect3>
- <title>Automatic Rotation</title>
-
- <para>
- &digikam; can use any information about the orientation of the camera at the moment the photograph was taken for automatic rotation of the photograph when it is downloaded. Not all cameras include this information. See the <link linkend="using-sidebarmetadata">sidebar Meta-Data</link> section for more detail about information that your camera may have embedded in your photographs.
- </para>
-
- <example> <title>On the fly Operations Options</title>
- <screenshot><screeninfo>On the fly Operations Options</screeninfo><mediaobject><imageobject><imagedata fileref="&path;cameraclientsetting2.png" format="PNG" /> </imageobject></mediaobject></screenshot>
- </example>
-
- <para>
- This automatic rotation is switched on by default, and if your camera does not include the information, &digikam; will leave the photograph at its original orientation. If you would like to switch the automatic rotation off, click the <guilabel>Advanced</guilabel> button and deselect the <guilabel>Auto Orient</guilabel> option at the bottom of the window.
- </para>
-
- </sect3>
-
- <sect3>
- <title>Automatic Destination Albums Creation</title>
-
- <para>
- If your camera provides information about the date of the photograph's taking, &digikam; can use this to automatically create subalbums in the destination Album when it is downloaded. Subalbums names will be based on image dates. All images which have the same date will be downloaded into the same subalbum. Not all cameras include this information.
- See the <link linkend="using-sidebarmetadata">
- sidebar Meta-Data</link> section for more detail about
- information your camera may have embedded in your photographs.
- </para>
-
- <example> <title>Albums Auto-creation Options</title>
- <screenshot><screeninfo>Albums Auto-creation Options</screeninfo><mediaobject><imageobject><imagedata fileref="&path;cameraclientsetting3.png" format="PNG" /> </imageobject></mediaobject></screenshot>
- </example>
-
- <para>
- This option is switched off by default and in this case &digikam; will download the photographs
- in the root destination Albums. If you would like to switch on this option click the
- <guilabel>Advanced</guilabel> button and select the <guilabel>Download photo in automatically</guilabel>
- option at the bottom of the window.
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2>
- <title>Uploading Photographs to your camera</title>
-
- <para>
- The simplest way to upload photographs from your computer to your camera is to click the <guilabel>Download</guilabel> button and then click <guilabel>Upload</guilabel>. A standard file selection dialog will appear to select the files from your computer to copying on your camera. You can select more than one file using the standard selection methods.
- </para>
-
- <para>
- When images selection is done, &digikam; will ask you where you want to upload the files on your camera. A camera folder selection dialog will appear. Just select one folder and press OK to start uploading. No images will be removed from your computer.
- </para>
-
- <example> <title>The Camera Folder Selection Dialog</title>
- <screenshot><screeninfo>The Camera Folder Selection Dialog</screeninfo><mediaobject><imageobject><imagedata fileref="&path;camerafolderselectiondialog.png" format="PNG" /> </imageobject></mediaobject></screenshot>
- </example>
-
- <note><para>
- Uploading feature is not supported by all camera drivers.
- </para></note>
-
- </sect2>
-
- <sect2 id="using-gps">
- <title>How to use a GPS device with &digikam;</title>
- <note><para>
- <inlinemediaobject>
- <imageobject><imagedata fileref="&path;handheld_gps.png" format="PNG"/></imageobject>
- </inlinemediaobject>GPS (global positioning system) is used as a generic term throughout this document. It just means a location in latitude and longitude global coordinates that can be displayed on a map. The actual technical implementation that provides the data can be the American GPS, the Russian GLONAS, the European GALILEO or any other system.
- </para></note>
-
- <para>
- Not only for professional photographers can it be interesting to link an image to a precise geographical location. Not everybody uses an airplane to overfly and scan a certain area with automatic GPS data recording. Environmental planners, military, police, construction bureaus, real estate agencies, all will have an immediate application.
- </para>
- <para>
- But if, after some time, one has forgotten where the image was taken, if one loves the nice feature to open with a simple click a browser displaying a zoom of the area, if you like to send your image as a postcard to another &digikam; user (who is then able to locate your shot), or if you simply need the documentation aspect of it - having position data stored in a photo is great.
- </para>
- <para>
- Now, how do we get GPS data into the images? <ulink url="http://www.exiv2.org/tags.html">exiv2</ulink> supports many kinds of the GPS data fields, even bearing, satellite and map references. So the question is really how to get the data into those fields? There are at least three ways to do this: directly with the appropriate hardware, per post-treatment of GPS and image files using the Geolocation Kipi-plugin (<ulink url="help:/kipi-plugins/geolocalization.html">Manual</ulink>) and per 'manual' insertion of known locations.
- </para>
- <itemizedlist>
-
- <listitem><para>Direct GPS data insertion into the image files</para>
- <para>
- To our knowledge there is at the time of writing no camera that integrates a GPS unit. But there are a few that combine with GPS receivers, either as a plug-in card or by data transmission through cable or Bluetooth.
- </para>
- <para><ulink url="http://www.engadget.com.nyud.net:8090/2004/09/17/diy-black-box-tagging-photos-with-gps-coordinates/">Selfmade Howto</ulink>
- </para>
- </listitem>
-
- <listitem><para>Post-treatment of GPS data and image files</para>
- <para>
- Using the Geolocation Kipi-plugin (<ulink url="help:/kipi-plugins/geolocalization.html">Manual</ulink> if Kipi-plugins are already installed).
- </para>
- <para>
- This approach is dead easy: while taking your pictures just keep a GPS device running and carry it around with the camera. Once you are done, download the pictures and the GPS tracks, and run the above plugin. It will correlate the data in the time domain; so it is important that the camera be accurate in its clock setting (the GPS device is always accurate through the satellites). The positional accuracy interpolated from the track points can be as good as 20 meters. Of course, this approach only works if your camera can record EXIF data.
- </para>
- <para>The GPS track download from a device can be managed with the <ulink url="http://gpsman.sourceforge.net/">gpsman</ulink> or <ulink url="http://www.gpsbabel.org">gpsbabel</ulink>. It is important that the downloaded tracks are being stored in gpx format, which is the only one compatible with the Geolocation plugin.
- </para>
- <para>
- Several programs exist for &Windows; and MacOS that are able to extract and correlate data from images and GPS data tracks. The following site provides the same functionality for &Linux;:
- <ulink url="http://freefoote.dview.net/linux_gpscorr.html">gpsCorr</ulink> or
- <ulink url="http://www.carto.net/projects/photoTools/gpsPhoto/">gpsPhoto</ulink>
- </para>
- </listitem>
-
- <listitem>
- <para>'Manual' insertion of known locations</para>
- <para>If you happen to know the latitude/longitude or other data you can use the this script which is a GPS wrapper for Phil Harvey's <ulink url="http://www.sno.phy.queensu.ca/~phil/exiftool">ExifTool</ulink> that uses the signed floating number coordinate notation as produced by maps.google.
- </para>
- </listitem>
-
- </itemizedlist>
-
- <para>
- GPS devices:
- <ulink url="http://www.letsgodigital.org/en/9323/sony_gps_photography/">GPS tracker from Sony </ulink> and
- <ulink url="http://www.emtac.com/products/bluetooth/index.html#btgps">EMTAC bluetooth GPS </ulink>
- </para>
- </sect2>
- </sect1>
-
- <sect1 id="using-setup"> <title>&digikam; Configuration</title>
-
- <sect2 id="setupdialog"> <title>The Setup Section</title>
-
- <anchor id="setupdialog.anchor"/>
-
- <para>
- &digikam; tries to give you as much control over how it works as possible. There are many options that change the behavior of &digikam;. To access these settings select
- <menuchoice><guimenu>Settings</guimenu>
- <guimenuitem>Configure &digikam;</guimenuitem></menuchoice> from the menubar. The configuration dialog is separated into 15 pages. You can change between these pages by clicking on the icons on the left-hand side of the dialog.
- </para>
-
- <itemizedlist>
- <listitem><para><link linkend="setup-album">Album Settings</link></para></listitem>
- <listitem><para><link linkend="setup-collection">Collection Settings</link></para></listitem>
- <listitem><para><link linkend="author-identity">Default Author Identity</link></para></listitem>
- <listitem><para><link linkend="setup-embeddedinfo">Metadata (embedded information)</link></para></listitem>
- <listitem><para><link linkend="setup-tooltip">Tooltip Settings</link></para></listitem>
- <listitem><para><link linkend="setup-mimetype">Mime Type Settings</link></para></listitem>
- <listitem><para><link linkend="setup-lighttable">Light Table Settings</link></para></listitem>
- <listitem><para><link linkend="setup-editor">Image Editor Settings</link></para></listitem>
- <listitem><para><link linkend="setup-saveimages">Save Image Options</link></para></listitem>
- <listitem><para><link linkend="setup-raw-decoder">RAW Decoder Settings</link></para></listitem>
- <listitem><para><link linkend="setup-iccprofiles">ICC Profiles setup</link></para></listitem>
- <listitem><para><link linkend="setup-kipiplugins">Kipi Plugins Settings</link></para></listitem>
- <listitem><para><link linkend="setup-slideshow">Slide show settings</link></para></listitem>
- <listitem><para><link linkend="setup-camera">Camera Interface Settings</link></para></listitem>
- <listitem><para><link linkend="setup-miscellaneous">Miscellaneous Settings</link></para></listitem>
- </itemizedlist>
-
- <sect3 id="setup-album"> <title>Album Settings</title>
-
- <para>
- The Album settings control how the main application will behave.
- </para>
-
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;setupalbum.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
-
- <para>
- The <guilabel>Album Library Path</guilabel> is the location on your hard disk where &digikam; will store all of the Albums. If you change this location without manually moving all of the Albums on the hard disk, &digikam; assumes that there are no existing Albums and will generate a new database at the new location. Your old Albums will not be altered but you will need to change the Album Library Path back to the old location to access them. If you are not sure of what you are doing it is best not to change this location.
- </para>
-
- <para>
- The <guilabel>Thumbnails</guilabel> options are described in the <link linkend="using-imageview">Images</link> section.
- </para>
-
- <para>
- The <guilabel>Click action</guilabel> can be set to <guilabel>Show embedded preview</guilabel> or <guilabel>Start image editor</guilabel>. You herewith define the default behavior of &digikam; when you click on an image item in the main view.
- </para>
-
- </sect3>
-
- <sect3 id="setup-collection"> <title>Collection Settings</title>
-
- <para>
- This dialog manages your Collection types. Album Collections are described in detail in the <link linkend="using-myalbumsview">Albums</link> section.
- </para>
-
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;setupcollections.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
-
- </sect3>
-
- <sect3 id="author-identity"> <title>Default Author Identity for IPTC</title>
-
- <para>
- This page contains the default identity and copyright data as shown on the printscreen below. The data will be automatically written into the respective IPTC data fields if so selected during the download from the <link linkend="using-cameraclientrenaming">camera interface</link>. Also, if you call for database synchronisation, this data will be written into the IPTC fields.
- </para>
-
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;cameraclientidentity.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
-
- <para>This is an extract of the IPTC specifications:</para>
- <itemizedlist>
- <listitem><para>
- <emphasis>Author</emphasis> (is synonymous to <emphasis>Creator</emphasis> and <emphasis>By-line</emphasis>): This field should contain your name, or the name of the person who created the photograph. If it is not appropriate to add the name of the photographer (for example, if the identity of the photographer needs to be protected) the name of a company or organization can also be used. Once saved, this field should not be changed by anyone. This field does not support the use of commas or semi-colons as separator.
- </para></listitem>
-
- <listitem><para>
- <emphasis>Author title</emphasis> (synonymous with <emphasis>By-line title</emphasis>): This field should contain the job title of the photographer. Examples might include titles such as: Staff Photographer, Freelance Photographer, or Independent Commercial Photographer. Since this is a qualifier for the Author field, the Author field must also be filled out.
- </para></listitem>
-
- <listitem><para>
- <emphasis>Credit</emphasis> (synonymous with Provider): Use the credit field to identify who is providing the photograph. This does not necessarily have to be the author. If a photographer is working for a news agency such as Reuters or the Associated Press, these organizations could be listed here as they are "providing" the image for use by others. If the image is a stock photograph, then the group (agency) involved in supplying the image should be listed here.
- </para></listitem>
-
- <listitem><para>
- <emphasis>Source</emphasis>: The Source field should be used to identify the original owner or copyright holder of the photograph. The value of this field should never be changed after the information is entered following the image's creation. While not yet enforced by the custom panels, you should consider this to be a "write-once" field. The source could be an individual, an agency, or a member of an agency. To aid in later searches, it is suggested to separate any slashes "/" with a blank space. Use the form "photographer / agency" rather than "photographer/agency." Source may also be different from Creator and from the names listed in the Copyright Notice.
- </para></listitem>
-
- <listitem><para>
- <emphasis>Copyright Notice</emphasis>: The Copyright Notice should contain any necessary copyright notice for claiming the intellectual property, and should identify the current owner(s) of the copyright for the photograph. Usually, this would be the photographer, but if the image was done by an employee or as work-for-hire, then the agency or company should be listed. Use the form appropriate to your country. For the United States you would typically follow the form of © {date of first publication} name of copyright owner, as in "©2005 John Doe." Note, the word "copyright" or the abbreviation "copr" may be used in place of the © symbol. In some foreign countries only the copyright symbol is recognized and the abbreviation does not work. Furthermore the copyright symbol must be a full circle with a "c" inside; using something like (c) where the parentheses form a partial circle is not sufficient. For additional protection worldwide, use of the phrase, "all rights reserved" following the notice above is encouraged. In Europe you would use: Copyright {Year} {Copyright owner}, all rights reserved. In Japan, for maximum protection, the following three items should appear in the copyright field of the IPTC Core: (a) the word, Copyright; (b) year of the first publication; and (c) name of the author. You may also wish to include the phrase "all rights reserved."
- </para></listitem>
- </itemizedlist>
-
- </sect3>
-
- <sect3 id="setup-embeddedinfo"> <title>Metadata (embedded information settings)</title>
-
- <para>
- Image files can have some meta-data embedded into the image file format. This meta-data can be stored in a number of standard formats. &digikam; can read meta-data in the EXIF format if it is present in the file. &digikam; can also write captions into the <ulink url="http://www.exif.org">EXIF information</ulink>. Writing captions to the EXIF section is limited to JPEG images for now (the exiv2 library is in development and will be extended to PNG and TIFF format metadata embedding in the near future).
- </para>
-
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;setupembeddedinfo.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
-
- <para>
- These settings allow you to control how &digikam; will deal with this embedded information.
- </para>
-
- <para>
- <guilabel>Show images/thumbnails rotated according to orientation tag</guilabel> : this will use any orientation information that your camera has included in the EXIF information to automatically rotate your photographs so that they are the correct way up when displayed. It will not actually rotate the image file, only the display of the image on the screen. If you want to permanently rotate the image on file, you can right-click on the thumbnail and select <guilabel>Auto-rotate/flip according to EXIF orientation</guilabel>. The image will then be rotated on disk and the tag will be reset to "normal". If your camera routinely gets this orientation information wrong you might like to switch this feature off.
- </para>
-
- <para>
- <guilabel>Set orientation tag to normal after rotate/flip</guilabel> : the Auto Rotate option automatically corrects the orientation of images taken with digital cameras that have an orientation sensor. The camera adds an orientation tag to the image's EXIF meta-data. &digikam; can read this tag to adjust the image accordingly. If you manually rotate an image, this meta-data will be incorrect. This option will set the orientation tag to "Normal" after an adjustment, assuming that you rotated it to the correct orientation. Switch this off if you don't want &digikam; to make changes to the orientation tag, when you rotate or flip the image.
- </para>
-
- <para>
- The <guilabel>IPTC Actions</guilabel> will save the data into the respective IPTC fields, which ensures a permanent metadata storage in the image and not only in &digikam;'s database. Thus, metadata is persistent across applications, and may be exported or imported into &digikam; without loss.
- </para>
-
- <para>
- <guilabel>Save image captions as embedded text</guilabel> : this will synchronize the captions that you add to your photographs with those in embedded in the image. This is useful because the captions embedded in the image can be read by other image viewers. Care should be taken if you have images that already have captions embedded in them because these captions will be overwritten by the captions made within &digikam;.
- </para>
-
- </sect3>
-
- <sect3 id="setup-tooltip"> <title>Tooltip Settings</title>
-
- <para>
- This setup page covers all options of information appearing when the mouse hovers over a file in the main view. According the checked options they will be shown or not.
- </para>
-
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;setuptooltip.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
-
- </sect3>
-
- <sect3 id="setup-mimetype"> <title>Mime Type Settings</title>
-
- <para>
- &digikam; can understand lots of different image file types as well as some video and audio formats. To control which types of files &digikam; will try to display you can add or remove file extensions from these lists. Any files that are in the &digikam; Album folders that do not match these extensions will be ignored by &digikam;.
- </para>
- <note><para>The default settings can be easily restored by clicking on the update buttons to the right of each category.</para></note>
-
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;setupmimetypes.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
-
- </sect3>
-
- <sect3 id="setup-lighttable"> <title>Light Table Settings</title>
-
- <para>
- The setting of the &digikam; Light Table can be set to default values on this page so that every time you open the Light Table, these settings are activated (if possible, because for images having different sizes the synchronous mode does not work). The "Load full image size" is only recommended for fast maschines, but if you have one, enable this option for better viewing results.
- </para>
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;setuplighttable.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
-
- </sect3>
-
- <sect3 id="setup-editor"> <title>Image Editor Settings</title>
- <para>
- By default the Image Editor will use a black background behind photographs when they are displayed. If you prefer a different background color you can choose one here. You can also turn off the ToolBar when the Image Editor is in full screen mode.
- </para>
- <para>
- Over and underexposed areas of an image can be indicated by dark and light marker colors that can be defined here. In the editor this viewing mode can be switched on and off with F10 and F11 respectively.</para>
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;setupimageeditor.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
-
- </sect3>
-
- <sect3 id="setup-saveimages"> <title>Save Image Options</title>
-
- <para>
- When changes are made to JPEG files and they are saved back to the hard disk the JPEG file must be re-encoded. Each time a JPEG file is encoded a decision must be made on the level of quality that is to be applied. Unfortunately the level of quality applied is not recorded in the image file. This means that the Image Editor cannot use the same quality ratio when saving an altered image as was used for the original image. You can change the default level of quality that the Image Editor will apply when it saves altered images by moving the <guilabel>JPEG quality</guilabel> slider (1: low quality / 100: high quality and no compression).
- </para>
- <para>
- Chroma subsampling is the practice of encoding images by implementing more resolution for luminance information than for color information. Please read <ulink url="http://en.wikipedia.org/wiki/Chroma_subsampling">this</ulink> Wikipedia article for a full explanation.
- </para>
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;setupsaveimages.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
-
- <para>
- With <guilabel>PNG compression</guilabel> option, you can reduce PNG image files size. This operation does not reduce image quality because PNG uses a lossless algorithm. The only effect is that image data needs more time to compress/decompress. If you have a fast computer you can change this value to use a high compression factor (1: low compression / 9: high compression).
- </para>
-
- <para>
- With <guilabel>Compress TIFF</guilabel> option, you can toggle to use <emphasis>Deflate</emphasis> compression algorithm with TIFF image files. This will reduce TIFF image files sizes. It has no image quality effect because <emphasis>Deflate</emphasis> is a lossless algorithm.
- </para>
-
- <para>
- With the <guilabel>LossLess JPEG 2000 files</guilabel> option allows for lossless storage, or, if the lossy options is selected, even then the quality for comparative files size is much better than normal JPEG. At the time of writing, metadata is not yet supported, but it is in the 'pipeline'.
- </para>
-
- </sect3>
-
- <sect3 id="setup-raw-decoder"> <title>RAW Decoder Settings</title>
-
- <para>
- In the early versions of &digikam; the Image Editor was just a viewer for photographs, but it is rapidly developing into a very useful photo manipulation tool. This dialog allows you to control how the Image Editor will behave.
- </para>
-
- <para><guilabel>16-bit color depth</guilabel></para>
- <para>If enabled, all RAW files will be decoded to 16-bit color depth using a linear gamma curve. To prevent dark image rendering in the editor, it is recommended to use Color Management in this mode. If disabled, all RAW files will be decoded to 8-bit color depth with a BT.709 gamma curve and a 99th-percentile white point. This mode is faster than 16-bit decoding. In 8-bit mode only will the <guilabel>brightness</guilabel> setting be taken into account (dcraw limitation).
- </para>
-
- <para><guilabel>Interpolate RGB as four colors</guilabel></para>
- <para>The default is to assume that all green pixels are the same. If even-row green pixels of the CCD sensor are more sensitive to ultraviolet light than odd-row this difference causes a mesh pattern in the output; using this option solves this problem with minimal loss of detail. To resume, this option blurs the image a little, but it eliminates false 2x2 mesh patterns with VNG quality method or mazes with AHD quality method.</para>
-
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;setuprawfiledecoding.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
-
- <para><guilabel>Use camera white balance</guilabel></para>
- <para>Use the camera's custom white-balance settings if set. Otherwise apply <guilabel>Automatic color balance</guilabel> if this option is set.</para>
-
- <para><guilabel>Automatic color balance</guilabel></para>
- <para>Only used if camera white balance is not set. The default is to use a fixed color balance based on a white card photographed in sunlight.</para>
-
- <para><guilabel>Use Super CCD secondary sensors</guilabel></para>
- <para>For Fuji Super CCD SLR cameras only. Use the secondary sensors, in effect underexposing the image by four stops to reveal detail in the highlights. For all other camera types this option is being ignored.</para>
-
- <para><guilabel>Highlights</guilabel></para>
- <para>This is the story of the three highlight options, courtesy of Nicolas Vilars:</para>
- <para>Default is here to consider highlights (read: part of your images that are burned due to the inability of your camera to capture the highlights) as plain / solid white (<guilabel>solid white</guilabel> option). You can get some fancy results with the <guilabel>unclip</guilabel> option which will paint the highlights in various pinks. At last you can try to consider recovering some parts of the missing information from the highlights (<guilabel>reconstruct</guilabel> option).</para>
- <para>
- This is possible because the blue pixels tends to saturate less quickly than the greens and the reds. &digikam;/dcraw will try to reconstruct the missing green and red colors from the remaining none saturated blue pixels. Of course here everything is a question of tradeoff between how much color or white you want.</para>
- <para>If you select <guilabel>reconstruct</guilabel> as the option, you will be given the choice to set a level. A value of 3 is a compromise and can/should be adapted on a per image basis.</para>
- <note><para>
- A small warning here, for the few curious that have read the man pages of Dcraw, the author says that 5 is the compromise, 0 is solid white and 1 unclip. This is because in &digikam; 0 and 1 are the "solid white" and "unclip" options in the drop down menu (if you select these, the level slider will be grayed out). Therefore, the slider in &digikam; with the "reconstruct" option will let you choose between 0 to 7 (instead of 0 to 9 in Dcraw command line) where 3 is the compromise instead of 5 in "native" Dcraw command line tool.</para></note>
-
- <para><guilabel>Brightness</guilabel> (works in 8 bit mode only)</para>
- <para>
- Set the luminosity to your taste, you probably need to go a little higher than the default = 1. But this can be adjusted later with the image options in the &digikam; image editor. Given the cost in time for demosaicing, stay conservative.
- </para>
-
- <para><guilabel>Quality</guilabel></para>
- <para>
- A <ulink url="http://en.wikipedia.org/wiki/Demosaicing">demosaicing</ulink> algorithm is a digital image process used to interpolate a complete image from the partial raw data received from the color-filtered image sensor internal to many digital cameras in form of a matrix of colored pixels. Also known as CFA interpolation or color reconstruction.</para>
- <para>
- &digikam; and Dcraw offer us three alternatives: bi-linear, VNG interpolation, AHD interpolation. It seems that <emphasis>AHD interpolation</emphasis> (for Adaptive Homogeneity-Directed) is the best choice for quality according to some test that I have performed and the paper of the person that implemented it. <emphasis>VNG interpolation</emphasis> (Variable Number of Gradients) was the first algorithm used by Dcraw but suffers from color artifacts on the edge. <emphasis>Bilinear</emphasis> is interesting if you are looking for speed with a acceptable result.</para>
-
- <para><guilabel>Enable Noise Reduction</guilabel></para>
- <para>
- While demosaicing your image you can additionally ask for noise reduction (at a slight speed penalty). This option applies a noise reduction algorithm while the image still is in CIE Lab color space. Because the noise is only applied to the Luminosity layer (the "L" of the Lab), it should not blur your image as traditional noise reduction algorithms do in RGB mode. So, if you converted an image from RAW and it appears noisy, rather than applying a denoiser, go back and re-convert with this option enabled. The defaults are: <emphasis>Threshold</emphasis> = 100. Higher values will increase the smoothing, lower will decrease smoothing.
- </para>
-
- <anchor id="CA.anchor"/>
- <para><guilabel>Enable chromatic aberration (CA) correction</guilabel></para>
- <para>
- If you know the CA of your lenses you can set the red and blue correction values here. This is certainly the optimal method for CA correction as it is done during RAW conversion.
- </para>
-
- </sect3>
-
- <sect3 id="setup-iccprofiles"> <title>ICC Profiles setup</title>
-
- <para>
- &digikam; is color-management enabled. RAW files - as they come - are not color managed at all. Your camera provides the data it has captured in a raw format and will let you manage all the processing. Every camera has its specifics as to how it captures color information, therefore you will need to apply a specific profile to the images you want to process. Please refer to the section <link linkend="using-iccprofile">ICC color profile management</link> for more details an explanations.
- </para>
- <para>
- Basically, a profile "maps" the color information and gives information on how one should render them. It gives also information to LCMS and &digikam; on how to translate the color information from one color space to an other in order to keep the colors as accurate as possible across all rendring media.
- </para>
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;setupiccprofiles.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
-
- <para>
- <guilabel>Behavior</guilabel> Ask when opening an image in image editor / Launch Color Management tool with RAW files
- </para>
- <para><guilabel>Color Profiles Directory</guilabel>
- Set this to the folder where you store all your profiles ⪚ "/usr/share/color/icc" or "/home/user/.color/icc". &digikam; will scan this folder when starting up.</para>
- <para><guilabel>ICC Profiles Settings</guilabel>
- Here you are given the ability to provide "default" choices for your profiles. Everything is adaptable later-on at the opening of a RAW file.</para>
- <itemizedlist>
-
- <listitem><para>The <guilabel>Use color managed view</guilabel> is an alternative to using Xcalib or Argyll. Only your image will be color managed, not your entire screen! </para></listitem>
-
- <listitem><para>
- You have to provide a workspace profile (linear profiles such as sRGB, ECI-RGB, LStar-RGB, Adobe-RGB or CIE-RGB). If you want to print your images, you may want to opt for Adobe RGB, if it is only for web publishing, sRGB is better (Adobe RGB will be displayed slightly dull in non color managed enabled software such as browsers). However you may change this later of course (by attributing another profile), therefore Adobe RGB can be a good choice for storing and image handling as you can always change it to sRGB before releasing an image for your blog.</para><para>Do not use non-linear profiles as they will change the color-balance</para>
- </listitem>
-
- <listitem><para>
- The input profile should match the camera maker and model you are using. 'Not all profiles are created equal', there are some that have no tone mapping/gamma correction included (Canon). As of now, dcraw does not correct gamma for 16 bit depth conversion, which means that you have to do the tone mapping yourself.</para></listitem>
-
- <listitem><para>
- There are some other options such as the soft proof profile which enables you to emulate, granted that you have a profile for it, how your image will render for a particular device. It is useful before printing for instance because your printer has a smaller gamut than your camera and some colors might look saturated. You may want to fix this manually instead of relying on the "blind" algorithm of your printer.</para></listitem>
-
- </itemizedlist>
-
- <para>
- For most cameras it is pretty obvious what color profile they propose for the type at hand, not so for the Canon's. Here is a table of camera/profiles matches, it is non-authoritative of course:
- </para>
- <informaltable><tgroup cols="2">
- <thead><row>
- <entry>Camera</entry>
- <entry>Profile series</entry>
- </row></thead>
- <tbody>
- <row> <entry>Canon 1D mark II</entry> <entry>6051</entry> </row>
- <row> <entry>Canon 1D mark II</entry> <entry>6111</entry> </row>
- <row> <entry>Canon 1Ds</entry> <entry>6021</entry> </row>
- <row> <entry>Canon 1Ds mark II</entry> <entry>6081</entry> </row>
- <row> <entry>Canon 5D</entry> <entry>6091</entry> </row>
- <row> <entry>Canon 10D</entry> <entry>6031</entry> </row>
- <row> <entry>Canon 20D</entry> <entry>6061</entry> </row>
- <row> <entry>Canon 30D</entry> <entry>6112</entry> </row>
- <row> <entry>Canon 40D</entry> <entry>6101</entry> </row>
- <row> <entry>Canon 300D</entry> <entry>6031</entry> </row>
- <row> <entry>Canon 350D</entry> <entry>6111 or 6071</entry> </row>
- <row> <entry>Canon 400D</entry> <entry>6131</entry> </row>
- </tbody>
- </tgroup>
- </informaltable>
- <para>The Canon profile extension betray the target style: F for Faithful Style, L for Landscape Style, N for Neutral Style, P for Portrait Style, S for Standard Style.
- </para>
-
- <para>Here you find a typical <link linkend="raw-workflow">RAW workflow</link> scenario.</para>
- </sect3>
-
- <sect3 id="setup-kipiplugins"> <title>Kipi Plugins Settings</title>
-
- <para>
- Kipi is an Image Plugin Interface. It is an interface that is supported by a number of image viewer/editor applications. By providing this interface, &digikam; can take advantage of many plugins that are written to work with any application that implements the Kipi interface.
- </para>
-
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;setupkipiplugins.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
-
- <para>
- If your operating system has the Kipi plugins package installed, you will see a list of available plugins. Select those that you want to use and they will be loaded into &digikam;. The plugins will appear as new menu entries in the main menu bar and in the context menu for thumbnails.
- </para>
-
- <para>
- Keyboard shortcuts to actions that plugins perform can be set up in the
- <menuchoice><guimenu>Setting</guimenu>
- <guimenuitem>Configure Shortcuts</guimenuitem></menuchoice> menu.
- </para>
-
- <para>
- For more information about Kipi plugins, you can consult the <ulink url="help:/kipi-plugins/index.html">Kipi-plugins manual</ulink>.
- </para>
-
- </sect3>
-
- <sect3 id="setup-slideshow"> <title>Slide show setup</title>
- <para>The slide show setup should be easy to understand. The upper slider adjusts the time between image transitions; usually a time of 4-5 seconds is good. The other check boxes enable/disable the metadata to be shown on the bottom of the slide show images during display.</para>
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;setupslideshow.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
- </sect3>
-
- <sect3 id="setup-camera"> <title>Camera Interface Settings</title>
-
- <para>
- The camera settings shows on the left of the list of the currently supported cameras. On the right at the top there is an auto-detect button, which tries to identify the camera connected to your computer (make sure that the camera is connected properly to the computer and turned on in the image display mode). Below this are the port settings; the currently supported are Serial, USB, and USB/FireWire Mass Storage.
- </para>
-
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;setupcamera.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
-
- <anchor id="cameraselection.anchor"/>
-
- <para>
- Clicking on a camera in the list on the left will display the supported ports which you can then select. If there is only one supported port it will be automatically selected. At the bottom on the right there is a box for setting the exact path in case of a serial port. Please note that USB interface does not need any paths to be set. If you cannot find your camera on the list, you can try to use a generic Mass Storage device selecting <guilabel>Mounted Camera</guilabel> item in the list.
- </para>
-
- <para>
- At the very bottom is where you set the path for a USB or FireWire (IEEE-1394 or i-link) Mass Storage camera. This box becomes active once you select USB or FireWire Mass Storage camera in the camera list. You need to enter here the path where you mount the camera, usually "/mnt/camera" or "/mnt/removable".
- </para>
-
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;setupaddcamera.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
-
- <para>
- To be able to use your digital camera with &digikam;, connect the camera to your computer, switch the camera to the image display mode and turn it on.
- </para>
-
- <para>
- Try and see if &digikam; can auto-detect the camera; if not, you can set the camera model and port manually. Once you have the camera setup, go to the "Cameras" menu in the main interface and you will see the camera listed in the menu.
- </para>
-
- <note><para>
- You can choose any title you like for the camera in the setup and this title will be used in the main window <guilabel>Cameras</guilabel> menu. If you have more than one camera, you can add them through this setup interface.
-
- </para></note>
-
- </sect3>
-
- <sect3 id="setup-miscellaneous"> <title>Miscellaneous Settings</title>
-
- <para>
- With the <guilabel>Confirm when moving items to trash</guilabel> setting you can set the verbosity of &digikam; when you delete a photograph or an Album. See <link linkend="using-deleteimage">Deleting a Photograph</link> and <link linkend="using-deletealbum">Deleting an Album</link> sections for more details.
- </para>
-
- <para>
- The editorial changes done through the right sidebar can be quietly applied by &digikam; when setting the <guilabel>Apply changes in the right sidebar without confirmation</guilabel> option. Otherwise the changes must be applied by pressing the <guilabel>Apply changes</guilabel> button.
- </para>
-
- <para>
- You can also switch off the display of the splash screen when &digikam; loads. This may speed up the start time of &digikam; slightly.
- </para>
-
- <anchor id="rescan-items" />
- <para>
- <guilabel>Scan for new items at startup</guilabel> option will force &digikam; to scan the album library tree for new items added or removed between &digikam; sessions. This may slow down the start time of &digikam;. If any items have been removed from album library, &digikam; will ask you confirmation before to remove definitely item references in database.
- </para>
-
- <para>
- <inlinemediaobject><imageobject><imagedata fileref="&path;setupmisc.png" format="PNG" /> </imageobject></inlinemediaobject>
- </para>
-
- </sect3>
-
- </sect2>
-
- <sect2 id="setuptheme"> <title>The Theme Setup</title>
-
- <para>
- Color schemes are supplied like themes to personalize &digikam; main interface for you pleasure. To access these settings select
- <menuchoice><guimenu>Settings</guimenu>
- <guimenuitem>Themes</guimenuitem></menuchoice> from the menubar and select your preferred theme to use.
- </para>
- </sect2>
-
- </sect1>
-
-</chapter>
-
-<!-- ****************************************************************************************** -->
-
-<chapter id="image-editor"> <title>The Image Editor</title>
-
- <sect1 id="using-imageeditor"> <title>Introduction to Image Editor</title>
- <anchor id="imageeditor.anchor"/>
-
- <sect2 id="imageeditor-window"> <title>The Image Editor Window</title>
- <para>
- &digikam; incorporates a fast Image Editor with a few basic yet powerful image editing tools. You can use the Image Editor to view your photographs and to make corrections and alterations. The Image Editor can be accessed either by clicking on a thumbnail in the Image Window or by right-clicking on a thumbnail and selecting <guilabel>Edit</guilabel> from the context menu.
- </para>
-
- <para>
- The Image Editor provides a number of tools that enable you to adjust a photograph. Some of these tools are provided by plugins to &digikam;. So they may not be available by default on your distribution. See the <link linkend="setup-kipiplugins">Setup Image Editor Section</link> for more details about Kipi-plugins.
- </para>
-
- <example> <title>The Image Editor Window</title>
- <screenshot><screeninfo>The Image Editor Window</screeninfo><mediaobject><imageobject><imagedata fileref="&path;editorpreview.png" format="PNG" /> </imageobject></mediaobject></screenshot>
- </example>
-
- <para>
- The image editor has just one main window with:
-
- <itemizedlist>
-
- <listitem><para>
- A status at the bottom which shows the filename, the current file number, the current zoom level, and the current image size.
- </para></listitem>
-
- <listitem><para>
- A menu bar across the top and below that a tool bar that provides quick access to some commonly used functions.
- </para></listitem>
-
- </itemizedlist>
- </para>
-
- <para>
- <inlinemediaobject>
- <imageobject><imagedata fileref="&path;editortoolbar.png" format="PNG"/></imageobject>
- <textobject> <phrase>The Image Editor Toolbar</phrase> </textobject>
- </inlinemediaobject>
- </para>
-
- <para>
-
- <orderedlist>
-
- <listitem><para>First Current Album Image.</para></listitem>
-
- <listitem><para>Previous Image.</para></listitem>
-
- <listitem><para>Next Image.</para></listitem>
-
- <listitem><para>Last Current Album Image.</para></listitem>
-
- <listitem><para>Save the modified image.</para></listitem>
-
- <listitem><para>Undoing last action.</para></listitem>
-
- <listitem><para>Redoing previous action.</para></listitem>
-
- <listitem><para>Restore the Current Image From Disk.</para></listitem>
-
- <listitem><para>Zoom Into the Image.</para></listitem>
-
- <listitem><para>Zoom Out of the Image.</para></listitem>
-
- <listitem><para>Toggle Auto Zooming (if selected image will fit in the window).</para></listitem>
-
- <listitem><para>Rotate the Current Image.</para></listitem>
-
- <listitem><para>Crop Image to the Selected Region.</para></listitem>
-
- </orderedlist>
-
- </para>
- </sect2>
-
- <sect2> <title>Restoring Your Original Photograph</title>
-
- <para>
- The editing functions of the Image Editor will make changes to your photograph. None of the editing functions will change the original photograph unless you select
- <menuchoice><guimenu>File</guimenu>
- <guimenuitem>Save</guimenuitem></menuchoice>
- or click the <guilabel>Save</guilabel> button in the tool bar. Note that once you have saved the changed version you will not be able to recover the original photograph.
- </para>
-
- <para>
- You might prefer to take a copy of your photograph before you make any changes. You can use
- <menuchoice><guimenu>File</guimenu>
- <guimenuitem>Save As</guimenuitem></menuchoice>
- to save a working copy.
- </para>
-
- <para>
- At any time <emphasis>before</emphasis> you save your photograph you can restore the view to the original image by selecting
- <menuchoice><guimenu>File</guimenu>
- <guimenuitem>Revert</guimenuitem></menuchoice>
- or clicking the
- <inlinemediaobject>
- <imageobject><imagedata fileref="&path;editorrevertbutton.png" format="PNG"/></imageobject>
- <textobject><phrase>The Image Editor Revert Button</phrase></textobject>
- </inlinemediaobject>
- <guilabel>Revert</guilabel> button on the tool bar. You will lose any changes that you have made to the photograph since it was last saved.
- </para>
-
- </sect2>
-
- <sect2> <title>Undoing/Redoing Actions</title>
-
- <para>
- Almost anything you do to an image in Image Editor can be undone/redone. You can undo the most recent action by choosing <menuchoice><guimenu>Edit</guimenu><guimenuitem>Undo</guimenuitem></menuchoice>, and redo by <menuchoice><guimenu>Edit</guimenu><guimenuitem>Redo</guimenuitem></menuchoice>
- </para>
-
- <para>
- If these are done frequently, you really should memorize the keyboard shortcuts, <guilabel>&Ctrl;-Z</guilabel> to undo an action, and <guilabel>&Ctrl;-Shift-Z</guilabel> to redo an action.
- </para>
-
- <para>
- You have to press the &LMB; over the undo or redo icon in the tool bar and hold it down for a moment to produce a context menu. If you choose one of the menu items, all undo/redo actions until the chosen ones are undone/redone.
- </para>
-
- </sect2>
-
- <sect2> <title>Moving Between Photographs</title>
-
- <para>
- Once you have started the Image Editor you can move between photographs in the same view you started from by using the navigator buttons on the toolbar, <keycap>PgUp</keycap>, <keycap>PgDown</keycap> or the entries in the <guilabel>File</guilabel> menu. If you have made any changes to the current photograph you will be asked if you want to save them.
- </para>
-
- </sect2>
-
- <sect2> <title>Changing the View</title>
-
- <para>
- You can zoom in and out of a photograph using the <keycombo action="press">&Ctrl;<keycap>scroll wheel</keycap></keycombo>, the toolbar icons or the entries in the View menu.
- </para>
- <para>
- To make a photograph fit the window use this button on the tool bar: <guilabel>Zoom Autofit</guilabel>
- <inlinemediaobject>
- <imageobject><imagedata fileref="&path;editorautosizebutton.png" format="PNG"/></imageobject>
- <textobject> <phrase>The Image Editor AutoFit Button</phrase> </textobject>
- </inlinemediaobject>
- </para>
-
- <para>
- <menuchoice><guimenu>View</guimenu>
- <guimenuitem>Full Screen Mode</guimenuitem></menuchoice> will display the photograph using the full screen mode. You can move back to the normal view by pressing the <keycombo>&Esc;</keycombo> key. By default the toolbar is still displayed even in Full Screen Mode. If you would prefer that the toolbar is not displayed you can turn it off in the Configure &digikam; dialog accessed from the main &digikam; window, see the <link linkend="setup-editor">Setup Image Editor Section</link>.
- </para>
-
- </sect2>
-
- <sect2> <title>Printing Images</title>
-
- <para>
- When you want to print the current image from the Image Editor, select
- <menuchoice><guimenu>File</guimenu>
- <guimenuitem>Print image</guimenuitem></menuchoice> (&Ctrl;+P) and you get the standard Print dialog, where you can adjust the settings before printing your photograph.
- </para>
-
- <para>
- From the main window view you can print single images or whole sets of them. Entire thumbnail pages can be printed with your selection. All you need to do is selecting images the standard way and call <menuchoice><guimenu>Image</guimenu> <guimenuitem>Print Assistant</guimenuitem></menuchoice>. Then follow the instructions and choices to make.
- </para>
- </sect2>
-
- </sect1>
-
- &doc-photo-editing;
- &doc-color-management;
-
-</chapter>
-
-<!-- ******** BQM ********************************************************** -->
-
-<chapter id="batch-queue-manager"> <title>The Batch Queue Manager</title>
-
- <sect1 id="bqm-intro"> <title>Introduction to Batch Queue Manager</title>
- <anchor id="bqm.anchor"/>
-
- &doc-bqm-mainwindow;
-
- </sect1>
-
- <sect1 id="bqm-workflow"> <title>Batch Photographic Workflow</title>
-
- &doc-bqm-rawconverter;
-
- </sect1>
-
-</chapter>
-
-<!-- ******** MISC TOOLS *************************************************** -->
-
-&doc-tool-acquireimages;
-&doc-tool-geolocationeditor;
-&doc-tool-presentation;
-&doc-tool-advrename;
-&doc-tool-metadataeditor;
-
-<!-- *********************************************************************** -->
-
-&doc-menu-descriptions;
-
-<!-- *********************************************************************** -->
-
-&doc-credits-annexes;
-
-&documentation.index;
-
-</book>
+</sect1>
+
+<!--
+Local Variables:
+mode: sgml
+sgml-omittag: nil
+sgml-shorttag: t
+End:
+-->
More information about the kde-doc-english
mailing list