===== Images =====


>Direct access to the image archive is not available (this is intentional, as it is likely that direct handling of the archived files would lead to mistakes, such as deleted files). Therefore, this window is available as a means of communicating with the archive.

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 | images - button}}

You will end up here:

{{  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 general commands**\\ These control elements are the actual means of communication.
  - **The tabbed windows** \\ These windows represent different approaches to process data from the archive.
==== General elements ====
=== Server ===
The field **server** lets you choose the server that hold the images you wish to look at.
=== ImportPictures ===
This button behaves in two different ways:
   - Usually, this will force a full image import of the chosen server.
   - If there are [[documentation:input:images#Forcing_import|forced]] images, only these will be imported.
=== Rescan Server ===
The information in the tabbed views depends on the last time the server was scanned. If one suspects this to be out of date, one can issue a rescan with this button. 
==== Image & data check ====
> Before using this, make sure that you have selected the correct server!

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  | images - check}}

=== X missing Pics ===
This column tells you which database entries have the //dig. image// box checked, but no image in the archive. Clicking on a number will open the //Edit Specimens//-field.
=== X missing database entries ===
This column tells you which images have been taken, but contain no database entry. Clicking on the number will open a simple data entry sheet to enter the specimen.
=== X missing database checks ===
This column tells you for which images, entries exist that are marked //checked// but not //dig. image//. Clicking on the number will open the //Edit Specimens//-window. 
=== X faulty database entries ===
This column tells you how many and which database entries have faulty numbers. Clicking on the name will open the //Edit Specimens//-form. This information is only given if requested by the right button. 
==== Server consistency ====
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  | images - consistency}}
==== image list ====
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  | images - list}}
==== thread logs ====
In the thread logs tab, you can see the messages that the archive has produced, whilst importing the images. 
If you pick a date, and click on //List Threads// all log-files **from that date until today** are shown.

The server usually runs the routine import at 2:30am, so there should always be a log at that time. If you want to read the messages of the log, click on the corresponding line. 

> 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  | 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: 

{{  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. 
=== Forcing import ===
If a picture that is in the archive, should be overwritten by a new picture, this has to be done following these steps:
  - First, take the new picture, move it to the import folder, and let the overnight import run. (Alternatively, the import can be triggered right away by clicking [[documentation:input:images#ImportPictures|ImportPictures]])
  - This will fail, because there is already a picture under that name in the archive. (This step can't be skipped, because the import has to fail once by default)
  - After the import has failed, look up the corresponding day in the thread log.
  - 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. 
  - 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  | images - thread_logs_confirm}}