tu9-jct-data/background.qmd at main · slub/tu9-jct-data · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
---
title: "Background"
---

The link between an agreement, its participating institutions, and the
journals it covers comes from a voluntary, partly manual process, rather than
an authoritative feed from publishers.

## How the data is assembled

1. A publisher and a library consortium (or a single institution) negotiate a
   [transformative agreement](https://esac-initiative.org/about/transformative-agreements/).
2. The consortium or institution registers it in the
   [ESAC Transformative Agreement Registry](https://esac-initiative.org/about/transformative-agreements/agreement-registry/).
   Sharing the terms is
   [voluntary](https://esac-initiative.org/about/transformative-agreements/share/),
   and agreements are registered at the consortium level rather than per member.
3. The [Journal Checker Tool](https://journalcheckertool.org/) (JCT) data team
   monitors ESAC regularly for new agreements, then contacts each consortium
   for the covered titles and the institutions with access.
4. The JCT publishes the result as CC0
   ["Transformative Agreements Public Data"](https://journalcheckertool.org/transformative-agreements/)
   with an [API](https://journalcheckertool.org/apidocs).
5. This site consumes that data and matches agreements to
   [TU9](https://www.tu9.de/) universities by [ROR](https://ror.org/) ID.

A single agreement can provide different institutions with access to different
title sets. The JCT records this in its per-agreement sheets. There is no fixed
one-to-one relationship between an agreement and its journal or institution
lists.

## How this site matches agreements

An agreement is listed for a university when one of the university's ROR IDs
appears among the agreement's participating institutions. A university is
represented by the ROR IDs listed for its `slug` in
[`data-raw/orgs.csv`](https://github.com/slub/tu9-jct-data/blob/main/data-raw/orgs.csv),
including libraries and university hospitals when those units have separate
ROR IDs. The `members_ror` column records which of those ROR IDs were matched
for each agreement.

## Sources

- Hope, H. (2020). Enabling accurate results within the Journal Checker Tool.
  *sOApbox, official blog of cOAlition S*, 18 November 2020.
  <https://www.coalition-s.org/blog/enabling-accurate-results-within-the-journal-checker-tool/>
- Kiley, R. (2023). Introducing new search features in the Journal Checker Tool
  for Transformative Agreements. *sOApbox, official blog of cOAlition S*,
  22 September 2023.
  <https://www.coalition-s.org/blog/introducing-new-search-features-in-the-journal-checker-tool-for-transformative-agreements/>