Changeset View
Changeset View
Standalone View
Standalone View
core/data/scripts/digitaglinktree/digitaglinktree.1
| Context not available. | |||||
| 39 | by changing directory to the folder with the tags name created by this script. | 39 | by changing directory to the folder with the tags name created by this script. | ||
|---|---|---|---|---|---|
| 40 | This allows you e.g. to run JAlbum a photo album software that needs to find the | 40 | This allows you e.g. to run JAlbum a photo album software that needs to find the | ||
| 41 | pictures to be put into a web album in the filesystem because JAlbum cannot | 41 | pictures to be put into a web album in the filesystem because JAlbum cannot | ||
| 42 | access digikams virtual folders directly. | 42 | access digikam's virtual folders directly. | ||
| 43 | 43 | | |||
| 44 | 44 | | |||
| 45 | The second way of calling this script is the so called archive-mode by setting | 45 | The second way of calling this script is the so called archive-mode by setting | ||
| 46 | option -A \fIarchiveDir\fR. | 46 | option -A \fIarchiveDir\fR. | ||
| 47 | 47 | | |||
| 48 | Archive mode is thought for people who want to archive tagged photos | 48 | Archive mode is thought for people who want to archive tagged photos | ||
| 49 | independently of digikams root directories and the photos therein. This way you | 49 | independently of digikam's root directories and the photos therein. This way you | ||
| 50 | can put your photos and their tag structure in eg. a tar archive and send it to | 50 | can put your photos and their tag structure in eg. a tar archive and send it to | ||
| 51 | a friend, who can look at the photos via their tag structure. In this mode the | 51 | a friend, who can look at the photos via their tag structure. In this mode the | ||
| 52 | script creates the directory given as parameter to -A and in this directory two | 52 | script creates the directory given as parameter to -A and in this directory two | ||
| Context not available. | |||||
| 93 | The Tags subdirectory will contain links to the files in | 93 | The Tags subdirectory will contain links to the files in | ||
| 94 | the Photos directory. This way you have one archive directory that is completely | 94 | the Photos directory. This way you have one archive directory that is completely | ||
| 95 | self contained. You can tar it, send it to a friend or just put it somewhere | 95 | self contained. You can tar it, send it to a friend or just put it somewhere | ||
| 96 | for archivel or backup purposes. Usually only those photos will be archived that | 96 | for archival or backup purposes. Usually only those photos will be archived that | ||
| 97 | have a digikam tag set on them. By using option -C however you can perform a | 97 | have a digikam tag set on them. By using option -C however you can perform a | ||
| 98 | complete archive. See -C for more infos. | 98 | complete archive. See -C for more info. | ||
| 99 | 99 | | |||
| 100 | .TP | 100 | .TP | ||
| 101 | \fB \-d \fIdatabase\fR | 101 | \fB \-d \fIdatabase\fR | ||
| 102 | \fIdatabase\fR is the complete path including the filename to digikams photo database which | 102 | \fIdatabase\fR is the complete path including the filename to digikams photo database which | ||
| 103 | usually can be found in digikams root directory. The files name is usually | 103 | usually can be found in digikam's root directory. The files name is usually | ||
| 104 | digikam.db . | 104 | digikam.db . | ||
| 105 | 105 | | |||
| 106 | .TP | 106 | .TP | ||
| 107 | \fB \-r \fIrootdir\fR | 107 | \fB \-r \fIrootdir\fR | ||
| 108 | \fIrootdir\fR denotes the digikam base directory containing all your photos if you are using | 108 | \fIrootdir\fR denotes the digikam base directory containing all your photos if you are using | ||
| 109 | digikam in a version before 0.10. If you are using digikam 0.10 or newer you must not | 109 | digikam in a version before 0.10. If you are using digikam 0.10 or newer you must not | ||
| 110 | use this option. If you do it anyway you will see a hint that the option given will be ignored because | 110 | use this option. If you do it anyway you will see a hint that the option given will be ignored because | ||
| 111 | digikams version 0.10 database contains the root directories of all albums defined in digikam. | 111 | digikam's version 0.10 database contains the root directories of all albums defined in digikam. | ||
| 112 | 112 | | |||
| 113 | .TP | 113 | .TP | ||
| 114 | \fB \-C\fR | 114 | \fB \-C\fR | ||
| Context not available. | |||||
| 124 | By default the script will try to create relative symbolic links from the | 124 | By default the script will try to create relative symbolic links from the | ||
| 125 | directory \fItaglinkdir\fR set by option -l to the photo files under | 125 | directory \fItaglinkdir\fR set by option -l to the photo files under | ||
| 126 | \fIrootdir\fR given by option -r. Using this option will result in absolute symbolic | 126 | \fIrootdir\fR given by option -r. Using this option will result in absolute symbolic | ||
| 127 | links beeing created instead of relative ones. | 127 | links being created instead of relative ones. | ||
| 128 | 128 | | |||
| 129 | .TP | 129 | .TP | ||
| 130 | \fB \-H \fR | 130 | \fB \-H \fR | ||
| Context not available. | |||||
| 136 | 136 | | |||
| 137 | .TP | 137 | .TP | ||
| 138 | \fB \-f \fR | 138 | \fB \-f \fR | ||
| 139 | In digikam photos can have hierachical tags (tags that have subtags). In this case | 139 | In digikam photos can have hierarchical tags (tags that have subtags). In this case | ||
| 140 | digitaglinktree would by default add a directory for the tag and a subdirectory for | 140 | digitaglinktree would by default add a directory for the tag and a subdirectory for | ||
| 141 | each of the subtags of this tag. By setting \fB \-f \fR a subtag is treated like a | 141 | each of the subtags of this tag. By setting \fB \-f \fR a subtag is treated like a | ||
| 142 | regular tag just as its parent tag so digitaglinktree will create all subdirectories | 142 | regular tag just as its parent tag so digitaglinktree will create all subdirectories | ||
| 143 | for tags and subtags at the same level independent of the tag - subtag hierarchy. | 143 | for tags and subtags at the same level independent of the tag - subtag hierarchy. | ||
| 144 | 144 | | |||
| 145 | .TP | 145 | .TP | ||
| Context not available. | |||||
| 216 | digiTagLinktree -l /home/user/tags | 216 | digiTagLinktree -l /home/user/tags | ||
| 217 | -d /home/user/photos/digikam.db | 217 | -d /home/user/photos/digikam.db | ||
| 218 | 218 | | |||
| 219 | In this example digikams photo root denoted by -r is /home/user/photos. | 219 | In this example, digikam's photo root denoted by -r is /home/user/photos. | ||
| 220 | 220 | | |||
| 221 | Option -l /home/user/tags | 221 | Option -l /home/user/tags | ||
| 222 | tells the script that all the subdirectories and symbolic links will be placed in | 222 | tells the script that all the subdirectories and symbolic links will be placed in | ||
| 223 | the directory /home/user/tags. The folder was chosen so that the tags-directory is not under digikams photo root. You may put the tags folder inside digikams photoroot but this is not the preferred method. | 223 | the directory /home/user/tags. The folder was chosen so that the tags-directory is not under digikam's photo root. You may put the tags folder inside digikam's photoroot but this is not the preferred method. | ||
| 224 | Because the link directory contains only links this tag structure does hardly need any additional space on your harddisk. | 224 | Because the link directory contains only links this tag structure does hardly need any additional space on your harddisk. | ||
| 225 | 225 | | |||
| 226 | digiTagLinktree -r /home/user/photos -l /home/user/tags | 226 | digiTagLinktree -r /home/user/photos -l /home/user/tags | ||
| 227 | -d /home/user/photos/digikam.db | 227 | -d /home/user/photos/digikam.db | ||
| Context not available. | |||||