Annotation Database Import: Difference between revisions
Jump to navigation
Jump to search
(Progress on content.) |
No edit summary |
||
(8 intermediate revisions by the same user not shown) | |||
Line 3: | Line 3: | ||
As a trivial example, one survey might identify a fine substrate as comprising silt, sand and fine gravel while another might identify fine sediment as only silt. Ideally, the database will provide a way to preserve this distinction without introducing so much complexity that it becomes impossible to use and maintain. | As a trivial example, one survey might identify a fine substrate as comprising silt, sand and fine gravel while another might identify fine sediment as only silt. Ideally, the database will provide a way to preserve this distinction without introducing so much complexity that it becomes impossible to use and maintain. | ||
The database import process consists of three main steps | The database import process consists of three main steps: | ||
# [[Preparation of Import Data|Prepare data.]] | |||
# [[Label Mapping|Map annotation labels to database entities.]] | |||
# [[Import Data|Import the data using the import form.]] | |||
# [[Cache Tables|Regenerate caches.]] | |||
Latest revision as of 23:38, 6 May 2025
The database is intended as a retrospective view on data collected by many potentially narrowly-focused surveys. Each survey produces a large number of entities with distinctive forms and purposes that must be mapped onto entities in the database, whose structure is roughly static and which must remain comparable through time.
As a trivial example, one survey might identify a fine substrate as comprising silt, sand and fine gravel while another might identify fine sediment as only silt. Ideally, the database will provide a way to preserve this distinction without introducing so much complexity that it becomes impossible to use and maintain.
The database import process consists of three main steps: