Merge branch 'master' of github.com:luckinet/tabshiftr

.github/.gitignore

@@ -0,0 +1 @@
+*.html

DESCRIPTION

@@ -65,6 +65,5 @@ Suggests:
     knitr,
     rmarkdown,
     bookdown,
-    readr,
-    covr
+    readr
 VignetteBuilder: knitr

README.Rmd

@@ -18,11 +18,14 @@ options(knitr.kable.NA = '.')
 
 
 [![CRAN\_Status\_Badge](http://www.r-pkg.org/badges/version/tabshiftr)](https://cran.r-project.org/package=tabshiftr)
-[![R-CMD-check](https://github.com/EhrmannS/tabshiftr/workflows/R-CMD-check/badge.svg)](https://github.com/luckinet/tabshiftr/actions)
-[![Coverage Status](https://img.shields.io/codecov/c/github/EhrmannS/tabshiftr/master.svg)](https://codecov.io/github/EhrmannS/tabshiftr?branch=master)
-[![](http://cranlogs.r-pkg.org/badges/grand-total/tabshiftr)](https://cran.r-project.org/package=tabshiftr)
+[![DOI](https://zenodo.org/badge/248468235.svg)](https://zenodo.org/badge/latestdoi/248468235)
+
+[![R-CMD-check](https://github.com/luckinet/tabshiftr/workflows/R-CMD-check/badge.svg)](https://github.com/luckinet/tabshiftr/actions)
+[![codecov](https://codecov.io/gh/luckinet/tabshiftr/branch/master/graph/badge.svg?token=hjppymcGr3)](https://codecov.io/gh/luckinet/tabshiftr)
 [![Lifecycle:maturing](https://img.shields.io/badge/lifecycle-maturing-blue.svg)](https://lifecycle.r-lib.org/articles/stages.html)
 
+[![](http://cranlogs.r-pkg.org/badges/grand-total/tabshiftr)](https://cran.r-project.org/package=tabshiftr)
+
 ## Overview
 
 Data are stored in many different ways in tables or spreadsheets because no strict semantic or topographic standards for the organisation of tables are commonly accepted.

README.md

@@ -4,12 +4,14 @@
 # tabshiftr <a href='https://luckinet.github.io/tabshiftr/'><img src='man/figures/logo.svg' align="right" height="200" /></a>
 
 [![CRAN_Status_Badge](http://www.r-pkg.org/badges/version/tabshiftr)](https://cran.r-project.org/package=tabshiftr)
-[![R-CMD-check](https://github.com/EhrmannS/tabshiftr/workflows/R-CMD-check/badge.svg)](https://github.com/luckinet/tabshiftr/actions)
-[![Coverage
-Status](https://img.shields.io/codecov/c/github/EhrmannS/tabshiftr/master.svg)](https://codecov.io/github/EhrmannS/tabshiftr?branch=master)
-[![](http://cranlogs.r-pkg.org/badges/grand-total/tabshiftr)](https://cran.r-project.org/package=tabshiftr)
+[![DOI](https://zenodo.org/badge/248468235.svg)](https://zenodo.org/badge/latestdoi/248468235)
+
+[![R-CMD-check](https://github.com/luckinet/tabshiftr/workflows/R-CMD-check/badge.svg)](https://github.com/luckinet/tabshiftr/actions)
+[![codecov](https://codecov.io/gh/luckinet/tabshiftr/branch/master/graph/badge.svg?token=hjppymcGr3)](https://codecov.io/gh/luckinet/tabshiftr)
 [![Lifecycle:maturing](https://img.shields.io/badge/lifecycle-maturing-blue.svg)](https://lifecycle.r-lib.org/articles/stages.html)
 
+[![](http://cranlogs.r-pkg.org/badges/grand-total/tabshiftr)](https://cran.r-project.org/package=tabshiftr)
+
 ## Overview
 
 Data are stored in many different ways in tables or spreadsheets because
@@ -289,18 +291,18 @@ kable(output)
 
 # Contributions
 
--   tabshiftr is still in development. So far it reliably reorganises 20
-    different types of tables, but additional dimensions of
-    disorganisation might show themselves. If you encounter a table that
-    can’t be reorganised with the current infrastructure, we’d be more
-    than happy to collaborate on advancing `tabshiftr`.
--   Informative error management is work in process.
--   Moreover, the resulting schema descriptions can be useful for data
-    archiving or database building and `tabshiftr` should at some point
-    support that those schemas can be exported into data-formats that
-    are used by downstream applications (xml, json, …), following proper
-    (ISO) standards. In case you have experience with those standards
-    and would like to collaborate on it, please get in touch!
+- tabshiftr is still in development. So far it reliably reorganises 20
+  different types of tables, but additional dimensions of
+  disorganisation might show themselves. If you encounter a table that
+  can’t be reorganised with the current infrastructure, we’d be more
+  than happy to collaborate on advancing `tabshiftr`.
+- Informative error management is work in process.
+- Moreover, the resulting schema descriptions can be useful for data
+  archiving or database building and `tabshiftr` should at some point
+  support that those schemas can be exported into data-formats that are
+  used by downstream applications (xml, json, …), following proper (ISO)
+  standards. In case you have experience with those standards and would
+  like to collaborate on it, please get in touch!
 
 # Acknowledgement