JACQ Documentation

User Tools

Site Tools

Trace: • images
documentation:input:images

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
documentation:input:images [2013/08/11 19:50] – [thread logs] kmartinez_nhmdocumentation:input:images [2015/01/30 12:59] (current) – [thread logs] armin_loeckher
Line 6: Line 6:
 A click on the Images button opens a window for the image handling system.  A click on the Images button opens a window for the image handling system. 
  
-{{  https://docs.google.com/drawings/d/12IiXtRVyoMqng4cKEdGm4zhBXJXirM7wcoU8tbbr-bw/pub?w=587&h=409&.png?587x409 | button}}+{{  https://docs.google.com/drawings/d/12IiXtRVyoMqng4cKEdGm4zhBXJXirM7wcoU8tbbr-bw/pub?w=587&h=409&.png?587x409 | images - button}}
  
 You will end up here: You will end up here:
  
-{{  https://docs.google.com/drawings/d/1ze5KseBDGRvm0MMq8NFg0YCw7aJxMMiy8gt8fTtxR-Y/pub?w=902&h=682&.png?902x682  | mask}}+{{  https://docs.google.com/drawings/d/1ze5KseBDGRvm0MMq8NFg0YCw7aJxMMiy8gt8fTtxR-Y/pub?w=902&h=682&.png?902x682  | images - mask}}
  
 The window is divided into two parts: The window is divided into two parts:
Line 29: Line 29:
 You can use the institution and family-field to narrow your search, then click either on //Get last Scan// or //Get last Scan with Faulty HerbNumbers//. The result will look like this: You can use the institution and family-field to narrow your search, then click either on //Get last Scan// or //Get last Scan with Faulty HerbNumbers//. The result will look like this:
  
-{{  https://docs.google.com/drawings/d/1Oh5LruBBtQvML7fMNKksK0cGh57rSVClzKFMMds6CDw/pub?w=914&h=666&.png?914x666  | check}}+{{  https://docs.google.com/drawings/d/1Oh5LruBBtQvML7fMNKksK0cGh57rSVClzKFMMds6CDw/pub?w=914&h=666&.png?914x666  | images - check}}
  
 === X missing Pics === === X missing Pics ===
Line 42: Line 42:
 This field shows information on the consistency of the archive and the viewer. This should be empty. If its not, contact the person in charge of the archive.  This field shows information on the consistency of the archive and the viewer. This should be empty. If its not, contact the person in charge of the archive. 
  
-{{  https://docs.google.com/drawings/d/1ZZ1kO11KLjB_DTIUIfIW8Y3kjjhFd2V06cJhv0hS1ys/pub?w=612&h=192&.png?612x192  | consistency}}+{{  https://docs.google.com/drawings/d/1ZZ1kO11KLjB_DTIUIfIW8Y3kjjhFd2V06cJhv0hS1ys/pub?w=612&h=192&.png?612x192  | images - consistency}}
 ==== image list ==== ==== image list ====
 This is simply a list of all the images on the chosen server.  This is simply a list of all the images on the chosen server. 
  
-{{  https://docs.google.com/drawings/d/13yVwkjYn3wIq9dx8nwlDqDFwo1coD5mA_u0FtVwFHj0/pub?w=832&h=692&.png?832x692  | list}}+{{  https://docs.google.com/drawings/d/13yVwkjYn3wIq9dx8nwlDqDFwo1coD5mA_u0FtVwFHj0/pub?w=832&h=692&.png?832x692  | images - list}}
 ==== thread logs ==== ==== thread logs ====
 In the thread logs tab, you can see the messages that the archive has produced, whilst importing the images.  In the thread logs tab, you can see the messages that the archive has produced, whilst importing the images. 
Line 54: Line 54:
  
 > If the thread log is empty when you click on it, close it and open it again, this happens often. > If the thread log is empty when you click on it, close it and open it again, this happens often.
-{{  https://docs.google.com/drawings/d/12J_qS00xlQAW6GtRy8EWCt4goinF8UyKPkQ-dk1wtbc/pub?w=846&h=626&.png?846x626  | threadlogs}}+{{  https://docs.google.com/drawings/d/12J_qS00xlQAW6GtRy8EWCt4goinF8UyKPkQ-dk1wtbc/pub?w=846&h=626&.png?846x626  | images - threadlogs}}
  
 If there are images to be exported, where there are already images in the archive, the import will fail and leave a message in the thread log. This might look like this:  If there are images to be exported, where there are already images in the archive, the import will fail and leave a message in the thread log. This might look like this: 
  
-{{  https://docs.google.com/drawings/d/1IE-l2UMFhLEKTo4UmX3vSl7APIrCEfnIk2OS4RS7ytA/pub?w=1062&h=640&.png?1062x640  | thread_logs_2}}+{{  https://docs.google.com/drawings/d/1IE-l2UMFhLEKTo4UmX3vSl7APIrCEfnIk2OS4RS7ytA/pub?w=1062&h=640&.png?1062x640  | images - thread_logs_2}}
  
 Imports that fail, have to be forced.  Imports that fail, have to be forced. 
Line 68: Line 68:
   - All the rescans you did this way should show up as error messages in the thread logs.    - All the rescans you did this way should show up as error messages in the thread logs. 
   - Click on each one of them, click on //Yes// when asked to force the import, and wait until the message pops up that it has been added.    - Click on each one of them, click on //Yes// when asked to force the import, and wait until the message pops up that it has been added. 
-  - After all of the rescans have been added this way, click on [[documentation:input:images#ImportPictures|ImportPictures]], to force their import. You can refresh the thread log page. When the end date of the new thread log is no longer 1.1.1970, the import has finished. +  - After all of the rescans have been added this way, click on [[documentation:input:images#ImportPictures|ImportPictures]], to force their import. You can refresh the thread log page. When the end date of the new thread log is no longer 1.1.1970, the import has finished. This step is **mandatory**, otherwise recently added images will not be imported. 
-{{  https://docs.google.com/drawings/d/1LAmwIaWipxdl_Nga4V1gOs-OiciJIbr1veGsLwXBJsY/pub?w=764&h=502&.png?764x502  | thread_logs_confirm}}+{{  https://docs.google.com/drawings/d/1LAmwIaWipxdl_Nga4V1gOs-OiciJIbr1veGsLwXBJsY/pub?w=764&h=502&.png?764x502  | images - thread_logs_confirm}}
documentation/input/images.1376250630.txt.gz · Last modified: by kmartinez_nhm