HelpSet Table of Contents | Back to Project Home Page |
This screen is used to create, view, update, clone and delete Slide records. In the context of Project Hirtius, "slide" is a generic term that covers pictures in any physical or electronic format, such as old black-and-white prints, color slides, negatives, JPEG or RAW camera files, or even postcards.
The only requirement for you to be able to manage your pictures collection with Project Hirtius is that you devise a matching "tray" management policy to hold them (see Slide Trays Edition Page and Pictures Management Workflow). These "trays" may be represented in the physical world by photo albums, slide trays, boxes of postcards or indeed directory trees on your server.
As for the contents of those pictures, they may represent any subject you wish to investigate, or any "evidence" linked with your research on other Project Hirtius objects, such as Individuals, Events, Sources, etc. Typical examples would be buildings, archaeological artifacts, works of art, portraits, inscriptions, etc.
Please note: Slide objects can be marked as "obsolete" if a better, more relevant shot becomes available (see below). Obsolete slides will be visually identified in 'view' and 'edit' mode by a blue background under the card header and the obsolescence controls. Obsolete slides can be further edited if needed, but a warning will be displayed when doing so.
To reach the Edition Page of an existing Slide:
Of course, you can also reach the Slide view or edition screen through a lot of other ways, such as using search results (see Navigation Tips).
To add a new Slide record:
The Slide Edition Page supports the following actions:
Of these, only Add, Edit, View, Clone and DelCon are entry points. They are typically reached from the Slides List or the Main Application Menu (but in the case of View, there are many more possibilities).
Here below are the fields that you can expect to find on the Slide Edition Page. The goal here is not to simply duplicate the database layout information. If this is what interests you, please refer to the Database Layout, the database creation script or the database itself. The purpose is rather to explain what each field is meant for [D], what format it is expected to follow [F] and what are the conditions for its validity (if applicable) [V].
A star (*) after the name of the field denotes a mandatory field (the star is shown in red with the same meaning in the application user interface).
Object ID* | D | Sequential ID, automatically assigned by the DB during record creation. Hidden in the case of Slides, as we use the Slide ID instead. |
Slide ID* | D | Unique identifier for the Slide, manually given when creating the record (chosen by author based on own policy). |
V | Positive integer larger than zero, unique. | |
Location* | D | Town, village, region where the picture has been taken. Use "Unknown" or similar if unknown. |
Country* | D | Country where the picture has been taken. Select from list. Use special value "Unspecified (--)" if needed. |
Tray* | D | In-Tray address (i.e. defines address of picture in its container:
trayID followed by slot number in a slide tray, pouch number in a photo
album, etc.). The contents of this field should be the result of your chosen Tray Management Policy. Please read Pictures Management Workflow before defining it. |
F | String of typically 6 characters (max. 15). The first 4 (unless defined otherwise -- see $tidlen in the Global Definitions File) represent the tray ID, and the rest (typically 2 or 3, max. 15 - $tidlen) the "address" (= slot number) inside the tray. | |
V | The tray ID part (first $tidlen characters) must match an existing tray. The rest (slot number), once converted to decimal notation if necessary, must be within the range defined for that tray (between 1 and slides_per_tray -- see Slide Trays Edition Page). | |
Description 1* | D | Picture subject description |
F | Free text. HTML markup allowed, but it is recommended to limit its use to simple tags (e.g. italics). Do not terminate by a full stop (.), as these will be added by the application when displaying. | |
Description 2 | D | Picture subject description (continued). Use this second field to provide more specific info on the current slide. E.g. you might have multiple pictures with an identical first description, but then they should each have a second description that allows you to differentiate between them. |
F | Free text. HTML markup allowed, but it is recommended to limit its use to simple tags (e.g. italics). Do not terminate by a full stop (.), as these will be added by the application when displaying. | |
Coordinates | D | Geographical coordinates of the picture subject location (latitude and longitude expressed in degrees, minutes, seconds). Alternatively, as in the case of landscapes, coordinates of your own location when the shot was taken. |
F | Positive integers for degrees and minutes. Positive floats with 2 decimals for the seconds. Both ',' (comma) and '.' (dot) are allowed as decimal markers. | |
V | The value has to be included in the range specific to that field (e.g. 0-90 for long. degrees, 0-59 for minutes, or 0.0-59.99 for seconds). Also, if the degree fields are set, then all the other fields have to be set as well. If the degree fields are empty, the contents of all other fields will be silently ignored. | |
Shot date | D | Date the picture was shot. Can be left empty if unknown (as in the case of e.g. a commercial picture set) -- will then be stored as all zeroes. |
F | ISO format: year in 4 digits, then month in 2 digits (padded with zero
if needed), then day in 2 digits (padded with zero as needed). The date
parts can be separated with either '-' (hyphen), '/' (forward slash), or
'.' (dot). Example: "2012-10-31", "2012/10/31" or "2012.10.31". |
|
Shot type | D | Describes the media (e.g. Color Slide, Black-and-White Digital Still, Color Print, Postcard, etc.). Select from list. The values in that list are defined in the Global Definitions File. |
Subject date | D | Date of the picture subject. You can use '?' if unknown, and 'n/a' when not applicable. You can also leave empty if you prefer. |
F | Free text (to allow for such dates as "2nd half XVIth c."). | |
Can be published | D | Whether or not this picture can be published without the need for any prior vetting. This question is usually rather tricky these days, so you can use this field either to store your "best guess", or the decision resulting from such vetting process. |
Is entry point | D | When you have multiple slides on the same subject (e.g. shot at various angles, or global and detail views), you may prefer to centralize most of you general comments on one of the slide records. In this case, mark that record as "entry point". It will then be visually identified in the lists by a bold red spade (♠) -- unless set otherwise in the Global Definitions File.. |
Quality | D | How good is your picture ? Select from list (four choices, from "Good" to "Bad"). Allows you to easily identify the shots that would benefit from a second take. |
Comment | D | Any comment you might have on the picture itself (the circumstances when the shot was taken), or its subject (its meaning, its history, etc). This is where you would store the bulk of your research concerned specifically with the subject of that picture (of course, a much broader scope of reseach is possible as well, encompassing all supported kinds of objects and any number of them -- please refer to Projects Management Workflow for advice on how to manage that). |
F | Free text. HTML markup allowed. Special formats:
If the object that you refer to doesn't exist (yet) or is not linked to the current object (in the case of Bibref and Srcref), the reference will be rendered in a special style (orange italics) and the associated link will point to that object creation page (where possible). |
|
Reading | D | The text present on the object you shot. Mostly used in the context of epigraphy, paleography, etc. but it can also be put to good use if you take pictures of didactic panels (use 'RAW' mode -- see below) for instance, as their text then becomes searchable. If left empty, this field is omitted in view mode. |
F | Free text. HTML markup allowed. In the case of ancient inscriptions
or manuscripts, the idea is to layout the text in this field as it is
laid out on the original media (in terms of line breaks), and to reproduce
as accurately as possible the actual writing on the stone using special
notations to render abbreviations, missing parts, etc. When rendered
in view mode, the lines will then be automatically numbered. Please note: it is recommended to submit the record once the Reading field has been filled in, if you want the ability to use the Populate button to populate Transcription automatically. Suggested diacritics:
If the object that you refer to doesn't exist (yet) or is not linked to the current object (in the case of Bibref and Srcref), the reference will be rendered in a special style (orange italics) and the associated link will point to that object creation page (where possible). |
|
Transcription | D | Old inscriptions and manuscripts make heavy use of abbreviations, and their alphabet may not entirely match ours (e.g. no distinction between 'u' and 'v' in Latin). They may also use stenography-like shorthands (such as an inverted 'C' for 'centurio' or 'centuria'). Therefore, if you followed the suggestions above to try and reproduce the original text as accurately as possible in the Reading field, you may wish to use the Transcription field to store your fully resolved version of the original text (for search purposes, among others) without any diacritic. E.g. you will often find the following text on headstones: "Ao DNI", which you would write as "A(nn)O D(omi)NI" in the Reading field. You should then also store it as "anno Domini" in Transcription. The Populate button (only visible in 'Edit' mode) will help you do this. If left empty, this field is omitted in view mode. |
F | Free text. HTML markup allowed. Special formats:
If the object that you refer to doesn't exist (yet) or is not linked to the current object (in the case of Bibref and Srcref), the reference will be rendered in a special style (orange italics) and the associated link will point to that object creation page (where possible). |
|
Translation | D | In case the text in the 'Reading' field above is not written in the language of your planned work, you can use this field to store the translation. If left empty, this field is omitted in view mode. |
F | Free text. HTML markup allowed. Special formats:
If the object that you refer to doesn't exist (yet) or is not linked to the current object (in the case of Bibref and Srcref), the reference will be rendered in a special style (orange italics) and the associated link will point to that object creation page (where possible). |
|
See also | D | Use this field to link different objects together, even objects of
different kinds. For instance, you might wish to link the general view
of a subject with detailed shots. Or you might link the picture of a
portrait bust (a Slide object) with the Individual
object where you record the biography of the subject. As long as the list is empty, you only see the Add field. Once some See also entries have been created, you can also select one or more in the list below and check the Remove selected checkbox to remove the selected entries from the list. |
F | One or more object IDs, each composed of a single letter identifying
the object type (see Objects and Metadata Types for a list of supported prefixes --
only fully-fledged objects are eligible here) followed by the numerical
ID of the object. The prefix letter is case-insensitive. To add links to multiple objects at the same time, use a comma and an optional space to separate members in the list. E.g. 'd1242, i43, d239'. |
|
V | Each object ID has to refer to an existing object. Attempts to link the current object to itself will be reported and ignored. | |
Obsoleted by | D | In those cases where you're not satisfied with a shot and you have the opportunity to take a new one, you can use this field to flag the old slide as "obsolete", and link it with its replacement. A slide can only be obsoleted by a single replacement, but any given slide can end up obsoleting (replacing) many. |
F | A Slide ID, i.e. the letter 'D' followed by the numerical ID of the replacement slide. | |
V | The object ID has to refer to an existing object of type Slide and be different from itself. |
This result page appears once you have clicked the Submit button on the Add, Edit or Clone page. It will offer the following links:
See also:
Project Hirtius, © Les Ateliers du Héron, 2012.
Last updated: Thursday, Aug. 22, 2024.
HelpSet Table of Contents | Back to Project Home Page |