You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/collections/create.en.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ You are considering creating a new collection to track terms with Open Terms A
9
9
10
10
## Define metadata
11
11
12
-
First of all, define the [metadata]({{< relref "collections/metadata" >}}) of the collection you would like to create.
12
+
First of all, define the [metadata]({{< relref "collections/metadata" >}}) of the collection you would like to create and keep them ready to be used when setting up the repositories.
13
13
14
14
## Check existing collections
15
15
@@ -80,6 +80,10 @@ Issues labels will be added by the engine as problems are encountered when track
80
80
81
81
- Update the README file with proper metadata: topic, maintainers, jurisdictions, languages…
82
82
83
+
#### Update metadata
84
+
85
+
- Update the metadata file `metadata.yml` with the collection metadata you defined earlier.
86
+
83
87
### Snapshots
84
88
85
89
Create the snapshots repository by using the [`demo-snapshots` repository](https://github.com/OpenTermsArchive/demo-snapshots) as template:
A collection is defined by the following metadata.
9
9
10
-
## Description
11
-
12
-
A concise description of the collection topic.
13
-
14
-
### Examples
15
-
16
-
- Largest global social media
17
-
- Most used social media in France
18
-
- Dating apps
19
-
- Platforms providing services to businesses
20
-
21
-
## Name
22
-
23
-
Three words maximum.
24
-
25
-
### Examples
26
-
27
-
- Platform Governance Archive
28
-
- France Élections
29
-
- Dating
30
-
- P2B Compliance Assessment
31
-
32
-
## ID
33
-
34
-
An identifier derived from the collection name that can more easily be referenced in code. Use acronyms and replace spaces with dashes.
35
-
36
-
### Examples
37
-
38
-
-`pga`
39
-
-`France-elections`
40
-
-`dating`
41
-
-`p2b-compliance`
42
-
43
-
## Language
44
-
45
-
The expected language of the terms in the collection.
46
-
47
-
### Examples
48
-
49
-
-`English`
50
-
-`French`
51
-
-`All EU languages`
52
-
53
-
## Jurisdiction
54
-
55
-
The expected jurisdiction in which the terms in the collection apply.
56
-
57
-
### Examples
58
-
59
-
-`EU`
60
-
-`France`
61
-
-`EEA`
62
-
-`USA`
63
-
-`global`
64
-
65
-
## Roles
66
-
67
-
The name, URL and logo of the entities that will take responsibility for each of the necessary governance [roles]({{< relref "collections/governance" >}}).
| `startDate` | date ([ISO 8601 format: YYYY-MM-DD](https://en.wikipedia.org/wiki/ISO_8601)) | The date when tracking started |
66
+
| `endDate` | date ([ISO 8601 format: YYYY-MM-DD](https://en.wikipedia.org/wiki/ISO_8601)) | The date when tracking ended or will end. If not specified, tracking is ongoing. |
67
+
| `schedule` | string | A [cron expression](https://en.wikipedia.org/wiki/Cron#Cron_expression) that defines the tracking frequency |
68
+
| `serverLocation`| string (city name, [ISO 3166-2 country code](https://en.wikipedia.org/wiki/ISO_3166-2)) | The geographic location of the tracking server |
0 commit comments