|
|
Line 258: |
Line 258: |
| | | | | |
| The purpose of this guide is to lay out the governing principles and procedures that have evolved over the ten years of experience with the NYBG Virtual Herbarium. Hopefully this document will be useful in future years in explaining the rationale behind the approach taken and decisions made along the way, and may be useful to other institutions who are just now embarking on a Virtual Herbarium project, or searching for comparative or benchmark data. | | The purpose of this guide is to lay out the governing principles and procedures that have evolved over the ten years of experience with the NYBG Virtual Herbarium. Hopefully this document will be useful in future years in explaining the rationale behind the approach taken and decisions made along the way, and may be useful to other institutions who are just now embarking on a Virtual Herbarium project, or searching for comparative or benchmark data. |
| |}
| |
|
| |
| {|
| |
| == Relational database design and implementation for biodiversity informatics, by P. J. Morris, PhyloInformatics 7: 1-66 - 2005.==
| |
| !scope="col" width="15%" | Pub Date || 2005
| |
| |-
| |
| | '''URL'''
| |
| | http://www.athro.com/general/Phyloinformatics_7_85x11.pdf#
| |
| |-
| |
| | '''Description'''
| |
| |
| |
| The complexity of natural history collection information and similar information within the scope of biodiversity informatics poses significant challenges for effective long term stewardship of that information in electronic form. This paper discusses the principles of good relational database design, how to apply those principles in the practical implementation of databases, and examines how good database design is essential for long term stewardship of biodiversity information. Good design and implementation principles are illustrated with examples from the realm of biodiversity information, including an examination of the costs and benefits of different ways of storing hierarchical information in relational databases. This paper also discusses typical problems present in legacy data, how they are characteristic of efforts to handle complex information in simple databases, and methods for handling those data during data migration.
| |
| |} | | |} |
|
| |
|