documentation:input:images
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| documentation:input:images [2013/08/11 19:34] – [Image & data check] kmartinez_nhm | documentation: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:// | + | {{ https:// |
| You will end up here: | You will end up here: | ||
| - | {{ https:// | + | {{ https:// |
| The window is divided into two parts: | The window is divided into two parts: | ||
| - **The general commands**\\ These control elements are the actual means of communication. | - **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. | - **The tabbed windows** \\ These windows represent different approaches to process data from the archive. | ||
| - | |||
| - | |||
| ==== General elements ==== | ==== General elements ==== | ||
| === Server === | === Server === | ||
| Line 31: | 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// | 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// | ||
| - | {{ https:// | + | {{ https:// |
| === X missing Pics === | === X missing Pics === | ||
| Line 42: | Line 40: | ||
| This column tells you how many and which database entries have faulty numbers. Clicking on the name will open the //Edit Specimens// | This column tells you how many and which database entries have faulty numbers. Clicking on the name will open the //Edit Specimens// | ||
| ==== Server consistency ==== | ==== Server consistency ==== | ||
| - | This field shows information | + | This field shows information |
| - | + | ||
| - | {{https:// | + | |
| + | {{ https:// | ||
| ==== image list ==== | ==== image list ==== | ||
| - | This is simply a list of all images on the chosen server. | + | This is simply a list of all the images on the chosen server. |
| - | + | ||
| - | {{https:// | + | |
| + | {{ https:// | ||
| ==== thread logs ==== | ==== thread logs ==== | ||
| - | In the thread logs tab, you can see the messages that the archive produced, | + | In the thread logs tab, you can see the messages that the archive |
| If you pick a date, and click on //List Threads// all log-files **from that date until today** are shown. | If you pick a date, and click on //List Threads// all log-files **from that date until today** are shown. | ||
| - | Usually, the server 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. | + | The server |
| > 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:// | + | {{ https:// |
| 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:// | + | {{ https:// |
| Imports that fail, have to be forced. | Imports that fail, have to be forced. | ||
| === Forcing import === | === Forcing import === | ||
| - | If a picture that is in the archive, should be overwritten by a new picture, this has to follow | + | If a picture that is in the archive, should be overwritten by a new picture, this has to be done following |
| - First, take the new picture, move it to the import folder, and let the overnight import run. (Alternatively, | - First, take the new picture, move it to the import folder, and let the overnight import run. (Alternatively, | ||
| - | - 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 design) | + | - 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 failed, look up the right day in a thread log. | + | - After the import |
| - 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. | ||
| - | - For each one of them, click on them, click on //Yes// when asked to force the import, and wait until the message pops up that it was 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: | + | - After all of the rescans have been added this way, click on [[documentation: |
| - | {{https:// | + | {{ https:// |
| - | + | ||
documentation/input/images.1376249683.txt.gz · Last modified: by kmartinez_nhm
