Frequently asked questions


What is the Paleobiology Database?
How did the Database come into existence and how is it funded?
Who should I contact about the Database?
What data are now in the Database?
Who owns the Paleobiology Database?
How is the Database organized?
Who can contribute to the Paleobiology Database?
Who has access to the data?
Can I upload data into the Database?
Paleobiology Database Publications
PaleoDB Data Archives
How should Paleobiology Database data be cited?

What is the Paleobiology Database?
The Paleobiology Database (PaleoDB) is a non-governmental, non-profit public resource for paleontological data. It has been organized and operated by a multi-disciplinary, multi-institutional, international group of paleobiological researchers. Its purpose is to provide global, collection-based occurrence and taxonomic data for organisms of all geological ages, as well data services to allow easy access to data for independent development of analytical tools, visualization software, and applications of all types. The Database’s broader goal is to encourage and enable data-driven collaborative efforts that address large-scale paleobiological questions.

How did the Database come into existence and how is it funded?
The Paleobiology Database originated in the NCEAS-funded Phanerozoic Marine Paleofaunal Database initiative, which operated from August 1998 through August 2000. It was supported from 2000 to 2008 and from 2010 to 2013 by the US National Science Foundation has also received funding from the Australian Research Council. Many science-driven data entry projects have been funded by grants to individuals around the world.

John Alroy (Macquarie University) was one of the original founders of the PaleoDB (along with Charles Marshal). John was instrumental in the development of the PaleoDB in several different capacity. John served as the Database Administrator from 2000 to January of 2013, when the new role of Database Director was created, and John held that role until September of 2013.

Primary IT development is currently being carried out at UW-Madison under the direction of Shanan Peters and Michael McClennen, with support from NSF EAR Geoinformatics grant 0949416.

Who should I contact about the database?
General queries, bug reports, and feature requests should go the Executive Committee Chair.

Questions, comments, and suggested corrections regarding individual data records should be sent directly to the contributor who authorized the data. See our list of contributors for contact information.

To contribute data or analysis tools to the PaleoDB, contact the Executive Committee Secretary.

What data are now in the Database?
PaleoDB maintains full descriptions of many large datasets in the database in our Online Systematics Archives. You can also see what we know about the taxonomy of a group by generating a classification.

Who owns the Paleobiology Database?
All records are made available to the public based on a Creative Commons license that requires attribution before use, and also bars unlicensed derivatives and unlicensed commercial use.

Paleobiology Database is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.

How is the Database organized?
The Paleobiology Database is managed by the Executive Committee, which sets overall database policy, oversees matters related to the PaleoDB’s membership and access to data. The Committee consists of 12 members, including a Chair and a Secretary. The Chair is currently Mark D. Uhen and its Secretary is Jocelyn Sessa. Primary software development is being carried out at the University of Wisconsin-Madison under the direction of Shanan Peters and Michael McClennen.

The PaleoDB also has an External Advisory Board that advises the Executive Committee on Database activities and policies and promotes the use of the Database among the scientific community and forges links to other scientific communities and the general public.

TITLE
Database membership is open to all professional researchers who agree to abide by Database policy and contribute data. Most contributors have doctoral degrees, however, serious researchers without graduate-level training also may be considered. We expect that contributors will work largely independently of any academic supervisor, as opposed to using data collected by a supervisor. If you don't fit these criteria but do want to contribute, consider entering data under the authorization of a Database member. See our list of members for contact information and get in touch with them directly. If you do wish to join as a member, please contact the Secretary.

Who has access to the data?
Ultimately, everyone in the world has access to the data either through our display and visualization tools or through data services. We do allow researchers to embargo their own contributed data for short periods of time prior to their publication, but eventually all entered data becomes public and available to everyone. Protection is limited for up to one year after date of entry for previously published data, and up to five years for unpublished data.

Can I upload data into the Database?
We are able to accept paleontological data files for upload. However, PaleoDB needs some basic data types to be included in order to perform an upload. The best way to proceed is for you to become a member of the database first, see what kind of data we require, and then contact the Executive Committee Chair.

Paleobiology Database Publications
As with any public (and publicly funded) effort, we aim to keep track of our impact on science. Thus, PaleoDB would like to track those publications that use PaleoDB data. If you have a publication that uses data taken from PaleoDB, or a publication that results from research conducted while the author was funded specifically to work on or with PaleodB, we would like to give the publication an official Paleobiology Database publication number. Please notify the Secretary as soon as any such paper is accepted for publication and the final version is ready to be sent out. We will then give the publication a number that you can add a line to your paper saying "This is Paleobiology Database publication #..." We also encourage you to submit your electronic data files to be archived and made available on the web site.

Paleobiology Database Data Archives
Many contributors consider their contributed data sets to be electronic publications. If you have entered or uploaded a coherent set of data (for example, a particular taxonomic group, time period, or geographic area) simply write to the Secretary about your data set. Be sure to include a description of the scope of the data set, and a list of contributor, along with a title for the data set. PaleoDB will then post an entry on our E-Publications list that will reference the data set. The current list is here.

How should Paleobiology Database data be cited?
You can cite the Paleobiology Database in several ways. First, you can cite the specific e- publication that you used (see above). Second, you can refer to a specific download from the PaleoDB, giving the date and parameters of the download. Here is an example:

"The data were downloaded from the Paleobiology Database on 31 December, 2013, using the group name 'marine' and the following parameters: time intervals = Eocene and Oligocene, region = Europe, paleoenvironment = marine, Order = Cetacea."In such a case, you may want to cite or acknowledge the people who contributed the bulk of the data to the database.

We also strongly encourage that you create a secondary bibliography for work that uses large data sets. You can easily download all of the references that contributed to a dataset for this secondary bibliography. Many journals will accept a secondary bibliography as a supplementary material file, and this type of citation helps ensure that the hard work performed by members of our community collecting and describing fossil organisms gets acknowledged properly.


Page adapted (by Mark D. Uhen) on 10 September 2013 from the PaleoDB FAQs by John Alroy, after the original PMPD FAQ by John Alroy on 22 August 2000. Revised on an ongoing basis.