Skip to Content
Last modified by Robin Huisman on 2024/12/18 14:57
From version 42.1
edited by Robin Huisman
on 2024/04/05 15:41
Change comment: There is no comment for this version
To version 43.3
edited by Luca de Laat
on 2024/04/10 11:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.RobinHuisman
1 +XWiki.LucadeLaat
Content
... ... @@ -1,14 +1,14 @@
1 1  = Creating a Delivery file and binding them to a customer =
2 2  
3 -This chapter contains the information needed to understand the lab delivery file. A Lab delivery file only has to be updated when there are changes. Otherwise TerraIndex will always show the last imported file.
3 +This chapter contains the information needed to understand the lab delivery file. A Lab delivery file only has to be updated when there are changes. Otherwise, TerraIndex will always show the last imported file.
4 4  
5 5  {{warning}}
6 6  Latest version can be found here: [[https:~~/~~/www.sikb.nl/datastandaarden/sikb0101-bodembeheer>>url:https://www.sikb.nl/datastandaarden/sikb0101-bodembeheer]]
7 7  {{/warning}}
8 8  
9 -== What is a lab delivery file ==
9 +== What is a lab delivery file? ==
10 10  
11 -A lab delivery file contains the Customer code of the customer that will be sending the lab assignment. It also contains the analyses that can be requested from the a lab by the customer. A Lab delivery file needs to be custom for every user and needs to be a XML file
11 +A lab delivery file contains the Customer code of the customer that will be sending the lab assignment. It also contains the analyses that can be requested from the lab by the customer. A Lab delivery file needs to be custom for every user and needs to be a XML file. This file will be available for the customer to choose their options for requesting and ordering an analysis at the lab. It's the Menu-card of the Lab, the user can choose from.
12 12  
13 13  **Example files**:  [[attach:Labdeliveryfile.xml||rel="noopener noreferrer" target="_blank"]]
14 14  
... ... @@ -20,9 +20,13 @@
20 20  {{toc/}}
21 21  
22 22  
23 +~==> nle Add field Certification (screen 1 of labassignment)
24 +
23 23  == File structure ==
24 24  
25 25  In the image below the main structure of the XML file is shown. Every table is described in more detail later on in this chapter.
28 +
29 +~==> nle Dutch text in screenshot
26 26  [[image:1712158795900-531.png||height="604" width="391"]]
27 27  
28 28  (% class="table-hover" %)
... ... @@ -73,7 +73,7 @@
73 73  
74 74  “Category” does not need a lot of explanation. A category is a group defined by the lab where certain values in the “koppeltabel” can be grouped under. A category is determined by the lab and can be used in the “Links”.
75 75  
76 -In TerraIndex it will be showed as Header/Group:
80 +In TerraIndex, it will be shown as Header/Group:
77 77  [[image:1712162927138-349.png]]
78 78  
79 79  
... ... @@ -88,14 +88,14 @@
88 88  
89 89  == Structure explanation AnalysisLink and Analysis ==
90 90  
91 -This table contains all the analyses that a analyses package can contain. Be sure the “analysepakketcode” corresponds to a code in the table: “analysepakketten”. The analysecode is your own identification code for the analyses.
95 +This table contains all the analyses that an analysis package can contain. Be sure the “analysepakketcode” corresponds to a code in the table: “analysepakketten”. The analysecode is your own identification code for the analyses.
92 92  \\[[image:1712163145392-331.png]]
93 93  \\[[image:1712163459761-326.png||height="488" width="799"]]
94 94  
95 95  (% class="table-hover" %)
96 96  |(% colspan="1" rowspan="1" %)**Attribute name**|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)**Unit**
97 -|(% colspan="1" rowspan="1" %)**AnalysisSetId**|(% colspan="1" rowspan="1" %)The analyse set code that corresponds to a code in the “//AnalysisSets//”|(% colspan="1" rowspan="1" %)string
98 -|(% colspan="1" rowspan="1" %)**Analysis**|(% colspan="1" rowspan="1" %)A table containing ale the analyses that should be in this analysis set or package|(% colspan="1" rowspan="1" %)-
101 +|(% colspan="1" rowspan="1" %)**AnalysisSetId**|(% colspan="1" rowspan="1" %)The analysis set code that corresponds to a code in the “//AnalysisSets//”|(% colspan="1" rowspan="1" %)string
102 +|(% colspan="1" rowspan="1" %)**Analysis**|(% colspan="1" rowspan="1" %)A table containing all the analyses that should be in this analysis set or package|(% colspan="1" rowspan="1" %)-
99 99  
100 100  === __Analysis__ ===
101 101  
... ... @@ -108,7 +108,7 @@
108 108  
109 109  == Structure explanation Clients ==
110 110  
111 -A customer can have multiple “clients”. There always needs to be one “client” so that a lab assignment can be send. But for example when there is a price agreement for a certain project a new “Client” can be added. Or when a company has multiple offices every office can have its own “Client”.
115 +A customer can have multiple “clients”. There always needs to be one “client” so that a lab assignment can be sent. But for example, when there is a price agreement for a certain project, a new “Client” can be added. Or when a company has multiple offices, every office can have its own “Client”.
112 112  \\It will be shown in the interface of TerraIndex, and needs to be chosen before selecting analysis sets:
113 113  [[image:1712163957735-690.png]]
114 114  \\[[image:1712163986350-364.png||height="409" width="544"]]
... ... @@ -115,11 +115,11 @@
115 115  
116 116  |(% colspan="1" rowspan="1" %)**Attribute name**|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)**Unit**
117 117  |(% colspan="1" rowspan="1" %)**ClientId**|(% colspan="1" rowspan="1" %)The customer identification code(s) for the company or office|(% colspan="1" rowspan="1" %)string
118 -|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)The name\description of the customer code, as shown in the interface and will be invoiced.|(% colspan="1" rowspan="1" %)string
122 +|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)The name\description of the customer code, as shown in the interface, and will be invoiced.|(% colspan="1" rowspan="1" %)string
119 119  
120 120  == Structure explanation LabSampleMatrices ==
121 121  
122 -The “LabSampleMatrices” is an important sections of the XML. The “matrix” defines the main type of sample for the lab, and can contain multiple or prefined additional pretreatments of preservations. Without a sample type in this table a customer will not be able to send in lab assignments to the laboratory.
126 +The “LabSampleMatrices” is an important section of the XML. The “matrix” defines the main type of sample for the lab, and can contain multiple or predefined additional pretreatments of preservatives. Without a sample type in this table, a customer will not be able to send in lab assignments to the laboratory.
123 123  
124 124  It needs to be chosen in the interface of TerraIndex, before any analysis set can be chosen:
125 125  \\[[image:1712164314258-543.png]]
... ... @@ -129,15 +129,15 @@
129 129  
130 130  (% class="table-hover" %)
131 131  |(% colspan="1" rowspan="1" %)**Attribute name**|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)**unit**
132 -|(% colspan="1" rowspan="1" %)**CompartimentId**|(% colspan="1" rowspan="1" %)An SIKB ID that determins to which matrix the analyses belongs.
136 +|(% colspan="1" rowspan="1" %)**CompartimentId**|(% colspan="1" rowspan="1" %)An SIKB ID that determines to which matrix the analyses belongs.
133 133  Domaintable: [[Compartment/Matrix>>https://codes.sikb.nl/tablet/domain-table-details/6134f3bb-6048-431d-a130-01290d84172c]]|(% colspan="1" rowspan="1" %)int
134 134  |(% colspan="1" rowspan="1" %)//CompartimentCode//|(% colspan="1" rowspan="1" %)-not in use-|(% colspan="1" rowspan="1" %)
135 -|(% colspan="1" rowspan="1" %)**LabSampleMatrixCode**|(% colspan="1" rowspan="1" %)The laboratory matrix- or compartment-code of the lab, that will be also be send in the Labassignment to the lab|(% colspan="1" %)string
139 +|(% colspan="1" rowspan="1" %)**LabSampleMatrixCode**|(% colspan="1" rowspan="1" %)The laboratory matrix- or compartment-code of the lab, that will be also be sent in the Labassignment to the lab|(% colspan="1" %)string
136 136  |(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)The name\description of the matrix or compartment of the lab, as shown in the interface.|(% colspan="1" rowspan="1" %)string
137 137  
138 138  == Structure explanation SpecialAppointment ==
139 139  
140 -The “SpecialAppointment" contains the names of the price catalogus, the default quote or the special project quote. This way extra discount options are possible. It will be send in the labassignment to the lab.
144 +The “SpecialAppointment" contains the names of the price catalogs, the default quote or the special project quote. This way, extra discount options are possible. It will be sent in the labassignment to the lab.
141 141  
142 142  It needs to be chosen in the interface of TerraIndex, before any analysis set can be chosen, and empty means 'default quote':
143 143