Citation Vocabulary for Taxonomic Literature Elements Needed:
A. Title types (there is an implicit equivalency relationship between each of these):
1. Title: (string) full long title in original language of publication (e.g., Systema
Naturae per regna tria naturae, secundum Classes, Ordines, Genera, Species, cum
characteribus, differentiis, synonymis, locis.”)
2. UniformTitle: (string) keep but use the specific definition used by libraries (used
to link to MARC)
3. ParallelTitle: (string) Any translated title
4. AlternateTitle: (string) anything ever used as a title for a work (repeatable, may be
used to build a list of synonyms used in literature).
5. MicrocitationTitle: (string) abbreviated or other title form recommended for use
in taxonomy & nomenclature. In Botany, this is likely to come from BPH or TL2 (may be used to build microcitation, e.g. Syst. Nat. or Sp. Pl.)
6. FullCitationTitle: (string) title form that is used most frequently in full
bibliographic citations (e.g., Systema Naturae or Species Plantarum)
B. Agent types: The group agrees to adopt a common agent format for all ‘agents’.
Also agrees that we do not recommend creating a GUID of any kind for Teams of
agents, instead have a way to deal with one to many without a specific identifier
(other than a string) for teams. Possible roles for adoption:
7. Author (author of work at the level of current record)
8. Editor
9. Publisher
10. Translator
11. Taxon Author (for microcitation)
12. Ex Author (for microcitation)
13. Other <unspecified contributor> (refer to lists from LOC, Dublin Core)
C. Dates (and related data) types:
14. VerbatimDate: (string) date or date range taken directly from cover page or other
source in document itself (if date not on cover page). Verbatim date is given in
whatever calendar system that it was originally cited from (the nomenclatural
codes are uninformative about calendar systems).
15. BeginDate: (ISO or w3c date field) earliest date that something was or may have
been published. If date(s) is/are certain, then it is the earliest or only date of the
range. If certain dates are known for sections of the work, then child records
should be created to specify the dates for each page or range of pages. This
should be done to the point at which the BeginDate and EndDate are the same, if
possible.
16. BeginDateSource: (string) – The reference to a source or an explanation of
research or data used to for BeginDate, especially if from outside the work – may
belong in metadata only.
17. EndDate: (ISO or w3c date field) latest date that something was or may have been
published. If date(s) is/are certain, then it is the latest or a repeat of the only date
of the range.
18. EndDateSource: (string) – The reference to a source or an explanation of research
or data used to for BeginDate, especially if from outside the work – may belong in
metadata only.
19. SumbissionDate: (ISO or w3c date field) – The date a manuscript was received by
the editor or publisher for publication. May come from the work itself or from
correspondence researched after the fact. – may belong in metadata only.
20. AcceptedDate: (ISO or w3c date field) – The date a manuscript was received by
the editor or publisher for publication. May come from the work itself or from
correspondence researched after the fact. – may belong in metadata only.
21. VolumeDate: The declared Year (or date) that corresponds to a Volume in
Journals or other Serials. This may or may not correspond to some or all of the
publication dates. It should not be confused with any of the above dates.
22. In order to make sure that a person or application knows to look for child records
if created to deal with dates for parts of a single work (or for other reasons), there
should be a string to inform them to look for child records in the parent record.
o All agree that Nomenclatural dates may override the publication dates as known
for various reasons. This should be left for the taxon-level vocabulary.
o The group did not come to a final conclusion about whether the Year portion of
the ISO fields BeginDate and EndDate should also be repeated (denormalized)
and made available separately for searching or other purposes. This will be
discussed and concluded on the Wiki on or before 31 March 2008.
D. Editions, parts of and relationships between works:
23. Edition: (string) a republication with modification of the same work (independent
of author)
24. Republication: (string) a republication (microfiche, scanned edition, or other
facsimile) or reprint without modification (page numbering may differ, but other
content remains the same)
25. Copy: (string) an individual copy of a work that is identified for a specific reason
(e.g., citation of marginalia, copy that was scanned for BHL, copy photographed
for microfiche).
26. Volume: (string) the highest level of enumerated pieces within a serial (other than
series), usually volume.
27. OtherPartLabel: (string; repeatable and structured) for anything between (or other
than) Volume and IssueLabel, e.g., subvolume.
28. IssueLabel: (string) the lowest level (highest granularity) of enumerated piece
within a serial (issue, number, etc.). This may be independent of volume (if
volume is present) or within volume or even a numbering of articles within some
portion of a journal.
29. NumberOfVolumes: (string) – (definition to be provided overnight) may belong
in metadata only.
30. Preceeding: (string) repeatable for Serials that change names and may also split or
merge at the same time.
31. Succeeding (string) repeatable for Serials that change names and may also split or
merge at the same time.
32. Synonyms: (identifier?) a equivalency property that allows linking records that
represent the same citation (may be different copies, different records from
different sources).
E. Data types that do not belong to the above groups:
33. Identifier: Identifiers: It was decided that the number of identifiers is potentially
infinite and changes based on domain. The recommendation is that a single form
for Identifiers needs to be created in the base/common domain and that all
identifiers should refer to that (similar to Agents, above). This will need to handle
the nested relationship between IdentifierValue and KindOfIdentifier. Although it
is possible to choose to create special categories for certain identifiers or classes
of identifiers, the group agreed that this would not be the best or most global
solution. A starting point for a vocabulary for KindOfIdentifier will be discussed
and concluded on the Wiki on or before 31 March 2008 (this vocabulary is
expected to grow as technology changes and as unusual examples come up).
34. Pagination: (string) to contain the string of all pagination, e.g., i-xii, 1-323, Pl. 115, maps 1-3. The group agreed that all information in this belongs in a single
string because there are too many variables, and atomizing would serve no
purpose for taxonomists. This corresponds to MARC 300b, “Extent”. We chose
to use a more descriptive name for the element.
35. PublicationType: There are many, many kinds of publications that could be
enumerated here. The group recommends that we follow recommendations used
in previous work by library cataloguers on this, but that we also devise a list that
is specific to taxonomy. This list of values to be used in PublicationType will be
defined on the Wiki before 31 March 2008. Lists to be used as a starting point
include the MARC standard, Rich Pyle’s list adapted from that in Endnote. These
lists will be put on the Wiki for discussion.
It is important to note that PublicationType defines the form/structure that a
Citation takes in a Bibliography. This should be taken into account when
compiling the list and recommendations made accordingly.
Comments to be included as best practice in explanations
 Series within Journals should be handled as separate titles, tied to the same
parent.
 Monograph & Book Series should be handled as a parent work.
 Section: Newspapers could be handled within Pagination for those few
taxonomic works published in newspapers.
Definitions & examples (to be expanded):
Microcitation: Emery, Boll. Mus. Zool. Torino, xi. p. 3 (1896).
Subreference: a section that has either a different authorship or a different effective
date.