Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/petzi53/repairdata
Open Repair Alliance Datasets 2021
https://github.com/petzi53/repairdata
data open-data open-datasets r repair repair-cafe repairs
Last synced: 8 days ago
JSON representation
Open Repair Alliance Datasets 2021
- Host: GitHub
- URL: https://github.com/petzi53/repairdata
- Owner: petzi53
- License: other
- Created: 2021-10-18T21:18:50.000Z (over 3 years ago)
- Default Branch: master
- Last Pushed: 2021-10-22T21:13:20.000Z (over 3 years ago)
- Last Synced: 2024-04-27T03:03:58.045Z (9 months ago)
- Topics: data, open-data, open-datasets, r, repair, repair-cafe, repairs
- Language: R
- Homepage: https://petzi53.github.io/repairData
- Size: 986 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.Rmd
- License: LICENSE
Awesome Lists containing this project
README
---
output: github_document
---```{r, include = FALSE}
knitr::opts_chunk$set(
collapse = TRUE,
comment = "#>",
fig.path = "man/figures/README-",
out.width = "100%"
)
```# repairData
[![CRAN status](https://www.r-pkg.org/badges/version/repairData)](https://cran.r-project.org/package=repairData)
[![Lifecycle:
stable](https://img.shields.io/badge/lifecycle-stable-green.svg)](https://lifecycle.r-lib.org/articles/stages.html#stable)[![R-CMD-check](https://github.com/petzi53/repairData/workflows/R-CMD-check/badge.svg)](https://github.com/petzi53/repairData/actions)
Data is from the website of the [Open Repair Alliance](https://openrepair.org/open-data/downloads/). The structure of the data follows the technical documentation of the [Open Repair Data Standard](https://standard.openrepair.org/) (ORDS Version 0.21).
Besides the complete dataset `repairs` with 48,669 entries, I have also added four compiled datasets on `batteries`, `mobiles`, `printers`, and `tablets` with additional information about fault types.
## Aims of `repairData`
The goal of the `repairData` package is
- to create a joint approach to documenting successes and challenges with post-warranty repairs
- to promote it as a standard available to other community repair networks and in the future to commercial repairers and others collecting repair data
- to enable coalition members and others to use the data from our joint work to produce insights, intending to demand more repairable products, improved support, and access to better repair services
- to explore jointly additional information we can all collect to help make a stronger case for increased repairability. (Slightly changed from [Open Repair Data Standard](https://standard.openrepair.org/about.html).)Eventually, these datasets should help to extend the reach to commercial repairers and others collecting repair data. This data will be used to [tell stories](https://openrepair.org/open-data/insights/) about the positive impacts of repair and to inform advocacy. Together, we can make a stronger case for more easily repairable devices.
## Installation
You can install the released version of repairData from [CRAN](https://CRAN.R-project.org) with:
``` r
install.packages("repairData")
```And the development version from [GitHub](https://github.com/) with:
``` r
# install.packages("devtools")
devtools::install_github("petzi53/repairData")
```
## ExampleAfter loaded the package you have access to all datasets with the data() function.
```{r example}
library(repairData)
# simple example code
data(repairs)
# or all together
data(repairs, batteries, printers, mobiles, tablets)
```## Data specifications
The following table stems from the [documentation of the Open Repair Data Standard](https://standard.openrepair.org/standard.html#field-reference) (ORDS Version 0.21). (In the last column, I report my changes to the variable type of some columns according to the ORDS `Type` description.)
| Title | Field name | Type | R Data Type |
|---------------------|-------------------------------|-----------------------------------------------------------------------------------------------------------------|-------------|
| ID | id | Unique identifier from the partner organisation. Does not have to be unique across all partner data. | character |
| Partner category | partner_product_category | Option from partner codelist. | character |
| Product category | product_category | Option from ORDS *product category codelist*. | factor |
| Brand | brand | Free text. | character |
| Year of manufacture | year_of_manufacture | Year. YYYY. | character* |
| Problem | problem | Free text. Personal data should be removed, e.g. email addresses. | character |
| Repair status | repair_status | Option from ORDS *repair status codelist*. | factor |
| Repair barrier | repair_barrier_if_end_of_life | Option from ORDS *repair barrier codelist*. Optional. Only relevant where repair_status = "End of life". | factor |
| Group identifier | group_identifier | String. Unique. A unique identifier across all partners that can identify the group responsible for the repair. | factor |
| Event date | event_date | Date. YYYY-MM-DD format. The date of the repair event that the repair took place at. | Date |
| Data provider | data_provider | Option from ORDS codelist. Name of partner organisation. | factor |
| Country | country | String. 3 letter ISO code, e.g. “GBR”. | factor |
| Record date | record_date | Date. YYYY-MM-DD format. The date that the record was last updated. | Date |* Because of many NA's written as "????" I chose to import this column as "character".