Skip to content

Commit

Permalink
Merge pull request #37 from swerik-project/decision-11
Browse files Browse the repository at this point in the history
Ammend Decision 3 API structure
  • Loading branch information
fredrik1984 authored Nov 1, 2024
2 parents 0e77451 + 491d1e4 commit 664d9e2
Showing 1 changed file with 38 additions and 0 deletions.
38 changes: 38 additions & 0 deletions docs/decisions/decision-3+11_API-structure-of-data-repositories.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
# API structure of data repositories

## Status

Decided

- Decision: accepted

## Context

*Amendment to decision 3 following decision 8.*

We need to have a unifide API to access and work with quality estimation for each individual repository. An example is that we want to have the data to estimate the OCR quality (i.e. the test data) in the repository so when the repository is updated the estimation can be conducted.

This also includes that we need to store the estimated results in the corpus in a nice formats for the umbrella repository to easily access and use estimated quality.

See [#329](https://github.com/welfare-state-analytics/riksdagen-corpus/issues/329) for discussions.

## Decision
We store the data, test, and quality estimation in the following way.

### Data
/data/... -> the data is stored here

### Data integrity tests
/test/... -> data integrity tests of the specific data
/test/data/... -> data used by data integrity tests
/test/results/... -> test results by version stored for easy access
/test/docs/... -> data integrity test descriptions (decision 8)

### Quality estimation
/quality/... -> scripts used for quality estimation
/quality/data/... -> data used for quality estimation
/quality/estimates/... -> estimates by version stored for easy access
/quality/docs/... -> quality dimension descriptions (decision 8)

## Consequences
This will make clear where different data sources go.

0 comments on commit 664d9e2

Please sign in to comment.