-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathenglish-guidelines.html
320 lines (278 loc) · 14.6 KB
/
english-guidelines.html
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
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
<!DOCTYPE html>
<html >
<head>
<meta name="protocol-title" content="English guidelines | INBO protocols" />
<meta name="protocol-subtitle" content="" />
<meta name="protocol-code" content="" />
<meta name="protocol-version" content="" />
<meta name="protocol-language" content="" />
<meta name="protocol-theme" content="" />
<meta name="protocol-reviewer" content="" />
<meta name="protocol-file-manager" content="" />
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<title>English guidelines | INBO protocols</title>
<meta name="description" content="English guidelines | INBO protocols">
<meta name="generator" content="bookdown and GitBook 2.6.7">
<meta property="og:title" content="English guidelines | INBO protocols" />
<meta property="og:type" content="book" />
<meta name="twitter:card" content="summary" />
<meta name="twitter:title" content="English guidelines | INBO protocols" />
<meta name="date" content="2023-01-19">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black">
<link rel="prev" href="nederlandstalige-richtlijnen.html"/>
<link rel="next" href="standard-field-protocols-sfp.html"/>
<script src="libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/fuse.js@6.4.6/dist/fuse.min.js"></script>
<link href="libs/gitbook-2.6.7/css/style.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-table.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-bookdown.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-highlight.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-search.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-fontsettings.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-clipboard.css" rel="stylesheet" />
<link href="libs/anchor-sections-1.1.0/anchor-sections.css" rel="stylesheet" />
<link href="libs/anchor-sections-1.1.0/anchor-sections-hash.css" rel="stylesheet" />
<script src="libs/anchor-sections-1.1.0/anchor-sections.js"></script>
<script src="libs/htmlwidgets-1.6.1/htmlwidgets.js"></script>
<script src="libs/jquery-migrate-3.1.0/jquery-migrate-3.1.0.min.js"></script>
<link href="libs/slick-1.8.1/slick/slick.css" rel="stylesheet" />
<link href="libs/slick-1.8.1/slick/slick-theme.css" rel="stylesheet" />
<script src="libs/slick-1.8.1/slick/slick.min.js"></script>
<script src="libs/css-resize-1.2.1/ResizeSensor.js"></script>
<script src="libs/css-resize-1.2.1/ElementQueries.js"></script>
<link href="libs/slickR-0.0.2/slick.css" rel="stylesheet" />
<link href="libs/slickR-0.0.2/slick-theme.css" rel="stylesheet" />
<script src="libs/slickR-0.0.2/slickR.js"></script>
<script src="libs/core-js-2.5.3/shim.min.js"></script>
<script src="libs/react-17.0.0/react.min.js"></script>
<script src="libs/react-17.0.0/react-dom.min.js"></script>
<script src="libs/reactwidget-1.0.0/react-tools.js"></script>
<link href="libs/reactable-0.4.3/reactable.css" rel="stylesheet" />
<script src="libs/reactable-binding-0.4.3/reactable.js"></script>
<link rel="stylesheet" href="css/inbo_rapport.css" type="text/css"/>
<link rel="stylesheet" href="css/inbo_rapport.css" type="text/css" />
</head>
<body>
<div class="book without-animation with-summary font-size-2 font-family-1" data-basepath=".">
<div class="book-summary">
<nav role="navigation">
<ul class="summary">
<li class="toc-logo"><a href="https://www.vlaanderen.be/inbo/home/"><img src="css/img/inbo-en.jpg"></a></li>
<li class="divider"></li>
<li class="chapter" data-level="" data-path="index.html"><a href="index.html"><i class="fa fa-check"></i>Welkom! / Welcome!</a></li>
<li class="chapter" data-level="" data-path="nederlandstalige-richtlijnen.html"><a href="nederlandstalige-richtlijnen.html"><i class="fa fa-check"></i>Nederlandstalige richtlijnen</a></li>
<li class="chapter" data-level="" data-path="english-guidelines.html"><a href="english-guidelines.html"><i class="fa fa-check"></i>English guidelines</a></li>
<li class="chapter" data-level="" data-path="standard-field-protocols-sfp.html"><a href="standard-field-protocols-sfp.html"><i class="fa fa-check"></i>Standard field protocols (sfp)</a></li>
<li class="chapter" data-level="" data-path="standard-instrument-protocols-sip.html"><a href="standard-instrument-protocols-sip.html"><i class="fa fa-check"></i>Standard instrument protocols (sip)</a></li>
<li class="chapter" data-level="" data-path="standard-analytical-protocols-sap.html"><a href="standard-analytical-protocols-sap.html"><i class="fa fa-check"></i>Standard analytical protocols (sap)</a></li>
<li class="chapter" data-level="" data-path="standard-operating-procedures-sop.html"><a href="standard-operating-procedures-sop.html"><i class="fa fa-check"></i>Standard operating procedures (sop)</a></li>
<li class="chapter" data-level="" data-path="project-specific-protocols-spp.html"><a href="project-specific-protocols-spp.html"><i class="fa fa-check"></i>Project-specific protocols (spp)</a></li>
<li class="chapter" data-level="" data-path="news.html"><a href="news.html"><i class="fa fa-check"></i>NEWS</a></li>
<li class="divider"></li>
<li class="cc"><a href="http://creativecommons.org/licenses/by/4.0/"><img src="css/img/cc-by.png"></a></li>
</ul>
</nav>
</div>
<div class="book-body">
<div class="body-inner">
<div class="book-header" role="navigation">
<h1>
<i class="fa fa-circle-o-notch fa-spin"></i><a href="./">INBO protocols</a>
</h1>
</div>
<div class="page-wrapper" tabindex="-1" role="main">
<div class="page-inner">
<section class="normal" id="section-">
<div id="english-guidelines" class="section level1 hasAnchor">
<h1>English guidelines<a href="english-guidelines.html#english-guidelines" class="anchor-section" aria-label="Anchor link to header"></a></h1>
<div id="welcome" class="section level3 hasAnchor">
<h3>Welcome!<a href="english-guidelines.html#welcome" class="anchor-section" aria-label="Anchor link to header"></a></h3>
<p>Protocols increase the quality of fieldwork and labwork and thus the quality of scientific research, which must be transparent, traceable and applicable.
They help make field- and labwork more harmonized and more repeatable, reproducible and comparable.
Standardization is also interesting for the Institute for Nature and Forest
Research (INBO) from an efficiency point of view.</p>
<p>This site serves as a repository for the latest versions of approved, publicly available protocols used at the INBO.
Each protocol can either be accessed online through this website (html version) or a PDF version can be downloaded.
On the left side you will find the navigation to the different sections.
In the NEWS section you can find which (versions of) protocols were added when.</p>
<p>This website contains the published protocols.
The management, maintenance, approval and revision of the source files underlying these published protocols is done in the <a href="https://github.com/inbo/protocolsource">inbo/protocolsource</a> GitHub repository.</p>
</div>
<div id="five-types-of-protocols" class="section level3 hasAnchor">
<h3>Five types of protocols<a href="english-guidelines.html#five-types-of-protocols" class="anchor-section" aria-label="Anchor link to header"></a></h3>
<p>We distinguish five types of standard protocols.
The first type is the <strong>standard field protocol</strong> (<code>sfp</code>) which is used to explain the steps that are needed in the field by a field worker to execute a specific field activity.
The second type is the <strong>standard instrument protocol</strong> (<code>sip</code>) which explains the use and maintenance of instruments.
The third type is the <strong>standard analytical protocol</strong> (<code>sap</code>) which is used in the laboratory or the field to explain a particular lab or field-analytical procedure involving physical or chemical measurements.
The fourth type stands for <strong>standard operating procedure</strong> (<code>sop</code>) and is for everything that does not fit in one of the previous types.</p>
<p>The fifth type is a category reserved for <strong>project-specific protocols</strong> (<code>spp</code>).
The latter is more of a convenience to aid quick development and employment of protocols within a project context.
Within the scope of a project, it might sometimes be necessary to re-use a <code>sfp</code> type protocol but with slightly different settings which are specific to the project.
This can be done by including a published <code>sfp</code> protocol as an <code>spp</code> subprotocol where the deviations from the default settings are given.</p>
</div>
<div id="protocol-identification" class="section level3 hasAnchor">
<h3>Protocol identification<a href="english-guidelines.html#protocol-identification" class="anchor-section" aria-label="Anchor link to header"></a></h3>
<p>The previously explained typology of protocols is further detailed in a so-called protocol-code.
A <strong>protocol-code</strong> consists of a prefix referring to the <em>protocol-type</em> (three characters), a <em>protocol-number</em> (three digits) and a <em>language tag</em> (two characters), all separated by a hyphen.</p>
<table>
<thead>
<tr class="header">
<th align="left">type</th>
<th align="left">theme</th>
<th align="left">theme_number</th>
<th align="left">protocol-code</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left">field</td>
<td align="left">generic</td>
<td align="left">0</td>
<td align="left">sfp-0##-en</td>
</tr>
<tr class="even">
<td align="left">field</td>
<td align="left">water</td>
<td align="left">1</td>
<td align="left">sfp-1##-en</td>
</tr>
<tr class="odd">
<td align="left">field</td>
<td align="left">air</td>
<td align="left">2</td>
<td align="left">sfp-2##-en</td>
</tr>
<tr class="even">
<td align="left">field</td>
<td align="left">soil</td>
<td align="left">3</td>
<td align="left">sfp-3##-en</td>
</tr>
<tr class="odd">
<td align="left">field</td>
<td align="left">vegetation</td>
<td align="left">4</td>
<td align="left">sfp-4##-en</td>
</tr>
<tr class="even">
<td align="left">field</td>
<td align="left">species</td>
<td align="left">5</td>
<td align="left">sfp-5##-en</td>
</tr>
<tr class="odd">
<td align="left">instrument</td>
<td align="left"></td>
<td align="left"></td>
<td align="left">sip-###-en</td>
</tr>
<tr class="even">
<td align="left">operating</td>
<td align="left"></td>
<td align="left"></td>
<td align="left">sop-###-en</td>
</tr>
<tr class="odd">
<td align="left">analysis</td>
<td align="left"></td>
<td align="left"></td>
<td align="left">sap-###-en</td>
</tr>
<tr class="even">
<td align="left">project</td>
<td align="left"></td>
<td align="left"></td>
<td align="left">spp-###-en</td>
</tr>
</tbody>
</table>
<p>Field protocols are further subdivided into 5 themes, which indicates broadly which environmental or biological aspect is targeted by the protocol.
In case of thematic protocols, the first digit of the protocol-number corresponds with the theme-number.
The <code>##</code> indicates an incremental number.
For instance, the first field protocol for “theme water” will have protocol code <code>sfp-101-en</code>.
The <code>s*p-###</code> part of the protocol code can be thought of as a code that corresponds one-to-one with the title of the protocol (when ignoring language).</p>
<p>The final two characters identify the language the protocol is written in.
This can be either Dutch (<code>nl</code>) or English (<code>en</code>).
A same protocol but written in a different language, will have the same protocol code safe for the final two characters.</p>
<p>Each protocol thus has a unique protocol-code, but there can be multiple versions of a protocol.
To discriminate between different versions of protocol, we need a version number.
The <strong>version number</strong> that we use is of the form <code>YYYY.NN</code>.
<code>YYYY</code> indicates the year in which the version of the protocol was released.
The <code>NN</code> is a number that indicates the order of release within that year (starting with 01).
The version number will therefore uniquely identify a specific version of a specific protocol, which can be refered to without the need to refer to the protocol-code.
Here’s a fictive example:</p>
<ul>
<li>version <code>2022.01</code> (identifies a first version of <code>sfp-401-en</code>)</li>
<li>version <code>2022.02</code> (identifies a first version of <code>sfp-001-en</code>)</li>
<li>version <code>2022.03</code> (identifies a second version of <code>sfp-401-en</code>)</li>
</ul>
<p>The <a href="news.html">NEWS</a> page lists the version numbers (in descending chronological order) and identifies which protocols they belong to.
The website also has an overview table per protocol type, which lists all versions of protocols that belong to that type.
These tables can be filtered by protocol code.
This can be used to easily get an overview of all versions of a protocol.</p>
</div>
</div>
<p> </p>
<p><a rel="license" href="http://creativecommons.org/licenses/by/4.0/"><img alt="Creative Commons-Licentie" style="border-width:0" src="css/img/cc-by.png" class = "cc"/></a>
</section>
</div>
</div>
</div>
<a href="nederlandstalige-richtlijnen.html" class="navigation navigation-prev " aria-label="Previous page"><i class="fa fa-angle-left"></i></a>
<a href="standard-field-protocols-sfp.html" class="navigation navigation-next " aria-label="Next page"><i class="fa fa-angle-right"></i></a>
</div>
<script src="libs/gitbook-2.6.7/js/app.min.js"></script>
<script src="libs/gitbook-2.6.7/js/clipboard.min.js"></script>
<script src="libs/gitbook-2.6.7/js/plugin-search.js"></script>
<script src="libs/gitbook-2.6.7/js/plugin-sharing.js"></script>
<script src="libs/gitbook-2.6.7/js/plugin-fontsettings.js"></script>
<script src="libs/gitbook-2.6.7/js/plugin-bookdown.js"></script>
<script src="libs/gitbook-2.6.7/js/jquery.highlight.js"></script>
<script src="libs/gitbook-2.6.7/js/plugin-clipboard.js"></script>
<script>
gitbook.require(["gitbook"], function(gitbook) {
gitbook.start({
"sharing": {
"github": false,
"facebook": true,
"twitter": true,
"linkedin": false,
"weibo": false,
"instapaper": false,
"vk": false,
"whatsapp": false,
"all": ["facebook", "twitter", "linkedin", "weibo", "instapaper"]
},
"fontsettings": {
"theme": "white",
"family": "sans",
"size": 2
},
"edit": {
"link": null,
"text": null
},
"history": {
"link": null,
"text": null
},
"view": {
"link": null,
"text": null
},
"download": null,
"search": {
"engine": "fuse",
"options": null
},
"toc": {
"collapse": "subsection"
}
});
});
</script>
</body>
</html>