This table lists all field names & column types for the MySQL database table 'refs' that's used in conjunction with refbase 0.8.0:
Field | Type | Example | Comment |
---|---|---|---|
author | text | Clough, LM; de Broyer, H-C; Ambrose Jr., WG | The author(s) of a publication. Separate family and given names with a comma & a space (', '). Multiple authors are separated with a semicolon & a space ('; '). |
address | text | School of Environmental Sciences, University of East Anglia, Norwich, Norfolk, NR4 7TJ, UK, mailto:author@geos.com | The author's address or any other contact information like the email of the corresponding author. Separate multiple addresses with a semicolon & a space ('; '). |
corporate_author | varchar(255) | University of California | Use this field when the author of a particular publication is not a person, but an organization, government agency, company or other group. The personal author (if there is one) is subordinate to the organisation. In the case of a thesis, the student's institution (or university) can be regarded as the corporate author of the student's work. Sometimes, the corporate author is identical to the publisher of a publication. |
first_author | varchar(100) | Clough, LM | This field holds the family and given name of the first author. It is required for proper sorting of references when citing. On edit refbase will automatically extract the first author from the author field and copy it to this field. |
author_count | tinyint(3) unsigned | 3 | The number of authors of a publication. It is required for proper sorting of references when citing. On edit refbase will automatically assign the correct author count to this field. |
title | text | Life and benthic environment in the Barents Sea | The title of a publication; don't append any dot to the title. |
orig_title | text | Zhizn' i usloviya ee sushchestvovaniya v bentali Barentseva morya | Use this field for the original title of a publication if the title given in the title field is a translated or transliterated version of the original title. |
publication | varchar(255) | Marine Ecology Progress Series | The full title of the journal or the book title. |
abbrev_journal | varchar(100) | Mar Ecol Prog Ser | In case of journals, the abbreviated journal title. |
year | smallint(6) | 1998 | The publication year; specify years in 4-digit format. |
volume | varchar(50) | 56A | The volume of a publication. |
volume_numeric | smallint(5) unsigned | 56 | The number part of the publication volume. refbase uses this field when sorting by volume . While the volume field accepts any text the field volume_numeric is of numeric type and can only contain numbers. On edit refbase will automatically extract the first number from field volume and copy it to this field. |
issue | varchar(50) | 4 | The issue (i.e. number) of a publication. |
pages | varchar(50) | 12-18 | The page range (or total number of pages) of a publication. For journal articles & book chapters use the page range like in '12-18' (no 'pp'), for whole books enter the total no. of pages like in '316 pp' (i.e. append 'pp') |
first_page | mediumint(8) unsigned | 12 | The first page of a publication (for journal articles or book chapters) or the total no. of pages in case of whole books. refbase uses this field when sorting by pages . On edit refbase will automatically extract the first number from field pages and copy it to this field. |
keywords | text | sea ice; flooding; primary productivity; PS, Antarctic Ocean; PSW, Weddell Sea | Any keywords given by the authors of the publication. A user's personal keywords should be entered in the user-specific field user_keys (MySQL table 'user_data'). Separate multiple (unrelated) keywords with a semicolon & a space ('; '), if some keywords are somehow related, you may optionally separate them with a comma & a space (', ') instead. |
abstract | text | Organic matter displayed a pronounced seasonal variation in carbon isotopes (expressed as [delta][super:13]C_[sub:OM]_). | The abstract or summary of the publication. The title , address , keywords and abstract fields support a markup language to provide rich text capabilities (i.e. italics, super/sub-script, greek letters, etc). E.g., the markup in the example would display as δ13COM. See Refbase markup syntax as well as the file initialize/ini.inc.php for further information. |
edition | tinyint(3) unsigned | 2 | The edition number of a publication. |
editor | text | Ackley, SF; Weeks, WF | The editor(s) of a publication. Format names as described for field author . |
publisher | varchar(255) | American Geophysical Union | The publisher of a publication. |
place | varchar(100) | Washington, DC | The place of publication. |
medium | varchar(50) | CD-ROM | Contains the medium type of a publication if not paper (e.g. CD-ROM, cassettes, disks, transparencies, negatives, slides, etc.) |
series_editor | text | Strelkov, A | The series editor(s). Format names as described for field author . |
series_title | text | UNESCO Monographs on Oceanographic Methodology | If the publication is part of a series, this field holds the full title of the series. |
abbrev_series_title | varchar(100) | UNESCO Monogr Oceanogr Methodol | The abbreviated series title. |
series_volume | varchar(50) | 6 | The series volume of a publication. |
series_volume_numeric | smallint(5) unsigned | 6 | The number part of the series volume. refbase uses this field when sorting by series_volume . While the series_volume field accepts any text the field series_volume_numeric is of numeric type and can only contain numbers. On edit refbase will automatically extract the first number from field series_volume and copy it to this field. |
series_issue | varchar(50) | II | The issue (i.e. number) of the series volume. |
issn | varchar(100) | 0148-0227 | If the publication is (part of) a journal or a dissertation, specify it's ISSN number in this field. |
isbn | varchar(100) | 0-12-026143-X | If the publication is a book (chapter), specify it's ISBN number in this field. |
language | varchar(100) | Russian | The language of the body text. |
summary_language | varchar(100) | English; Russian | The language of the summary or abstract. Separate multiple language identifiers with a semicolon & a space ('; '). |
area | varchar(255) | Antarctic; McMurdo Sound | The area of investigation this publication deals with. Multiple items should be separated with a semicolon & a space ('; '). |
type | varchar(100) | Journal Article | The reference type of a publication. By default refbase recognizes 'Journal Article', 'Book Chapter', 'Book Whole', 'Journal', 'Manuscript' and 'Map'. |
thesis | enum("Bachelor's thesis","Master's thesis","Ph.D. thesis","Diploma thesis","Doctoral thesis","Habilitation thesis") | Ph.D. thesis | If the publication is a thesis, specify the degree in this field. By default refbase recognizes 'Bachelor’s thesis', 'Master’s thesis', 'Ph.D. thesis', 'Diploma thesis', 'Doctoral thesis' and 'Habilitation thesis'. |
expedition | varchar(255) | Norwegian Antarctic Research Expedition (NARE) 2000/2001 | The name of the expedition where sampling took place. |
doi | varchar(100) | 10.1007/s00300-004-0674-5 | The unique Digital Object Identifier (DOI) of this publication. |
conference | varchar(255) | International Symposium on Polar Aspects of Global Change, Tromsø (Norway), 24-28 Aug 1998 | The conference this publication was initially presented at. |
url | varchar(255) | http://www.int-res.com/abstracts/meps/v251/p37-47.html | The web address providing more information for this publication. |
call_number | text | IPÖ @ msteffens @ 83; IPÖ @ mschmid @ Be 100; AWI @ tmock @ Ice-23 | Contains a user's identifier tag & personal reference number that uniquely identifies this record for the user. Multiple items should be separated with a semicolon & a space ('; '). This field is controlled (and automatically filled) by refbase on edit. Syntax: institutional abbreviation @ email user name @ personal reference number |
location | text | Matthias Steffens (msteffens@ipoe.de); Michael Schmid (mschmid@ipoe.de); Thomas Mock (tmock@awi.ac.uk) | Contains all users who have added this record to their personal literature data set. Multiple users should be separated with a semicolon & a space ('; '). Like the call_number field, this field is controlled (and automatically filled) by refbase on edit. Syntax: user name (email address) |
contribution_id | varchar(100) | IPÖ; AWI | Holds the institutional abbreviation of a database user if this publication was published by this user or a member of his institution. Multiple items must be separated with a semicolon & a space ('; '). Information in this field can be used to generate a dynamic web page of all publications that were published by a particular institution. See here for more information. |
online_publication | enum("no","yes") | no | Set to 'yes' if this publication is an online publication that has no print equivalent (yet). Must be either 'yes' or 'no'. |
online_citation | varchar(255) | L09402 | Contains any additional information that's required to locate the online location of the publication. If online_publication is 'yes', the contents of this field will be printed (together with the doi number) in place of pages when citing. |
file | varchar(255) | Science295p641.pdf | The name of (or path to) a file that's associated with this publication (e.g. a PDF file). The file field accepts full URLs (which must start with either 'http://' or 'ftp://') as well as relative or absolute paths to the file (if it's located on your server). Any string that's not a full URL will be prefixed with the string given in $filesBaseURL (file initialize/ini.inc.php). |
notes | text | Species identification book; richly illustrated keys with 135 tables with b/w morphological drawings | Any generic notes for this publication. Multiple items should be separated with a semicolon & a space ('; '). A user's personal notes should be entered in the user-specific field user_notes (MySQL table 'user_data'). |
serial | mediumint(8) unsigned | 1297 | The unique database serial number of the publication (i.e. the MySQL primary key). The serial number is automatically filled in by MySQL when importing/adding records and is used to uniquely identify a particular database entry. |
orig_record | mediumint(9) | -1297 | In the case of duplicates, this field indicates whether this record is considered as the original record or as a duplicate entry. If it's an original record, the orig_record field contains the record's own serial number prefixed with a minus ('-') sign. If this record is a duplicate entry, orig_record will contain the serial number of the original record. By this, the orig_record field can be used to flag or hide any duplicates and point to the original record instead. Currently, refbase will only flag original/duplicate records using appropriate icons. |
approved | enum("no","yes") | yes | Set to 'yes' if you've verified this record for correctness, otherwise set to 'no'. Must be either 'yes' or 'no'. |
created_date | date | 2004-12-31 | The creation date of this record. This field is controlled (and automatically filled) by refbase when adding a record. Date format must be YYYY-MM-DD . |
created_time | time | 19:08:44 | The creation time of this record. This field is controlled (and automatically filled) by refbase when adding a record. Time format must be HH:MM:SS . |
created_by | varchar(100) | Matthias Steffens (msteffens@ipoe.de) | Contains the name and email address of the person who created this record. This field is controlled (and automatically filled) by refbase when adding a record. Syntax: user name (email address). |
modified_date | date | 2005-03-22 | The modification date of this record. This field is controlled (and automatically filled) by refbase when editing a record. Date format must be YYYY-MM-DD . |
modified_time | time | 23:50:52 | The modification time of this record. This field is controlled (and automatically filled) by refbase when editing a record. Time format must be HH:MM:SS . |
modified_by | varchar(100) | Michael Schmid (mschmid@ipoe.de) | Contains the name and email address of the last person who modified this record. This field is controlled (and automatically filled) by refbase when editing a record. Syntax: user name (email address). |