https://github.com/weecology/livedat

Template for living data workflow
https://github.com/weecology/livedat

Last synced: 3 months ago
JSON representation

Template for living data workflow

• Host: GitHub
• URL: https://github.com/weecology/livedat
• Owner: weecology
• License: mit
• Created: 2018-04-17T12:44:27.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2019-01-30T05:08:59.000Z (almost 6 years ago)
• Last Synced: 2024-06-12T11:38:43.114Z (5 months ago)
• Language: R
• Size: 518 KB
• Stars: 15
• Watchers: 6
• Forks: 5
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• jimsghstars - weecology/livedat - Template for living data workflow (R)

README

        
[![Build Status](https://travis-ci.org/weecology/livedat.svg?branch=master)](https://travis-ci.org/weecology/livedat)

[![License](http://i.creativecommons.org/p/zero/1.0/88x31.png)](https://raw.githubusercontent.com/weecology/livedat/master/LICENSE)

# livedat

This is a **Template Repo** designed to assist in setting up a repository for regularly-updated data 

(new data are regularly added and need cleaning and curating). Read [our PLOS Biology paper](https://doi.org/10.1371/journal.pbio.3000125) for more details.

Instructions for creating an updating data workflow can be found at our companion website: 

## [UpdatingData.org](https://www.updatingdata.org/).

  The basic steps are:

    1. Clone the repository

    2. Configure the repository for your project

    3. Connect to Zenodo

    4. Connect to Travis

    5. Allow automated updating

    6. Add data code

    7. Add data

    8. Add data checks

    9. Update data

## Some Thoughts on Security

The Personal Access Token from GitHub provides full access to your entire account. It is equivalent to having your username and password. Travis and other CI companies are very serious about security, but there is always some risk when using credentials like this. To mitigate security issues you can set up a separate account purely for deploying your data and only give it access to the repositories that require it. Then use that account's Personal Access Token instead of the one for you primary account.