HISPID 3 - The Full Document

Croft, J.R. (ed.) (1989). HISPID - Herbarium Information Standards and Protocols for Interchange of Data (Australian National Botanic Gardens: Canberra).

Whalen, A. (ed.) (1993). HISPID - Herbarium Information Standards and Protocols for Interchange of Data (National Herbarium of New South Wales: Sydney).

INTRODUCTION

The 'Herbarium Information Standards and Protocols for Interchange of Data' (HISPID) is a standard format for the interchange of electronic herbarium specimen information. HISPID has been developed by a committee of representatives from all major Australian herbaria. This interchange standard was first published in 1989, with a revised version published in 1993.

HISPID3 is an accession-based interchange standard. Although many fields refer to attributes of the taxon they should be construed as applying to the specimen represented by the record, not to the taxon per se. The interchange of taxonomic, nomenclatural, bibliographic, typification, rare and endangered plant conservation, and other related information is not dealt with in this standard, unless it specifically refers to a particular accession (record).

This data dictionary is concerned primarily with data interchange standards but has considerable relevance to database structure since the task of preparing interchange files is simplified if the data fields of the despatching and receiving databases match, as far as possible, the interchange standard. If differences do exist then, generally, it is easier to combine data fields than it is to dissect them in a reliable manner. Fields that are concatenated are frequently heterogeneous in their nature and many preclude the possibility of rearranging the data contained within such fields.

The fields discussed in this data dictionary cover most of the herbarium and botanic gardens sphere of activity and have been arranged in groups of similar types of information. In many cases these groups may coincide with separate welldefined tables (or databases) of structurally similar records.

The challenge for herbarium data managers is to decide whether the data are to be efficiently exchanged as discrete but related tables (databases) or as a larger single flat file that may have to be appropriately dismembered by the receiving institution. Some database packages are able to stack multiple values in a single field. This useful data structure complicates the interchange format and will not be used at this stage.

Format of HISPID3

The 'Herbarium Information Systems Committee' (HISCOM) considered several format options for HISPID3. It was agreed that the interchange format of HISPID3 would be a flatfile. This flatfile format was chosen because it was relatively simple and required minimal computer programming to enable the importing and exporting of data. Furthermore, this format was in agreement with that chosen for the 'International Transfer Format for Botanic Garden Plant Records (Version 2.00)(ITF2). Although, it was recognised that it was difficult to transfer relational (hierarchical) data in flatfile formats, it was decided to proceed with the publication of this version of HISPID so that electronic data interchange could be actively encouraged. It is hoped that future versions of HISPID will include the capability of transferring data such that the relational structure is maintained.

There have been several major changes incorporated into this version of the HISPID transfer format, namely:

(1) HISPID3 allows for the interchange of variable length fields. It is no longer restricted to a fixed length format.

(3) HISPID3 provides a protocol for interchanging (non-standard) data that are either not defined within this document or are in a form different to that define here.

(4) Apart from a few exceptions, HISPID3 does not evaluate the relevance of interchanging any of the specific fields described in this document

(5) The references to how data are stored in the major Australian herbarium databases has been deleted from this document

(6) HISPID3 has been developed in conjunction with ITF2 (International Transfer Format for Botanic Gardens Plant Records version 2.00) so that the two interchange standards are as compatible as possible.

The transfer format of HISPID3 is based on 'Information technology - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1) '. International Standard ISO/IEC 8824, 2nd ed. (1990)(ISO/IEC: Genève).

Definitions

As far as practicable, raw data should be used. Interpretations or corrections in free text fields should be enclosed in square brackets: '[' and ']'. Omitted data should be represented by the ellipsis: '...'.

Italics:

Since the printable ASCII (EBDIC or UNICODE) character set does not include italicised characters, these are not included in the interchange file.

Nulls:

If information is not known for a field, then the field need not be included in the interchange file or else the field identifier may be interchanged unfilled. However, if the value of the Collector's Identifier field is unknown, then the default value should be 's.n.'.

Single character fields:

In general, single character (flag) fields have not been included in this standard because of the difficulty of detecting data entry errors.

Codes:

As for the 'single character' fields (above), codes are mostly not included in this standard because of the difficulty of detecting data entry errors.

Relevant Standards

The fields included in this interchange standard are a compilation from the following sources:

Summary of the important features of a HISPID3 file:

a) Each field is prefaced by an unique identifier this refers to the fields which describe the contents of the file, as well as to those which describe the information contained in each record);

b) Each unique identifier must begin with a lowercase letter (a-z) and cannot contain any spaces;

g) Fields can be omitted from the transfer file if there is no information available for that field;

j) Each field and each file information is one line long and is terminated by a comma (,);

Example of the start and end of a HISPID3 file:

An example of a filled HISPID3 interchange file

FORMAT OF THE TEXT IN THIS DESCRIPTION OF A HISPID3 FILE

The herbarium data fields for information interchange are listed below in the following format:

The full field name:

The name of the discrete piece of information within the file or within each record.

The transfer identifier code:

TDWG Short name:

The field description:

Relevant standards:

The existence of this type of data in any other published or proposed biological standards.

Domain/Range/Values:

The type of data allowed in this field, the range of values, or individual allowable values, and capitalisation.

Comments:

Any other remarks on the use or application of these data and its relationships to other data. Any conflicts or problems in the application of these data types.

Rules:

Additional information to that provided in Comments explaining the rules applying to these data.

Notes:

FILE IDENTIFICATION FIELDS

FILE IDENTIFIER GROUP:

This group of fields provides information about the file. These fields are required so that the receiving institution knows what to do with the incoming data.

Start of HISPID3 File

Transfer code: startfile

Description: The beginning of the transfer file has the file identifier 'startfile' only.

Domain/Range/Values: This field has the value 'startfile' only (all in lowercase).

End of HISPID3 File

Transfer code: endfile

Description: The end of the transfer file has the file identifier 'endfile' only.

Domain/Range/Values: This field has the value 'endfile' only (all in lowercase).

Comments: To be found at the very end of a HISPID3 file indicating the end of file. The description of this file identifier has been included here so that it can be considered together with the 'startfile' identifier.

Version of File

Transfer code: version

Domain/Range/Values: Alphanumeric; the version number prefaced by the acronym 'HISPID' (all in uppercase).

Comments: Although it is expected that the latest version of HISPID will normally be used for the transfer format, the format of earlier versions are allowable. The 'HISPID Version August 1993' should be referred to as HISPID2 and the original version of HISPID (1989) as HISPID1. This current version should be referred to as HISPID3.

Number of Records in File

Transfer code: numrecords

Date of File

Transfer code: datefile

Domain/Range/Values: Integer; year (4 digits) followed by month (2 digits) and then day (2 digits), without spaces between each. That is, YYYYMMDD. For example, the 6th July 1987 would be transferred in the form 19870706 (refer Collection Date for further details).

Name of Institution Supplying Information

Transfer code: institute

Description: The name in full of the institution sending the current HISPID file.

Contact Name

Transfer code: contact

Address of Institution Sending File

Transfer code: address

Comments: The address should be displayed as continuous text, no line breaks, only commas and spaces as required.

Telephone Number of Institution

Transfer code: phone

Comments: The use of national and international codes depends on the circumstances of the sending and receiving institutions.

Facsimile Number of Institution

Transfer code: fax

Comments: The use of national and international codes depends on the circumstances of the sending and receiving institutions.

Email Address of Institution

Transfer code: email

Non-Standard Option

Transfer code: nonstandard

Description: This field allows for the inclusion of data or standards that have not been included in this publication. The data is likely to be of particular interest to the sending and receiving institutions, who wish to use a HISPID type format for data fields which have not been described in this standard.

Domain/Range/Values: Alphanumeric; the field identifier 'nonstandard' is followed by a suggested unique field identifier (all lowercase (a-z) or at least first letter lowercase) to be used in the transfer file; which is followed by a brief explanation (if necessary); the syntax of the data (whether alphanumeric or numeric); and the reference to the standard used in this new field (if necessary)(all enclosed by round brackets and, within, each separated by a semicolon and space)(refer example below).

If the data for any one standard are being transferred in several fields, then each unique field identifier is separated by a space followed by the necessary explanatory information in round brackets.

If more than one non-standard HISPID field (based on different standards) is being used in the transfer file then each must be separated by a semicolon and space (; )(refer example, below).

Since this field is alphanumeric (text), the data must be enclosed by double quotations ("); all data must be on one line; and the field must end with a comma (,).

Note: Since conformity with the HISPID standard is an agreed (essential) requirement for institutions interchanging data according to HISPID3 format, institutions are strongly urged to modify their interchange data so that they conform with one or more of the current HISPID3 fields. However, when circumstances preclude this, the Non-Standard Option may be used to interchange such data. If an institution wishes to interchange non-standard data, then they are requested to notify the HISPID coordinator (editor) so that these additional fields can be considered for inclusion in future versions of HISPID.

In the following example, the 'nonstandard' information is presented on more than one line for readability.

nonstandard "pol (Pollinator; alphanumeric - scientific name of pollinator and authority at lowest level name or epithet); arch (Plant architectural models; alphanumeric; F. Hallé et al. 1978. 'Tropical trees and forests', Springer-Verlag: Berlin)",

If an institution is unable to provide information in the format of any particular HISPID3 field, as here defined, because they combine two or more of these fields together in such a way that the data are unable to be separated, then the Non-Standard option can be used.

For example, if an institution combines the Substrate and Soil Type fields together, and the Vegetation and Associated Species Fields together, in such a way that they are unable to separate these elements into separate fields, then a new 'Transfer code' for each pair of information can be formed, with the 'Transfer codes' of the segregate fields cited in round brackets, and each of these Transfer codes separated by a comma. It is then understood that the Domain/Range/Values and other Comments of each still applies.

subsoil is the nonstandard identifier for the combined Substrate and Soil Type fields;

vegass is the nonstandard identifier for the combined Vegetation and Associated Species fields.

Comments: The non-standard fields would have to be programmed into the receiving database, as well as into the HISPID insert program.

File Action Flag

Transfer code: fileaction

Description: A field to indicate how the records of the file should be processed.

Domain/Range/Values: Alphabetic; this field must consist of one of the values in the table below:

Comments: This field should be used in conjunction with the Description of File Contents and Other Comments field (refer below). The 'delete' option is used when previously received collections are know to be sufficiently inaccurate that it is recommended that the specimen be removed from the herbarium. The reason for this would be explained in the Description of File Contents and Other Comments field (refer below).

The 'insert' option is used for new records being sent to the receiving database. This is the default value for all exchange data.

The 'update' option is used for records already held in the receiving database which have been modified and included in the current transfer file. This option would be used for returning redeterminations and other corrections to the receiving institutions.

File Descriptor Flag

Transfer code: filedescriptor

Description: A field to indicate the nature of the records contained in the file.

Domain/Range/Values: Alphabetic; this field must consist of one of the values in the table below:

Comments: These key values may be used to automatically implement the procedures to be followed by the receiving institution. This field should be used in conjunction with the Description of File Contents and Other Comments field (refer below).

Description of File Contents and Other Comments

Transfer code: content

Example 1: Description of records being transferred as part of an herbarium loan:

Example 2: Description of transfer file containing corrections to the plant name (Record Identification Group of fields):

Comments: This field may be used in conjunction with the File Descriptor Flag (above).

Data Set URL

Transfer code: daturl

Description: The internet URL (Universal Resource Locator) where the records in this file can be found.

Relevant standards: Internet URL, RFC 1738 (refer URL http://www.w3.org/pub/WWW/Addressing/rfc1738.txt or URL http://www.w3.org/pub/WWW/Addressing/URL/Overview.html)

Comments: This information can refer to either a fixed export file, to an on-line query, or can link to a specimen database gateway.

ACCESSION INFORMATION Fields

ACCESSION IDENTIFIER GROUP:

This group of fields identifies the data records of the transfer file, that is, it describes the accession-based (specimen-based) information being interchanged. It is essential that these fields match exactly for the various exchange options to work effectively.

The fields in this group include the Institution Code and Accession Identifier, as well as the Record defining field identifiers.

Start of HISPID3 Record

Transfer code: {

Comments: To be found at the end of each HISPID3 record indicating the end of the data of a record, prior to beginning the next record or the endfile identifier if it is the last record in the transfer file.

Institution Code

Transfer code: insid

Description: The standard code for the Institution to which the plant record refers.

Relevant standards: Index Herbariorum, International Directory for Botanic Gardens, ABIS, ITF, TLR

Domain/Range/Values: The code must consist of an entry of 17 uppercase letters (AZ), no embedded spaces. This field must be filled.

Comments: When inserting the accession information into a receiving database, the Institution Code combines with the Accession Identifier to make up the unique Donor's accession identifier for each record.

It is perhaps not necessary to include this field in a 'home' database since it may be appended to the record as the interchange file is generated. However, it will be necessary if the herbarium chooses to keep records of other institutions' collections of particular groups (for research purposes for example).

A problem with this field may arise with herbaria associated with botanic gardens; it is desirable that the herbaria and botanic gardens have the same abbreviation. If the record is primarily referring to an herbarium voucher, then the herbarium code should always be used in the transfer file. The distinction between herbarium and living material can be handled by various flags in the Collection group.

If an institution's herbarium does not have an official code, then a temporary one should be assigned. However, it is essential that the institution receiving the transfer file is aware of the code being used. This information should be included in the Description of File Contents and other Comments field (refer above).

Accession Identifier

Transfer code: accid

Description: The unique identifier of the record, often called 'Accession Number', used internally by the institution to record each accession.

Domain/Range/Values: Alphanumeric; the Accession Identifier field may consist of any characters in the ASCII character set, no embedded spaces.

1. The Accession Identifier should be a unique set of characters that identifies each accession in the institution's own record system.

2. The same value of the Accession Identifier should not be used again for a separate, unrelated specimen in that institution.

Comments: Institutions differ widely in the way they accession and record herbarium specimens with one result that numbering systems (sometimes multiple) have been applied in fundamentally different ways. In some institutions this number refers to a unique specimen accession number, in others the specimen parts are accessioned individually and each part (eg. multiple sheets) has its own accession number, but supplementary material such as spirit and fruit may carry the number of the first sheet. The application of different specimen/accession number systems is a source of potential confusion where the specimen number and accession number may or may not be the same thing. However, only the Accession Identifier is used in HISPID3. This single number will either identify the single herbarium material or the group of material (when several identifiers are used for different elements of an accession).

Unlike herbaria, many botanic gardens include punctuation within their Accession Identifier, eg. 82BG2431. It is vital for an institution to be consistent on whether the punctuation is included in the HISPID3 transfer format.

BASIS OF RECORD GROUP

This group consists of a single field which indicates the basis of the record being interchanged.

Source of Record Flag

Transfer code: recsou

Description: A code indication of the type of item to which the record refers.

Values in Field	Meaning
Collection	Plant specimen
Electronic	Electronic record only, specimen no longer available
Literature	Reference
Observation	Observation, including photograph of plant, but not of specimen
Photograph	Photograph of specimen

Comments: The default should be 'Collection' for a specimenbased record. In the absence of any other value, a specimenbased record is assumed.

The values 'Observation' and 'Literature' may be used when the presence of a taxon is solely based on an observation or a published reference to an herbarium specimen held in another institution (respectively). The value 'Electronic' is used when the presence of a taxon is solely based on an electronic record of an herbarium specimen which is no longer available.

RECORD IDENTIFICATION GROUP

This group of fields completely describes the botanical name of the record. These fields also enable the identification of cultivars and hybrids and intermediates using either binomials or hybrid formulae, as well as qualified identifications.

These fields enable the interchange of either the 'full' scientific (Latin) name of a plant or the 'limited' scientific name.

'Full' Scientific Name

'Limited' Scientific

2. If a 'full' taxonomic name is not required, then an abbreviated ('limited') scientific name can be used to precisely refer to the taxon. This option is also available in HISPID3. Such a 'limited' scientific name is transferred according to the following rules:

only the genus name and the specific epithet are required. The authority is not required unless there is some possibility of confusion between this species and a homonym.

only the genus name, specific epithet and the lowest level infraspecific epithet are required. The authority is not required unless there is some possibility of confusion between this infraspecific taxon and a homonym.

The module for the Plant Name is based on Bisby, F.A. (1994) 'Plant names in botanical databases', Plant Taxonomic Database Standard No. 3 Version 1.00 (TDWG / Hunt: Pittsburgh).

Hybrids, Intergrades

Hybrids and Intergrades present considerable problems for handling of their names in electronic storage and transfer. The system presented here differs from ITF2, in that it does not indicate the taxonomic rank at which the hybrization or intergradation occurs. For example, in HISPID3, if the Hybrid Flag field is filled, then the name of the 'first' parent is transferred in the 'default' HISPID3 name fields (eg. Genus Name, Species Epithet, Infraspecific Epithet) and the 'second' parent is transferred in the 'hybrid' name fields (eg. Genus Name Parent 2 Hybrid, Species Epithet Parent 2 Hybrid, Infraspecific Epithet Parent 2 Hybrid). Unlike ITF2, this system readily allows for the interchange of hybrids and intergrades resulting from parents at different rank (eg. a hybrid between one species and the variety of another species).

Vernacular Names

Although the application of vernacular (common) names is not as rigorously controlled as scientific names, and they vary greatly and are often not unique for individual species, institutions may wish to interchange this information. A suggested format for interchanging these data are included (refer Vernacular Names).

Higher Group Names

The names of higher groups such as suprafamilial groups and families are not required in the HISPID3 transfer file because each accepted genus name in the plant kingdom is unique. However, these data may be interchanged, using the fields Suprafamilial Group Name and Family Name.

Plant Name Authorities

It is not necessary to include the authorities of the species and infraspecific names in a HISPID3 transfer file. However, the inclusion of authorities with the botanical names prevents confusion between homonyms. If these authorities are required, then they can be included in the transfer file. To minimise variation in the citation of the names of authors, it is recommended that a published standard for the citation of authorities be used. One such standard is Brummitt, R.K. & Powell, C.E. (1992) 'Authors of plant names' (Royal Botanic Gardens: Kew)(endorsed by the International Working Group on Taxonomic Databases for Plant Sciences - TDWG).

Other Comments

Mixed collections are unacceptable and must be handled by duplicate records or, if the mixture is not significant, by a note in the Name Comments field.

Suprafamilial Group Name

Transfer code: supfam

Description: The relevant suprafamilial group name of the taxon referred to in the record.

Domain/Range/Values: Alpha; any valid suprafamilial group name, with first letter in uppercase.

Comments: This field allows for material being sent for identification, particularly when even the family may not be known.

The ABIS standard included in this field any suprageneric category including family (see next field) and any other arbitrary grouping.

All plant groupings above the rank of genus are assigned automatically, the name depending on the classification system employed. As each institution uses its own classification system, in many cases different from others, this field and the next two fields may not always be a useful part of the interchange standard. However, it is simple to ignore this information when loading the data (if it is not required or is unsuitable), but it may be useful when reviewing the taxonomic system under which the data has been compiled when loading the file into a database.

Family Name

Transfer code: fam

Description: The family name appropriate to the Genus name field, entered in full.

Domain/Range/Values: Alpha; any valid plant family name, with capitalisation of the first letter only. If the name of the plant family is unknown, then this field may contain the value UNKNOWN (in uppercase). In this case, the remaining name fields should not be filled.

Comments: There is no universally accepted classification of plant genera into families, and several systems are in use in herbaria. Individual herbaria may choose to store two (or more) family fields to reflect different classification systems.

If institutions store family names or standard nomenclature in an abbreviated or encoded form, these must be expanded for transfer.

The ABIS standard includes this field in a suprageneric category (see previous field).

Suprageneric Group Rank

Transfer code: supgenrk

Description: A field to indicate the rank of the suprageneric group name of the plant.

Domain/Range/Values: Alpha; any valid suprageneric group rank, below the rank of family and above the rank of genus, capitalisation of the first letter only.

Comments: See comments on conventions and necessity of this type of information under Family Name and Suprafamilial Group Name fields.

This field must contain the full name of the rank of the suprageneric group, eg. 'subfamily'.

Suprageneric Group Name

Transfer code: supgen

Domain/Range/Values: Alpha; any valid suprageneric group name, below the rank of family, capitalisation of the first letter only.

Comments: See comments on conventions and necessity of this type of information under Family Name and Suprafamilial Group Name fields.

If the name of the genus of the plant is unknown, then this field does provide a higher level of identification than does the Family Name field alone.

HYBRIDS, GRAFTS, CHIMAERA AND INTERGRADES

The interchange of hybrid formulae and intergrade names is particularly difficult in a flatfile format because the relational nature of these data cannot be readily maintained. Unlike ITF2 which has Hybrid Flag fields for intergeneric, interspecific and infraspecific hybrids and intergrades, HISPID3 has only one (namely, Hybrid Flag field, refer below). In HISPID3, the Hybrid Flag indicates the type of hybrid, grafts, chimaera or intergrade involved, but does not describe the rank to which it applies. If the name is a Latin or non-Latin collective name, or if the name is a graft or chimaera, then only the standard 'default' HISPID3 name fields are required in the transfer file. For example, the name Lonicera x tellmaniana would be tranferred with the letter 'x' in the Hybrid Flag field, 'Lonicera' in the Genus Name field, and 'tellmaniana' in the Species Epithet field.

The concept of 'parent 1' and 'parent 2' has been implemented in HISPID3 to handle the transfer of names in the form of hybrid formulae and intergrades.

Example 1: the intergeneric hybrid Rhododendron x Vaccinium would transferred with the letter 'H' in the Hybrid Flag field, 'Rhododendron' in the Genus Name field ('parent 1' - transfer code: gen) and 'Vaccinium' in the Second Hybrid Genus Name field ('parent 2' - transfer code: genhy2). That is:

Example 2: the hybrid Prostanthera cuneata x Prostanthera lasianthos var. subcoriacea would be transferred with the letter 'H' in the Hybrid Flag field, 'Prostanthera' in the Genus Name field, 'cuneata' in the Species Epithet field ('parent 1' - transfer code sp), 'lasianthos' in the Second Hybrid Species Epithet field ('parent 2' - transfer code sphy2), 'var.' in the Second Hybrid Infraspecific Rank Flag ('parent 2' - transfer code isprkhy2), and 'subcoriacea' in the Second Hybrid Infraspecific Epithet field ('parent 2' - transfer code: isphy2). In this example, hybrid formulae which describe the results of hybridisation at different ranks can be effectively interchanged. That is:

hyb	"H",
gen	"Prostanthera",
sp	"cuneata",
sphy2	"lasianthos",
isprkhy2	"var",
isphy2	"subcoriacea",

Example 3: the hybrid Magnolia campbellii subsp. mollicomata x Magnolia sprengeri var. diva would be transferred as:

hyb	"H",
gen	"Magnolia",
sp	"campbellii",
isprk	"subsp.",
isp	"mollicomata",
sphy2	"sprengeri",
isprkhy2	"var.",
isphy2	"diva",

Hybrid Flag

Transfer code: hyb

Description: A field to indicate whether the plant name refers to a hybrid, graft chimaera or intergrade, without reference to rank.

Domain/Range/Values: If the accession is a hybrid, graft chimaera or intergrade, then the Hybrid field must consist of one of the characters in the table below:

Values in Field	Nature of name in Genus Name* field*
x	A Latin collective name for a hybrid
G	A non-Latin collective name for a hybrid
H	A hybrid formula for a hybrid
+	A graft hybrid or graft chimaera
	An intergrade of non-hybrid nature

1. The rules associated with these values are outlined under Genus Name field.

2. For interchange and data storage purposes, the value in this field for a hybrid is a lowercase 'x' not a multiplication sign (as specified in the International Code of Botanical Nomenclature), since the multiplication sign does not occur in the ASCII character set.

3. If an 'x' is placed in this field, then the plant name must be validly published under the ICBN.

Notes: ITF includes the letter 'U' in the 'Infraspecific Hybrid Flag' (refer ITF2) to indicate a Cultivar group name. However, HISPID3 only uses the Cultivar Group Name field (refer below) to transfer these data.

Genus Name

Transfer code: gen

Description: The name of the genus of a plant or ,if part of a hybrid formula or intergrade, then the name of the first 'parent' of that formula or intergrade, entered in full.

Domain/Range/Values: Alpha; any valid genus name, capitalisation of the first letter only.

Comments: This field, combined with the following Species Epithet and Infraspecies Epithet fields, constitute the minimum taxonomic information for the identity of the specimen.

This field may contain an embedded hyphen, in which case the second word is in lowercase

If the Hybrid Flag field is not filled (not transferred), then this field must contain:

1.1.3 This field should not be filled. In this case, the remaining name fields should also not be filled.

1.1.4 This field must contain the first 'parent' of a hybrid formula for an intergeneric hybrid name, validly published under the ICBN, eg. 'Rhododendron' for the hybrid formula Rhododendron x Vaccinium

1.1.5 This field must contain an intergeneric hybrid name, validly published under the ICBN, eg. Halimiocistus for x Halimiocistus sahucii.

If the Hybrid Flag is + and the name is an intergeneric graft hybrid or graft chimaera, then:

1.1.6 This field must be the name of an intergeneric graft hybrid or graft chimaera, validly published under the Cultivated Code, eg. Crataegomespilus for + Crataegomespilus dardarii.

Second Hybrid Genus Name

Transfer code: genhy2

Description: The second name of a hybrid formula or intergrade between two plant genera, entered in full.

Domain/Range/Values: Alpha; any valid genus name, capitalisation of the first letter only.

Comments: Refer discussion under HYBRIDS, GRAFTS, CHIMAERA AND INTERGRADES and compare with Genus Name field, above.

Subgeneric Group Name

Transfer code: subgen

Description: The subgeneric group name of the plant, preceded by its rank, entered in full.

Domain/Range/Values: Alpha; any valid subgeneric group name, capitalisation of the first letter only.

2. The first letter must be in uppercase (AZ), the rest of the word in lowercase letters (az).

3. One or two hyphens are permitted in the word; no characters other than the letters outlined above are permitted.

This field must contain a validly published subgeneric group name under the ICBN.

This field must also contain one of the following abbreviations of the rank of the Subgeneric Group name:

Abbreviation	Full subgeneric group name
subgen.	Subgenus
sect.	Section
subsect.	Subsection
ser.	Series
subser.	Subseries

If the name of the genus of the plant is unknown, then this field must not be filled. In this case, the remaining name fields should also be unfilled.

If the species name of the plant is unknown, then (if filled) this field does provide a higher level of identification than does the Genus Name field alone.

Species Qualifier

Transfer code: spql

Description: This qualifier permits the Species Epithet field to be used for normal species names, as well as names of aggregate (refer Comments 1, below) or segregate species.

1. If the Species Epithet field is not filled, then this field must not be filled.

2. If the Hybrid Flag is filled and the value in that field refers to an interspecific hybrid, then this field must not be filled.

3. This field must consist of one of the values in the table below, which refers to the following situations in Species Epithet field:

agg.	An aggregate species
s. lat.	aggregate species (sensu lato)
s. str.	segregate species (sensu stricto)

1. If the entry is 'agg.', then the plant has been identified to an aggregate species, and not to any of the segregate microspecies within the aggregate.

2. If this field is filled, then Infraspecific Rank Flag and Infraspecific Epithet fields must not be filled.

3. The terms collective species or species groups are sometimes also used in plant names. They should be treated as for aggregate species.

4. Under the current standards, it is not possible to use the aggregate/segregate concept at levels other than the species level.

Species Epithet

Transfer code: sp

Description: The species epithet of the plant or ,if part of a hybrid formula or intergrade, then the name of the first 'parent' of that formula or intergrade, entered in full.

Domain/Range/Values: Alpha; any valid species name, all lowercase, no embedded spaces.

1. The specific epithet must be one word (except as in the cases of Rules 1.1, 1.2, 3 and 4, below).

2. It must consist of lowercase letters (az), and may contain one or two hyphens. No other characters are permitted (except in the cases of Rules 1.1 and 1.2).

3. The field may be left unfilled if the species epithet is unknown. It must be left unfilled if the Genus name is unknown (Genus Name field) or the Family Name field has the value UNKNOWN.

4. If the specific epithet of a plant is uncertain, then the following name fields should not be filled.

1. If the Hybrid Flag is not filled, then this field must contain a validly published, nonhybrid specific epithet under the ICBN, except in the following special cases:

1.1 If the plant has not been identified to specific level, the field must be left unfilled, as must the following name fields. (The abbreviation sp. should not be entered in these circumstances.)

1.2 If the plant represents a new species which has not been formally described, then sp. nov., sp. A, sp. 1 (or other acceptable codes) should be entered, if possible followed by a unique identifier, such as the collector's name and number or the locality. The following Species Author field must be left unfilled.

2. If the Hybrid Flag is x and it refers to an interspecific hybrid, then the entry in the field must be a Latin Collective name for an interspecific hybrid, eg. tellmaniana for Lonicera x tellmaniana.

hyb	"H",
gen	"Rhododendron",
sp	"dichroanthum",
sphy2	"griersonianum",

If only one parent is known, then enter the specific epithet of that parent alone (without the lower case letter 'x').

5. If the Species Qualifier field is agg., then the entry in the field must be a validly published specific epithet under the ICBN, used for the name of the group of species concerned. The word agg. should not be included in the entry of this field.

The abbreviation sp. is not interchanged in HISPID3 if a plant has not been identified to the species epithet level (Rule 1.1, above).

Second Hybrid Species Epithet

Transfer code: sphy2

Description: The second specific epithet of a hybrid formula or intergrade between two plant species, entered in full.

Domain/Range/Values: Alpha; any valid species name, all lowercase, no embedded spaces (refer Species Epithet field, above).

Comments: Refer discussion under HYBRIDS, GRAFTS, CHIMAERA AND INTERGRADES and Species Epithet field, above.

Notes: The authority of the species names are not given when the name is a hybrid formula or intergrade.

Species AuthorFieldsSpecies Author

Transfer code: spau

Description: The author citation of the species (as given in Genus Name and Species Epithet fields, above), in standard abbreviated form

Domain/Range/Values: Alpha; any valid author abbreviation, initials and first letter of surname in uppercase, and other characters as described below:

1. The full name of a species (as transferred in the Species Epithet field) must include this field.

2. This field is not filled for the full name of a species aggregate (as transferred in the Species Qualifier and Species Epithet fields).

3. Alphabetic letters (A-Z, a-z), fullstops (periods), pairs of brackets, apostrophes, hyphens, ampersands (&) and spaces are all valid entries for this field.

4. For the citation of joint authors, it is recommended that the ampersand (&) is used between the last two names, not 'et' or 'and'. If more than two authors, then a comma and space (, ) are used to separate all authors except for the last two.

5. Names in languages other than the English languages should be transliterated into the roman alphabet. However, if institutions are able to receive and send other alphabetic characters (eg. if using UNICODE), then these may be included in the transfer file.

6. Parenthetical author or authors in the recommended form enclosed in round brackets at the beginning of the field.

Comments: Since the author is unique to any accepted plant name, it is usually not essential for this information to be interchange.

Notes: The authority of the species name is not given when the name refers to a hybrid formula or an intergrade. Therefore, the information transferred in this field does not refer to the Second Hybrid Species Epithet field.

Infraspecific Rank Flag

Transfer code: isprk

Description: A field to indicate the lowest infraspecific rank for the name in the Infraspecific Epithet field. The contents of this field are confined to the rank of the infraspecific name of non-collective, and non-cultivar group infraspecific taxa. It also indicates the lowest infraspecific rank for the name of the first 'parent' of a hybrid formula or intergrade.

Domain/Range/Values: Alpha; if the Infraspecific Epithet field is filled and the plant is not a Collective hybrid and is not a cultivar, then this field must be one of the values in the table below:

Values in field	Rank of Name in Infraspecific Epithet field (Non-hybrid names)
subsp.	Subspecies
var.	Variety
subvar.	Subvariety
f.	Form
subf.	Subform

Comments: If the Infraspecific Epithet field is not filled, then this field must not be filled.

Notes: The contents of this field represent the lowest infraspecific rank for this name.

Under the rules of the ICBN, every trinomial below the level of species is unique. Hence, Rhododendron arboreum subsp. delavayi var. peramoemum can be known uniquely as Rhododendron arboreum var. peramoemum. Therefore the name can consist of the genus, the species and the lowest infraspecific taxon name, qualified by its rank.

Second Hybrid Infraspecific Rank Flag

Transfer code: isprkhy2

Description: A field to indicate the lowest infraspecific rank for the name in the Infraspecific Epithet field of the second 'parent' of a hybrid formula or intergrade. The contents of this field are confined to the rank of the infraspecific name of non-collective, and non-cultivar group infraspecific taxa.

Values in field	Rank of Name in Infraspecific Epithet field (Non-hybrid names)
subsp.	Subspecies
var.	Variety
subvar.	Subvariety
f.	Form
subf.	Subform

Comments: Refer Infraspecific Rank Flag field (above) for further details.

Notes: The transfer code (isprkhy2), as for other hybrid fields which are used to transfer information about the second 'parent' of the hybrid formula or intergrade conclude with 'hy2'. This should not be confused with isp2rk which is the transfer code for the Second Infraspecific Rank Flag and isp2rkhy2 which is used to transfer the rank of the Second Hybrid of the Second Lowest Infraspecific Epithet when the full taxonomic name is being transferred.

Infraspecific Epithet

Transfer code: isp

Description: The epithet of the lowest infraspecific rank of the name, entered in full.

Domain/Range/Values: Alpha; any valid infraspecific taxon epithet, all lower case.

2. It must only consist of lowercase letters (az), and may contain one or two hyphens. No other characters are allowed (except in the case of Rules 1.1, 2, 4 and 5, below).

3. The field may be left unfilled to indicate that the plant is not identified below the species level. It must not be filled if the species epithet is not known. Indeterminate entries like 'subsp.', 'var.' etc., are not permissible.

1. If the Infraspecific Rank Flag is subsp. var., subvar., f. or subf., then the entry must be an epithet in the rank denoted by that field, validly published under the ICBN, except in the following special case:

1.1 Where a new infraspecific taxon has not been formally described, subsp. nov., var. nov., subvar. nov., f. nov., or subf. nov. may be entered, if possible followed by a unique identifier, such as the collector's name and number or the locality

2. If the Hybrid Flag value is 'H', then the entry must represent the first 'parent' in a hybrid formula

If the Hybrid Flag value is 'H' but only one 'parent' of a hybrid formula is known, then enter the infraspecific epithet of that parent alone

3. If the Hybrid Flag is 'x', then the entry must be a Latin collective name for an infraspecific hybrid. The name must be valid under the Cultivated Code.

4. If the Hybrid Flag value is G, then the entry must be a non-Latin collective name. It must be valid under the Cultivated Code.

Second Hybrid Infraspecific Epithet

Transfer code: isphy2

Description: The epithet of the lowest infraspecific rank of the name of the second 'parent' in a hybrid formula or intergrade, entered in full.

Domain/Range/Values: Alpha; any valid infraspecific taxon epithet, all lower case.

Comments: Refer the Infraspecific Epithet field for further details (above).

Notes: The authority of the infraspecific names are not given when the name is a hybrid formula or intergrade.

Infraspecific Author

Transfer code: ispau

Description: The author citation of the lowest infraspecific epithet, in standard abbreviated form.

Notes: The authority of the infraspecific names are not given when the name is a hybrid formula or intergrade.

Second Infraspecific Rank Flag

Transfer code: isp2rk

Description: An additional field to indicate the rank of the second lowest infraspecific name (as given in the Second Infraspecific Epithet field), which is at a higher level to that of the Infraspecific Epithet field. This field is used when a 'full' taxonomic name is required (refer Comments and Notes, below). This field is also used when a 'full' taxonomic name is required for the first 'parent' of a hybrid formula or intergrade.

Domain/Range/Values: See under Infraspecific Rank Flag, above. Note: these additional fields are for non-hybrid infraspecific taxa, not for hybrids, Collective names or cultivars.

Comments: This field has been included for those institutions who wish to transfer and/or receive a complete ('full') taxonomic name (as defined in Notes, below) in a form which is more easily inserted into a database than the contents of the Full Name field (p. 47). When more than one infraspecific name is being transferred, the following fields refer to the lowest level infraspecific name: Infraspecific Rank Flag, Infraspecific Epithet, and Infraspecific Author; whereas the Second Infraspecific Rank Flag, Second Infraspecific Epithet, and Second Infraspecific Author all refer to the second lowest level of infraspecific name (eg. var. and subsp., respectively). If institutions wish to transfer more than two levels of infraspecific names in this format, then the third lowest level has the number 3 included in the Transfer Code identifier (eg. isp3rk, isp3, isp3au), and so on, as appropriate.

Notes: The 'full' scientific name includes the genus and species names, together with all infraspecific names and ranks (where relevant) and all appropriate authorities. Such 'full' names are extremely useful, especially if the complete taxonomic name of the taxon is required.

Second Hybrid of the Second Infraspecific Flag

Transfer code: isp2rkhy2

Description: An additional field to indicate the rank of the second lowest infraspecific name of the second 'parent' of a hybrid formula or intergrade (as given in the Second Hybrid of the Second Infraspecific Epithet field), which is at a higher level to that of the Second Hybrid Infraspecific Epithet field. This field is used when a 'full' taxonomic name is required.

Second Infraspecific Epithet

Transfer code: isp2

Description: An additional field for the epithet of the second lowest infraspecific rank of the name of the plant, when a full taxonomic name is required (refer Comments under Second Infraspecific Rank Flag field, above).

Domain/Range/Values: See under Infraspecific Epithet field, above. Note: these additional fields are for non-hybrid infraspecific taxa, not for hybrids, collective names or cultivars.

Comments: Refer Comments under Second Infraspecific Rank Flag field, above.

Second Hybrid of the Second Infraspecific Epithet

Transfer code: isp2hy2

Description: An additional field for the epithet of the second lowest infraspecific rank of the name of the second 'parent' of a hybrid formula or intergrade, when a full taxonomic name is required.

Comments: Refer Comments under Second Infraspecific Rank Flag field, above.

Second Infraspecific Author

Transfer code: isp2au

Description: An additional field for the author citation of the second lowest infraspecific epithet, in standard abbreviated form.

Comments: Refer under Infraspecific Author and Second Infraspecific Rank Flag fields, above. Note: these additional fields are for non-hybrid infraspecific taxa, not for hybrids, collective names or cultivars.

Notes: The authority of the infraspecific names are not given when the name is a hybrid formula or intergrade.

Vernacular Names

Transfer code: vernam

Description: A free text field to allow for the inclusion of vernacular (common) plant names.

Domain/Range/Values: Vernacular name followed by language of each name in round brackets ( ).

Comments: If more than one vernacular name, then each name (and language group) is separated by a comma and a space.

CULTIVATED PLANT NAMES

Rules for naming agricultural, forestry and horticultural plant have recently been revised in the International Code of Nomenclature for Cultivated Plants (Ed. P. Trehane, Quarterjack Publishing, 1995). Following the lead of ITF2, HISPID3 allows compatibility with this code by introducing two new fields, the Cultivar Group Name and the Trade Designation Name, in addition to the Cultivar Name field. These three fields allow for an accurate interchange of these plants, in accordance with the rules of the above code. The only names that may be used in this code are the Cultivar epithet, the Cultivar Group epithet, and the Trade Designation name (or other similar trade name).

Signs to indicate hybrids (x) or graft chimera (+) must NOT be used in any of the following three fields. Authors names are not required by the cultivated plant code, and should not be appended to the names given at any of the three ranks.

gen	"Dracaena",
sp	"oleracea",
culgnam	"Deremensis",
culnam	"Christianne",

Cultivar Group Name

Transfer code: culgnam

2. If the accession cannot be assigned to a cultivar group, then the field should not be filled.

1. The cultivar group name must be a valid cultivar group name under the International Code of Nomenclature for Cultivated Plants. This field should not contain a cultivar name or trade designation name.

2. The first letter of each word of the cultivar group name should be uppercase.

3. The word 'Group' should not be appended to the cultivar group name; this is redundant in this field for transfer, or for database storage ('Group' can easily be appended to the information contained in this field in output programs).

4. The cultivar group name should not be enclosed in parentheses (these can easily be added to the information contained in this field in output programs if required).(refer CULTIVATED PLANT NAMES example 2, below).

1. A cultivar group is an assemblage of similar, named cultivars within a genus or species (including hybrid genera and species), eg. Lolium perenne Early Group. Such groups are often associated with a cultivar name, and in this case the Group Name is normally enclosed by round brackets, eg. Lolium perenne (Early Group) cv. Devon Eaver. For further details, see Article 4 of the International Code of Nomenclature for Cultivated Plants.

2. Under the provisions of the International Code of Nomenclature for Cultivated Plants, cultivar group names are written in outputs as contained between round brackets or square brackets when a cultivar name or trade designation is given; if no cultivar or trade designation is given then these brackets are omitted. In outputs the word 'Group' always terminates the cultivar group name: eg. Brassica oleracea Cauliflower Group, Dracaena fragrans (Deremensis Group) 'Christianne' or Dracaena fragrans [Deremensis Group] 'Christianne'.

Cultivar Name

Transfer code: culnam

Domain/Range/Values: Alpha; any valid cultivar name. The entry should consist solely of the cultivar name. The abbreviation 'cv.' should not be used (except under Comments 3 below), nor should the entry be enclosed in single quotes (these should be added in printed outputs only).

1. The cultivar must be a valid name published under the International Code of Nomenclature for Cultivated Plants.

2. Where the cultivar name directly follows the generic name, as in Tulipa 'Apeldoorn', the fields between Genus name and this field should not be filled (namely, the fields from Subgeneric group name through to Cultivar Group Name).

3. If the record represents a cultivar of unknown name, then 'cv.' should be entered in this field. This appears to contradict the approach with species names, but in this case a blank, space or null does not imply that the taxon is an unidentified cultivar.

1. A cultivar is part of the variation of cultivated plants being clearly distinguished by attributes that are distinct, uniform, stable and are retained when propagated by a suitable means. For further details, see Article 2 of the International Code of Nomenclature for Cultivated Plants.

2. Under the provisions of the International Code of Nomenclature for Cultivated Plants, cultivar names are written in outputs as contained between single quotes, eg. Citrullus lanatus 'Sugar Baby'. Double quotes or the abbreviation prefix 'cv. ' are not permitted under the Cultivated Plant Code.

3 The first character of each word in a cultivar name should be in uppercase (A-Z).

Trade Designation Name

Transfer code: tranam

Description: The trade name of an accession, where the taxon has a registered trade name or other similar trade designation.

1. An entry in this field should consist solely of the trade designation name, if applicable.

2. If the accession does not bear a designated trade name, this field should not be filled.

Comments: The trade name must be a valid name published under the International Code of Nomenclature for Cultivated Plants and accepted by the International Registration Authority for the group concerned.

Guidelines: Trade names are used in place of or additional to a cultivar name when the accepted cultivar name is not considered suitable for marketing purposes.

Full Name

Transfer code: fulnam

Description: The full name of the plant, including full author citation, hybrid name, hybrid formula, collective name, cultivar name (as appropriate).

Domain/Range/Values: Free text field. All previous rules, as described under the above name fields, apply in this field.

Comments: This field allows the full taxonomic name (including author citation), horticultural names, trade names and patents. Where there is more than one infraspecific rank (eg. quadrinomials or pentanomials), the reduction of this plant name to a trinomial (with only the lowest infraspecific rank cited) obscures much of the infraspecific hierarchy (refer discussion under RECORD IDENTIFICATION GROUP above).

Name Comments

Transfer code: namcom

Description: Any comments about the name of the plant are transferred in this field.

Comments: Although mixed collections are unacceptable in HISPID3, this field can be used to refer to such collections when the mixture is not significant.

TYPIFICATION GROUP

This group of fields conains three fields, Type Qualifier, Type Status and Basionym, which covers the typification of the name of the taxon as directly related to the accession record.

Type Qualifier Flag

Transfer code: tql

Description: This field provides standard terms to qualify the identification of the type of the name of the record when doubts exist.

Comments: This field is used in conjunction with Type Status (below). If the Type Status field is not filled, then this field must not be used.

Type Status

Transfer code: tsta

Domain/Range/Values: Alpha; standard abbreviation, as listed in the following table:

EPI	epitype
HOLO	holotype
ISO	isotype
ISOLECTO	isolectotype
ISONEO	isoneotype
ISOPARA	isoparatype
ISOPARALECTO	isoparalectotype
ISOSYN	isosyntype
KLEPTO	kleptotype
LECTO	lectotype
NEO	neotype
PARA	paratype
PARALECTO	paralectotype
SYN	syntype
TOPO	topotype
TYPE	Unknown type material

Comments: This field is not to be filled if the record is not one of these kinds of type.

Although topotypes have no taxonomic or nomenclatural status, the category has been included for those who may wish to interchange this information.

Basionym

Transfer code: basnam

Description: The plant name (frequently the basionym) of which this specimen is a type, not necessarily the accepted name for the taxon.

Domain/Range/Values: Alpha; a valid plant name, including relevant rank identifiers (such as subsp., var.,) as required, conventional capitalisation of name and author.

Comments: Although a specimen may be the type of more than one basionym, this field must hold the most recent known name. When a specimen is the type of more than one basionym, then the following additional fields refer to the second most recent basionym, together with its type status: Type Status of Second Most Recent Basionym and Second Most Recent Basionym fields (Transfer codes: tsta2 and basnam2, respectively). If more earlier basionyms are to be transferred, then the third most recent values are interchanged in the : Type Status of Third Most Recent Basionym and Third Most Recent Basionym fields (Transfer codes: tsta3 and basnam3, respectively), and so on, as appropriate. The type qualifier field may be required to provide qualification to the identification of the types of the various earlier basionyms. These additional fields are briefly described below.

Second Most Recent Type Qualifier

Transfer code: tql2

Description: This field provides standard terms to qualify the identification of the type of the name of the second most recent basionym of the record when doubts exist.

Domain/Range/Values: Alpha; as listed in Type Qualifier Flag field (above).

Comments: This field is used in conjunction with Second Most Recent Type Status field (below). If the Second Most Recent Type Status field is not filled, then this field must not be used.

Second Most Recent Type Status

Transfer code: tsta2

Description: A code indicating the type status of the second most recent basionym of the record.

Domain/Range/Values: Alpha; standard abbreviation, as listed in Type Status field (above).

Comments: For further information refer to previous TYPIFICATION GROUP fields (above).

Second Most Recent Basionym

Transfer code: basnam2

Description: The second most recent basionym of which this specimen is a type, not necessarily the accepted name for the taxon.

Domain/Range/Values: Alpha; a valid plant name, including relevant rank identifiers (such as subsp., var.,) as required, conventional capitalisation of name and author.

Comments: For further information refer to previous TYPIFICATION GROUP fields (above).

Third Most Recent Type Qualifier Flag

Transfer code: tql3

Description: This field provides standard terms to qualify the identification of the type of the name of the third most recent basionym of the record when doubts exist.

Comments: This field is used in conjunction with Third Most Recent Type Status field (below). If the Third Most Recent Type Status field is not filled, then this field must not be used.

Third Most Recent Type Status

Transfer code: tsta3

Description: A code indicating the type status of the third most recent basionym of the record.

Domain/Range/Values: Alpha; standard abbreviation, as listed in Type Status field (above).

INTRODUCTION	5	RECORD IDENTIFICATION GROUP	29
Format of HISPID3	5	'Full' Scientific Name	29
Definitions	6	'Limited' Scientific Name	29
Italics	6	Hybrids, Intergrades	29
Nulls	7	Vernacular Names	30
Single character fields	7	Higher Group Names	30
Codes	7	Plant Name Authorities	30
Relevant Standards	7	Other Comments	30
Summary of the important features of a HISPID3 file	8	HYBRIDS, GRAFTS, CHIMAERA AND INTERGRADES	32
Example of the start and end of a HISPID3 file	8	CULTIVATED PLANT NAMES	45
An example of a filled HISPID3 interchange file	9	TYPIFICATION GROUP	50
FORMAT OF THE TEXT IN THIS DESCRIPTION OF A HISPID3 FILE	11	VERIFICATION GROUP	55
The full field name	11	Identification Qualifiers	55
The transfer identifier code	11	LOCATION GROUP	63
TDWG Short name	11	Subsequent Location Fields	63
The field description	11	Geocode Information	63
Relevant standards	11	Spatial Data Interchange	64
Domain/Range/Values	11	HABITAT GROUP	79
Comments	11	COLLECTION GROUP	85
Rules	11	Subsequent Collection Fields	85
Notes	11	KIND OF COLLECTION, ADDITIONAL COMPONENTS and VOUCHER COLLECTIONS	93
FILE IDENTIFICATION FIELDS	13	ADDITIONAL DATA GROUP	103
FILE IDENTIFIER GROUP	13	LOAN GROUP	111
ACCESSION INFORMATION Fields	21	DATA ENTRY AND EDIT GROUP	117
ACCESSION IDENTIFIER GROUP	21	INDEX	121
BASIS OF RECORD GROUP	25

startfile
version	"HISPID3",
numrec	2,
datefile	19951202,
institute	"National Herbarium of New South Wales (NSW)",
contact	"Gary Chapple",
address	"Royal Botanic Gardens, Mrs Macquaries Road, Sydney NSW 2000, Australia",
phone	612 92318164,
fax	612 92517231,
email	"gary@rbgsyd.gov.au",
fileaction	"insert",
filedescriptor	"exchange",
content	"Herbarium exchange data of various species from NSW to CANB",
{
insid	"NSW",
accid	"390839",
fam	"Loranthaceae",
gen	"Amyema",
sp	"pendulum",
isprk	"subsp.",
isp	"longifolium",
vnam	"Wiecek, B.M.",
vdat	1995,
prot	"Wild",
cou	"AUSTRALIA",
pru	"NSW",
sru	"Central W. Slopes",
loc	"Mount Bolton, Moura",
latdeg	33,
latmin	15,
latdir	"S",
londeg	148,
lonmin	24,
londir	"E",
cnam	"Baeuerlen, W.",
cdat	190103,
hab	"On Eucalyptus macrorrhyncha.",
misc	"Donated by Museum of Applied Arts & Sciences, 1979.",
}
{
insid	"NSW",
accid	"248836",
fam	"Asclepiadaceae",
gen	"Cynanchum",
sp	"pedunculatum",
vnam	"Hill, K.D.",
vdat	1992,
prot	"Wild",
cou	"AUSTRALIA",
pru	"WA",
sru	"Fortescue",
loc	"Mount Lois.",
alt	800,
latdeg	22,
latmin	06,
latdir	"S",
londeg	117,
lonmin	44,
londir	"E",
geoacy	0.05,
hab	"Summit of mountain. Red loam derived from iron-rich shale.",
cnam	"Wilson, Peter G.",
cid	"1031",
cnam2	"Rowe, R.",
cdat	19910911,
cnot	"Rare. Scrambler. Flowers white; fruit green.",
}
endfile

startfile
version	HISPID version
numrecords	number of records in this file
datefile	date to which the file refers
institute	full name of institution supplying information
contact	contact name
address	postal address
phone	telephone number
fax	fax number
email	email address
nonstandard	optional field to describe any non-standard fields added to the HISPID3 transfer file
fileaction	descriptor flag indicating how records of file should be processed
filedescriptor	descriptor flag indicating the nature of the records included in file
content	contents of the file and other comments
{	start of a record
insid	the standard 'Index Herbariorum' code for the herbarium to which the plant record refers
accid	accession number
...
...
\|
\|
...
}	end of record
{	start of next record
insid
accid
...
\|
\|
...
}	end of next record
endfile	end of file

Values in Field	Meaning
delete	delete all records in file from institutional database receiving transfer file
insert	all records in file to be added to receiving database
update	update relevant fields of all records in file in receiving database

Values in Field	Meaning
exchange	records in file to be added to receiving database as part of exchange of herbarium material
loan	electronic herbarium data associated with loan of herbarium material
repatriation	repatriation of electronic data (from duplicate material held at sending institution to receiving institution) to the database held at the latter institution.

hyb	"+",
gen	"Xyringa",
sp	"correlata",

gen	"Salix ",
sp	"matsudana",
culnam	"Tortuosa",