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/reference/roles.md
+14-19Lines changed: 14 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,9 +9,8 @@ aliases:
9
9
10
10
# Collection roles reference
11
11
12
-
A collection in Open Terms Archive is a set of tracked terms from various services, organized around a specific purpose or theme. This document outlines the different roles involved in operating and maintaining a collection.
13
12
14
-
Each role represents a set of responsibilities and tasks that contribute to the collection's success. A role can be filled by one or multiple people, and one person can fulfill multiple roles. All roles can be either volunteer or paid positions, depending on the collection's resources and needs.
13
+
Each role represents a set of responsibilities and tasks that contribute to the collection’s success. A role can be filled by one or multiple people or organisations, and one entity can fulfill multiple roles. All roles can be either volunteer or paid positions, depending on the collection’s resources and needs.
15
14
16
15
This reference guide serves as a practical tool for collection organizers. It helps them understand the different roles needed for a collection, assign responsibilities effectively, ensure all necessary tasks are covered, and plan for long-term sustainability.
17
16
@@ -55,39 +54,38 @@ Manages the technical operation of the collection's engine, ensuring it runs smo
55
54
- Update Open Terms Archive engine and deployment system
56
55
- Monitor and restart engine if needed
57
56
- Investigate and resolve technical issues through log analysis
58
-
-Verify regular updates of snapshots, versions, and datasets
57
+
-Ensure that snapshots, versions and datasets are published
59
58
- Report bugs and suggest improvements to engine repository
60
59
61
60
---
62
61
63
62
### Curator
64
63
65
-
Defines the purpose of the collection, defines its boundaries and ensures all included content aligns with that purpose.
64
+
Defines the purpose and scope of the collectionand ensures all included content aligns with it.
66
65
67
66
#### Responsibilities
68
67
69
-
- Define and maintain collection's strategic direction
68
+
- Define and maintain the collection’s strategic direction
70
69
- Ensure collection content aligns with defined purpose
71
-
- Guide collection's evolution and growth
72
70
73
71
#### Tasks
74
72
75
73
- Define and document collection scope
76
-
- Review and approve scope changes
77
-
- Communicate scope decisions to maintainers and contributors
78
-
- Evaluate collection's alignment with purpose
74
+
- Define and document level of openness to third-party contributions
75
+
- Answer any questions related to scope that emerge from maintainers and contributors
76
+
- Communicate scope updates to maintainers and contributors
77
+
- Ensure collection’s alignment with original purpose
79
78
80
79
---
81
80
82
81
### Maintainer
83
82
84
-
Ensures the integrity, quality, and accuracy of the collection's terms while managing community contributions.
83
+
Ensures the integrity, quality, and accuracy of the collection’s terms. Manages incoming contributions.
85
84
86
85
#### Responsibilities
87
86
88
87
- Ensure quality and accuracy of collection terms
89
-
- Manage and facilitate community contributions
90
-
- Maintain quality of tracked terms
88
+
- Manage and facilitate contributions
91
89
92
90
#### Tasks
93
91
@@ -98,7 +96,7 @@ Ensures the integrity, quality, and accuracy of the collection's terms while man
98
96
- Manage repository issues and pull requests
99
97
- Provide feedback to contributors
100
98
- Report issues to system administrator
101
-
-Suggest scope improvements to curator
99
+
-Refer scope conflicts in contributions to curator to open potential scope updates
102
100
- Report issues on the engine repository
103
101
104
102
---
@@ -138,7 +136,6 @@ Provides non-operational support such as funding or resources to facilitate the
138
136
#### Tasks
139
137
140
138
- Provide and manage funding
141
-
- Allocate required resources
142
139
- Support collection promotion
143
140
- Leverage network for visibility
144
141
- Advocate for collection adoption
@@ -147,7 +144,7 @@ Provides non-operational support such as funding or resources to facilitate the
147
144
148
145
### Analyst
149
146
150
-
Analyzes terms changes to identify significant modifications and produce actionable insights.
147
+
Analyses terms changes to identify significant changes and produce reports in various formats.
151
148
152
149
#### Responsibilities
153
150
@@ -157,11 +154,9 @@ Analyzes terms changes to identify significant modifications and produce actiona
0 commit comments