Source Element Display in Source Definition Window

[Brian Gross 0]

Standard source elements display both with or without carrots in the source definition window.

 

For example:

Compiler [This is in the "Compiler" element group.]

< Date > [This is in the "Date" element group.]

 

Source elements I've created do the same thing.

 

For example:

County [This is in the "Record Type" element group.]

< Enumeration District [This is in the "Series" element group.]

(Note: I assume that tmg was trying to write "< Enumeration District >" but ran out of space.)

 

What do the carrots mean?

 

Thanks in advance for your help!

 

Brian Gross

[Paul Lawrence 0]

Standard source elements display both with or without carrots in the source definition window.

 

For example:

Compiler [This is in the "Compiler" element group.]

< Date > [This is in the "Date" element group.]

 

Source elements I've created do the same thing.

 

For example:

County [This is in the "Record Type" element group.]

< Enumeration District [This is in the "Series" element group.]

(Note: I assume that tmg was trying to write "< Enumeration District >" but ran out of space.)

 

What do the carrots mean?

 

Thanks in advance for your help!

 

Brian Gross

 

The < > are conditional brackets...if no data is entered in the element then the element will not print in the output. If there is no conditional brackets and the element if blank "Unknown" will print in the output.

[Michael Hannah 0]

If there are not conditional brackets you will get "unknown" followed by the name of the source element, e.g. "unknown enumeration district". The fact that the element name prints in this case is one motivation to create custom element names.

[Brian Gross 0]

I get it now, with some embarrassment!

 

I had not made the connection between the < > in the Source Definition window and the fact that those variables were conditionally printing, yes using < > that *I* added in full footnotes etc!

 

I did a little experimenting and, sure enough, the carrots disappeared in the Source Definition window when I eliminated the conditional printing.

 

Pretty good illustration of not seeing the forest for the trees.

 

Thanks for your help,

 

Brian