Overview
Second Site supports TMG's printer codes such as [BOLD:]
, etc., but it also includes support for codes that are only recognized by Second Site. Using TMG's [HID:]
and [:HID]
codes, you can include the SS-only codes in your TMG data but prevent TMG from attempting to process them.
In addition to the codes shown on this page, there are codes that are part of the Flag Events facility.
SS
Second Site supports [SS:]text[:SS]
, a special formatting code that makes it possible to restrict selected text to Second Site only. You can use this code if you want a portion of a memo to be processed only by Second Site.
The [SS:]text[:SS]
code is designed to be used in conjunction with TMG's [HID:]
and [:HID]
format codes. The [SS:]
code temporarily undoes the effect of TMG's [HID:]
code.
For example, you might key the following text into the memo field of an Anecdote tag to include an HTML link that is ignored when you run TMG reports but included when you make a site:
Example 1
The transcript reveals fascinating details of 19th century life. [HID:][SS:]<a href="doc1099.pdf"> <img src="pdficon.gif"></a>[:SS][:HID]
When Second Site makes the site, it will include the text within [SS:]
and [:SS]
. In this case, the text is HTML that will produce a clickable icon to download a PDF document. TMG will ignore all the text between [HID:]
and [:HID]
because it is within the HID codes.
Note that [SS:]
and [:SS]
may be used anywhere within [HID:]
and [:HID]
:
Example 2
[HID:]Hidden text [SS:]Text visible in SS only[:SS] More hidden text[:HID]
SS-HID
Second Site supports [SS-HID:]text[:SS-HID]
, a special formatting code that makes it possible to restrict selected text to TMG only. When used in conjunction with TMG's [HID:]
and [:HID]
format codes, the code can be used to force Second Site to ignore text that is processed by TMG.
For example, you might key the following text into a memo field to include formatting codes in TMG that are ignored when you make a site:
Example
[HID:][SS-HID:][:HID][:CR:][:CR:][HID:][:SS-HID][:HID] [LIND:]My mother and sister were in town at the hardware store when the telegram arrived. We told them ... [:LIND]
[SS-HID:]
and [:SS-HID]
must be placed inside [HID:]
and [:HID]
because they are not valid TMG printer codes. Second Site processes the text and detects the SS-HID codes. Any text between [SS-HID:]
and [:SS-HID]
will not be processed, and so the [:CR:]
codes do not affect the Second Site output.
PageLink
You may use the [PageLink:]id;name[:PageLink]
code in memos to create an HTML link to the person indicated by the id, which must be a TMG ID#. The optional name parameter is used to specify the link text, the text that the user will click to follow the link. If you do not include the name parameter, Second Site will use the primary name of the person as the link text.
In most cases, you should wrap the PageLink codes inside HID codes as shown below. This will hide the PageLink code from TMG.
Examples
[HID:][SS:]See [PageLink:]17[:PageLink][:SS][:HID] [HID:][SS:]See [PageLink:]17;J. Doe[:PageLink][:SS][:HID]
PageHRef
You may use the [PageHRef:]id[:PageHRef]
code in memos to create an HTML HRef parameter to the person indicated by the id, which must be a TMG ID#.
In most cases, you should wrap the PageHRef codes inside HID codes as shown below. This will hide the PageHRef code from TMG.
Example 1
[HID:][SS:]See <a href="[PageHRef:]17[:PageHRef]">J. Doe</a> [:SS][:HID]
PageHRef is similar to the PageLink code, but PageHRef creates the HRef parameter value whereas PageLink creates the entire HTML A element (link).
Current Person Shortcut
You can use a shortcut version of the PageHRef code when you are referring to the current person. This is useful when linking between sites that are both created with Second Site.
Example 2
[HID:][SS:]See entry on <a href="../othersite/[:PageHRef:]"> other site</a>[:SS][:HID]
Lifespan Codes
Second Site supports multiple sentence variables that you can use to add a person's lifespan to the output. Use these codes in TMG events that are only included in Second Site output, in FamilySectionNote events, or in the Family Sections.Heading Sentence property.
The codes are:
Code | Description |
---|---|
[LSP] |
Lifespan of current principal ([P]) |
[LSPO] |
Lifespan of other principal ([PO]) |
[LSP1] |
Lifespan of principal one ([P1]) |
[LSP2] |
Lifespan of principal two ([P2]) |
SS-L-Links
When Mapping Service Links are enabled, Second Site adds links to mapping services as part of the output of the TMG [L]
variable. If you have events with places where the event sentence does not use the [L]
variable, but you want place links included in the output, add the Second Site-only [SS-L-LINKS]
variable to the event's sentence.
[SS-L-LINKS]
has no meaning in TMG, so you should wrap it in HID codes when you add it to a sentence.
Example
<[HID:][SS-L-LINKS][:HID]>
No-Place-Map-Link
You may prevent Second Site from adding a mapping service link to a specific place by adding the code [:NO-PLACE-MAP-LINK:]
to any place part, or to the place comment.
This code has no meaning in TMG, so you should wrap it in HID codes when you add it to a place field.
Example
[HID:][:NO-PLACE-MAP-LINK:][:HID]
Place-Map-Link
You may instruct Second Site to allow mapping service links for a specific place by adding the code [:PLACE-MAP-LINK:]
to any place part, or to the place comment.
This code is useful when, for example, Only Places with LatLong is enabled, but you want specific places without LatLong coordinates to have mapping service links. Also, Second Site has filters to prevent the addition of mapping service links for places where geocoding is likely to fail. Second Site will ignore those filters when [:PLACE-MAP-LINK:]
is present.
This code has no meaning in TMG, so you should wrap it in HID codes when you add it to a place field.
Example
[HID:][:PLACE-MAP-LINK:][:HID]
Geo-Place
You may add [GEO-PLACE:]text[:GEO-PLACE]
in any place part, or in the place comment, to specify the text to be geocoded by the mapping service for a particular place.
Use this code when the actual text for a place will not produce acceptable geocoding results, but you have determined text that will be geocoded successfully. One example where this might be necessary is for historic addresses where some or all of the place fields have been renamed.
This code has no meaning in TMG, so you should wrap it in HID codes when you add it to a place field.
Example
Here is the text you might specify to link to a map that shows where Constantinople was, roughly equivalent to the modern city of Istanbul:
[HID:][GEO-PLACE:]Istanbul, , Turkey[:GEO-PLACE][:HID]
Note that the doubled commas in the example are important. To specify a city name and a country only, you must enter a comma to indicate that you are skipping the state field.
By the way, this is not a great example. Google Maps, for example, will geocode Constantinople as well as Istanbul, but the same is not true for lesser-known places.
Usage Notes
When passing place parts to a mapping service, Second Site must know which parts you have provided. It assigns the place level to the text you provide based on the number of commas in the text. As shown in the example above, you may specify extra commas to indicate missing parts.
Number of Parts |
Fields |
---|---|
1 | Country |
2 | State, Country |
3 | City, State, Country |
4 | City, County, State, Country |
5 | Detail, City, County, State, Country |
6 | Addressee, Detail, City, County, State, Country |
For the best results, you should always test the Geo-Place text by doing a search using the mapping service you have chosen. Go to the main page of the mapping service and enter the text in the search box it provides. Experiment, if necessary, until you get the results you want.
Note, however, that you should always include a country, and a state, if possible, in the Geo-Place text that you specify for Second Site. If you have determined that the mapping service does not need those details, or perhaps works better when they are not included, you should specify the proper values anyway, but single-exclude them to prevent them from being passed to the mapping service. Second Site makes decisions based on the country and state values, and so even though one or both of those values won't be passed to the mapping service, it will have an effect on the outcome.
Counties
When referring to a county, the table indicates you must provide four place parts because Second Site interprets three place parts as "city, state, country". However, the city and county fields do not get special treatment from Second Site, and they are both simply passed to the mapping service. For that reason, you can specify either "city, state, country" or "county, state, country" as the Geo-Place text.
When county names match city or town names in the same state, the mapping service will typically favor the smaller jurisdiction. For that reason, you may want to include the word "county" (or parish, etc.) as a hint to the mapping service's geocoding software.
For example, if you search for "Mobile,Alabama,USA" using Google Maps, it will produce a map with the outline of the city. If you search for "Mobile County,Alabama,USA", it will produce a map with the outline of the county.
Exhibit Codes
Second Site supports codes you can place in the Description field of the TMG Exhibit record to alter exhibit processing. The codes are described below. Some of the codes override the behavior specified in the Exhibit Section for the given type of exhibit.
To hide the Second Site-only codes from TMG, place them inside TMG's [HID:]
and [:HID]
codes. If you omit the HID codes, TMG will include the Second Site codes anywhere it displays the Exhibit Description. Second Site will detect its codes, and hide them, even if you neglect to provide the [HID:]
and [:HID]
codes.
Ignore, Link, or Embed
Code | Description and Example |
---|---|
[:SS-IGNORE:] |
When an image exhibit's description includes [:SS-IGNORE:] , Second Site will ignore the image even if the associated Exhibit Section option is set to Embed or Link. Use this option to ignore selected images when the default behavior is to embed or link.
Example: |
[:SS-LINK:] |
When an image exhibit's description includes [:SS-LINK:] , Second Site will link the image even if the associated Exhibit Section option is set to Embed. Use this code to link selected images when the default behavior is to embed.
Example: |
[:SS-EMBED:] |
When an image exhibit's description includes [:SS-EMBED:] , Second Site will embed the image even if the associated Exhibit Section option is set to Link. Use this code to embed selected images when the default behavior is to link.
Example: |
[:SS-EMBED-LEFT:] |
[:SS-EMBED-LEFT:] is a variation of [:SS-EMBED:] where the image will float left even if the default for embedded exhibits is set to float right or centered.
Example: |
[:SS-EMBED-CENTER:] |
[:SS-EMBED-CENTER:] is a variation of [:SS-EMBED:] where the image will be centered even if the default for embedded exhibits is set to float left or float right.
Example: |
[:SS-EMBED-RIGHT:] |
[:SS-EMBED-RIGHT:] is a variation of [:SS-EMBED:] where the image will float right even if the default for embedded exhibits is set to float left or centered.
Example: |
Please note that if the associated Exhibit Section option is set to Ignore, using the codes listed above will have no effect; you can use those codes to override Embed or Link, but you can not use them to override Ignore.
SS-Link-Text
The SS-LINK-TEXT code customizes the text used when Second Site creates a link to an exhibit. The default when no SS-LINK-TEXT code is supplied is an icon with the tooltip set to the exhibit's caption. If you supply the SS-LINK-TEXT code in the Description field of the Exhibit record, you can supply text and/or HTML to control the link.
You may supply one, two, or three parameters as part of the text enclosed by the SS-LINK-TEXT codes. The parameters are separated by semicolons. You do not have to supply any HTML if you use the one-parameter or three-parameter versions. You do have to provide HTML if you use the two-parameter version, but you have the most control over the link when using that method.
One Parameter
If you specify one parameter, the text is used as the text for the link to the exhibit:
[SS-LINK-TEXT:]link text[:SS-LINK-TEXT]
Example
- Input:
[SS-Link-Text:]Wedding Party[:SS-Link-Text]
- HTML:
<a href="href">Wedding Party</a>
- Result: Wedding Party
Two Parameters
If you specify two parameters, Second Site makes the link by inserting the HREF of the exhibit between the first parameter and the second parameter:
[SS-LINK-TEXT:]prefix HTML;suffix HTML[:SS-LINK-TEXT]
Your text should produce a valid HTML A element or the link will not work.
Example
- Input:
[SS-Link-Text:]See: <a href=";">Wedding Party</a> picture[:SS-Link-Text]
- HTML:
See: <a href="href">Wedding Party</a> picture
- Result: See: Wedding Party picture
Three Parameters
If you specify three parameters, Second Site uses the first and third values as a prefix and suffix, respectively, and inserts a link between them, using the second parameter as the link text:
[SS-LINK-TEXT:]prefix text;link text;suffix text[:SS-LINK-TEXT]
Example 1
- Input:
[SS-Link-Text:]See: ;Wedding Party; picture[:SS-Link-Text]
- HTML:
See: <a href="href">Wedding Party</a> picture
- Result: See: Wedding Party picture
Example 2
- Input:
[SS-Link-Text:](;Wedding Party;)[:SS-Link-Text]
- HTML:
(<a href="href">Wedding Party</a>)
- Result: (Wedding Party)
This page last changed on 07 Feb 2016.