Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
database_structure [2008/09/10 11:09]
jchrist this should be a wiki not a kind of blog
database_structure [2015/06/23 17:22] (current)
Line 1: Line 1:
-====== ​Report from the Aix meeting ​of ======+ 
 +======= Database structure ======= 
 + 
 +====== Aim ===== 
 +**The EPD is set up as a [[http://​en.wikipedia.org/​wiki/​Relational_database |relational database]] consisting of a large number of tables to allow querying ​the data in complex ways and to minimise the storage space required. The aim of the database structure support group is to find and maintain a table structure and database management system that is adequate and up to date for the widest possible use of the EPD. The group is maintaining and fostering links to other palaeo-environmental databases like the ALPine Pollen DAtaBAse (ALPADABA) housed in Bern (Switzerland),​ [[Neotoma]],​ the [[http://​medias.obs-mip.fr/​apd/​ |African Pollen Database (APD)]], [[PANGAEA]],​ and [[http://​www.bugscep.com/​|BugsCEP]]. 
 +** 
 + 
 +---- 
 + 
 + 
 +**The Publishing Network for Geoscientific & Environmental Data [[PANGAEA]] offers to support the EPD** 
 + 
 +---- 
 + 
 + 
 +**We are keeping track of developments of pollen databases and had a closer look at the [[Neotoma]] database** 
 + 
 + 
 + 
 + 
 +===== Review of the existing EPD table structure ​===== 
    
 Walter Finsinger, Simon Brewer, Thomas Giesecke and Basil Davis met in Aix between Mai 29 and 31. We reviewed the EPD table structure, discussed working protocols with Michelle Leydet and helped John Keltner to correct mistakes in the database. We are grateful to John, Michelle and Valérie Andrieu for advice in discussions and support. ​ Walter Finsinger, Simon Brewer, Thomas Giesecke and Basil Davis met in Aix between Mai 29 and 31. We reviewed the EPD table structure, discussed working protocols with Michelle Leydet and helped John Keltner to correct mistakes in the database. We are grateful to John, Michelle and Valérie Andrieu for advice in discussions and support. ​
Line 7: Line 28:
  
 //This report attempts to summarize the major discussions from the work meeting and suggests a few guidelines or protocols. None of the items are set in stone but they should serve as a base of discussions.// ​ //This report attempts to summarize the major discussions from the work meeting and suggests a few guidelines or protocols. None of the items are set in stone but they should serve as a base of discussions.// ​
- 
-===== Revision of the database structure ===== 
  
  
 We first reviewed the **paradox table structure** (Fig. 1) that the EPD is currently held in and identified fields that have not been used, items that should be combined or items that should be added. We first reviewed the **paradox table structure** (Fig. 1) that the EPD is currently held in and identified fields that have not been used, items that should be combined or items that should be added.
  
-{{epd_tables.jpg|}}+{{epd_tables.jpg?900x600}}
  
  Fig. 1: //Table structure and relationships of the most important EPD paradox tables (here imported in Access).//  Fig. 1: //Table structure and relationships of the most important EPD paradox tables (here imported in Access).//
Line 26: Line 45:
 Table ‘Entity’:​ IsCore, IsSect, IsSSamp could be combined into a field or combined with Descriptor. ​ Table ‘Entity’:​ IsCore, IsSect, IsSSamp could be combined into a field or combined with Descriptor. ​
  
-Table ‘Entity’:​ It would be good to add an identifier for a single publication that should be cited when using the dataset. The database should hold references to many publications that are describing the dataset, but when citing many records it is often only possible to cite one publication. Ideally, the person who submits data to the DB should indicate the reference to the publication that should be cited whenever the dataset is used.+Table ‘Entity’:​ It would be good to add an identifier for a single publication that should be cited when using the dataset. The database should hold references to many publications that are describing the dataset, but when citing many records it is often only possible to cite one publication. Ideally, the person who submits data to the DB should indicate the reference to the publication that should be cited whenever the dataset is used. However, one single publication is in some cases not sufficient: (1) Sometimes a diagram is published in two parts in different publications (e.g., Late Glacial in one and Holocene in another). (2) Sometimes the C14 dates, or part of them, are published in a later publication,​ separate from the original publication with the pollen diagram.
  
 Table ‘Entity’:​ The variables ‘IceThickCM’ and ‘C14DepthAdj’ may be deleted and the data that is present could be stored in a free text ‘notes’ field in an appropriate table. Table ‘Entity’:​ The variables ‘IceThickCM’ and ‘C14DepthAdj’ may be deleted and the data that is present could be stored in a free text ‘notes’ field in an appropriate table.
Line 59: Line 78:
  
  
-==== Data entry: ​==== +** Data entry: ​** 
  
  
Line 68: Line 87:
 c) Maximum possible c) Maximum possible
  
-==== When receiving a new dataset: ​====+** When receiving a new dataset: ​**
  
  
Line 79: Line 98:
 Any other problem contact regional work group. ​ Any other problem contact regional work group. ​
  
-==== Before entering the data: ====+** Before entering the data: **
  
  
Line 107: Line 126:
 Ask Taxonomy group to fix existing errors. Ask Taxonomy group to fix existing errors.
  
-=== Metadata mistakes: ​===+ 
 +** Metadata mistakes: ​**
  
  
Line 184: Line 204:
  
  
-~~DISCUSSION~~+ 
 +**You have to be logged for write access** 
 + 
 + 
database_structure.1221037765.txt.gz · Last modified: 2015/06/25 16:07 (external edit)
Back to top
chimeric.de = chi`s home Creative Commons License Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0