forked from EDIorg/data-package-best-practices
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.Rmd
53 lines (38 loc) · 2.5 KB
/
index.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
---
title: "Data Package Best Practices"
author: "Environmental Data Initiative"
date: "`r Sys.Date()`"
site: bookdown::bookdown_site
output:
bookdown::gitbook:
toc_depth: 3
split_by: section
documentclass: book
bibliography: [book.bib, packages.bib]
# url: your book url like https://bookdown.org/yihui/bookdown
# cover-image: path to the social sharing image like images/cover.jpg
description: |
Best practice recommendations for data packages, described by
Ecological Metadata Language (EML).
link-citations: yes
github-repo: EDIorg/data-package-best-practices
---
# Data Package Best Practices {.unlisted .unnumbered}
### Overview
This website contains current \"Best Practice\" recommendations for ecological and environmental science data packages. These recommendations are directed towards the following goals:
- Minimize heterogeneity of EML-described data packages to simplify development and re-use of software
- Maximize interoperability to facilitate data synthesis
- Provide guidance and clarification on
- the use of Ecological Metadata Language (EML)
- design a data package
- prepare a data product for synthesis
To participate in the "Best Practices for Data Packages" project, see "[About this site](./about-this-site.html)".
### [EML Metadata Concepts](./eml-best-practices.html)
The recommendations for EML metadata apply to all data packages. This section subsumes V3 of the static PDF document "Best Practices for Dataset Metadata in Ecological Metadata Language (EML)," last updated in 2017. The entire most recent (versioned, citable) release will be made available as a PDF.
**[Best Practices for Dataset Metadata in Ecological Metadata Language (EML)](./eml-best-practices.html)**
### [Data Package Design](./data-package-design-for-special-cases.html)
Considerations for a well designed data package including special cases based on data type, format, or acquisition method. Examples are images, documents, raw data stored in other repositories.
**[Recommendations for data package design](./data-package-design-for-special-cases.html)**
### [Data Products for Synthesis Research](./scientific-domain.html)
Recommendations for community developed data products. The data packages are derived from raw data and reformatted to meet certain data harmonization standards. Many of these data products have extensive related code bases, which recommendations can take into account and link to.
**[Recommendations for data products from specific scientific domains](./scientific-domain.html)**