this is for holding javascript data
Alberto Pepe edited Rule 8. Use community data repositories.md
almost 11 years ago
Commit id: 4df4df452d3939b1d81ee1f5b583fb1e21e00ddd
deletions | additions
diff --git a/Rule 8. Use community data repositories.md b/Rule 8. Use community data repositories.md
index 67879c9..b173e7e 100644
--- a/Rule 8. Use community data repositories.md
+++ b/Rule 8. Use community data repositories.md
...
# Rule 8. Foster and use
community data repositories.
For example, if your Sometimes the hardest and most time-consuming step of sharing data and code is finding and deciding where to put them. Your community
uses of reference probably already has and adopts a standard
repositories (eg repository. If you don't know where to start looking, ask an information or data scientist working in
astronomy, dbSNP your field. For example, if you are a biologist, any scholar in
genomics), upload bioinformatics can advise you on the best repository to host your data
to those repositories, and
if not try to promote code. If your field has no domain-based repository, your institution might have one.
In this case, your librarian should be able to instruct you on how to host your data at your institution. If
neither your community
doesn’t nor your institution have
a standard repository dedicated repositories, there are a variety of generic repository
site for example sites
like Dataverse, Figshare, and Dryad. A benefit to using a standard repository is that they provide a citation for your data and have guarantees about the longevity. We note that if you
have time it is good to describe your data with additional metadata can use (see
below). Appendix). If you get more ambitious,
publish everything as [interlinked URIs](http://www.w3.org/DesignIssues/LinkedData.html).
Rally your colleagues and establish best practices in your field. Make agreements how about
which standards and repositories are best used to deposit the data. Don’t make this an eternal discussion, get started and iterate based on your experiences. Engage your community by providing feedback on the quality of those data assets, praise those following the best practices, installing and
utilize these resources. The more the data created by your colleagues is accessible as an organized collection of some sort, the better your community’s research capacity. promoting a repository yourself?