Changes for page Lab delivery file - SIKB version 14
Last modified by Robin Huisman on 2024/12/18 14:57
From version 43.1
edited by Robin Huisman
on 2024/04/05 15:44
on 2024/04/05 15:44
Change comment:
There is no comment for this version
To version 44.1
edited by Robin Huisman
on 2024/04/10 15:33
on 2024/04/10 15:33
Change comment:
Uploaded new attachment "LabdeliveryFile_14.8.0_ENG_NL.xslt", version {1}
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,6 +1,6 @@ 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]] ... ... @@ -8,7 +8,7 @@ 8 8 9 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 alab 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 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.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 show edas 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 analys es 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 analys eset code that corresponds to a code in the “//AnalysisSets//”|(% colspan="1" rowspan="1" %)string98 -|(% colspan="1" rowspan="1" %)**Analysis**|(% colspan="1" rowspan="1" %)A table containing al ethe 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 sen d. 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 section sof 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 sen din the Labassignment to the lab|(% colspan="1" %)string139 +|(% 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 catalog us, the default quote or the special project quote. This way extra discount options are possible. It will be sendin 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 ... ... @@ -148,16 +148,16 @@ 148 148 149 149 (% class="table-hover" %) 150 150 |(% colspan="1" rowspan="1" %)**Attribute name**|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)**unit** 151 -|(% colspan="1" rowspan="1" %)**SpecialAppointmentId**|(% colspan="1" rowspan="1" %)An identifcation code from the lab that will be sen din the Labassignment to the lab.|(% colspan="1" rowspan="1" %)string155 +|(% colspan="1" rowspan="1" %)**SpecialAppointmentId**|(% colspan="1" rowspan="1" %)An identification code from the lab that will be sent in the Labassignment to the lab.|(% colspan="1" rowspan="1" %)string 152 152 |(% 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 153 153 |(% colspan="1" rowspan="1" %)//startdate//|(% colspan="1" rowspan="1" %)-not in use-|(% colspan="1" rowspan="1" %) 154 154 |(% colspan="1" rowspan="1" %)//finaldate//|(% colspan="1" rowspan="1" %)-not in use-|(% colspan="1" rowspan="1" %) 155 -|(% colspan="1" rowspan="1" %)**AppointmentTypeCode**|(% colspan="1" rowspan="1" %)The type of appointment, like: total pricelist, default quotation or special project agreement.159 +|(% colspan="1" rowspan="1" %)**AppointmentTypeCode**|(% colspan="1" rowspan="1" %)The type of appointment, like: total pricelist, default quotation or special project agreement. 156 156 Domaintable: [[PriceAgreement Type>>https://codes.sikb.nl/tablet/domain-table-details/60028a8a-f386-47bf-bf2e-f46af49b7b56]]|(% colspan="1" rowspan="1" %)int 157 157 158 158 == Structure explanation Links == 159 159 160 -The “Links” is one of the most important sections of the XML. The “Link” defines the combination of Analysespackages, cust erom/clientcode, categories and sampletype. Without a combination in this table a customer will not be able to send in lab assignments to the laboratory.164 +The “Links” is one of the most important sections of the XML. The “Link” defines the combination of Analysespackages, customer/clientcode, categories and sampletype. Without a combination in this table, a customer will not be able to send in lab assignments to the laboratory. 161 161 [[image:1712158823685-514.png||height="563" width="531"]] 162 162 163 163 ... ... @@ -173,7 +173,7 @@ 173 173 ))) 174 174 |(% colspan="1" %)Price|(% colspan="1" %)The optional Price indication for this combination of the Analysis|(% colspan="1" %)decimal 175 175 |(% colspan="1" %)CertificationId|(% colspan="1" %)The optional code that corresponds to the way of Sample and analysis handling as described in a certification. 176 -Some other labs have this arrage ned by the LabSampleMatrix types.180 +Some other labs have this arranged by the LabSampleMatrix types. 177 177 Domaintable: [[CertificeringsCode >>https://codes.sikb.nl/tablet/domain-table-details/df7ffd7c-192c-44f7-ae9f-0461d9266b30]]|(% colspan="1" %)int 178 178 |(% colspan="1" rowspan="1" %)**CategoryId**|(% colspan="1" rowspan="1" %)The code that corresponds to a category code in Categories table|(% colspan="1" rowspan="1" %)string 179 179 |(% colspan="1" rowspan="1" %)//Accredited//|(% colspan="1" rowspan="1" %)-not in use-|(% colspan="1" rowspan="1" %)bool ... ... @@ -180,7 +180,7 @@ 180 180 181 181 == Structure explanation Urgencies == 182 182 183 -This table contains a list with different delivery times for analyses results. For example 5 work days, overnight, within 48 hours and so on. The “UrgencyId” is a code given by the lab. 187 +This table contains a list with different delivery times for analyses results. For example, 5 work days, overnight, within 48 hours and so on. The “UrgencyId” is a code given by the lab. 184 184 185 185 [[image:1712324236054-772.png||height="372" width="511"]] 186 186 ... ... @@ -191,7 +191,7 @@ 191 191 192 192 == Structure explanation StoragePeriods == 193 193 194 -This table contains a list with different storage periods for the storage of the delivered Samples and it 's containers. For example '1 month', '5 weeks', 'customer agreement' and so on. The “StroragePeriodId” is a code given by the lab.198 +This table contains a list with different storage periods for the storage of the delivered Samples and its containers. For example, '1 month', '5 weeks', 'customer agreement' and so on. The “StoragePeriodId” is a code given by the lab. 195 195 196 196 [[image:1712324393233-546.png||height="359" width="519"]] 197 197
- LabdeliveryFile_14.8.0_ENG_NL.xslt
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.RobinHuisman - Size
-
... ... @@ -1,0 +1,1 @@ 1 +9.1 KB - Content
-
... ... @@ -1,0 +1,356 @@ 1 +<?xml version="1.0" encoding="UTF-8"?> 2 +<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xpath-default-namespace="http://www.element-examples.org" xmlns="http://www.element-examples.org" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 3 + 4 +<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/> 5 + 6 + <!-- Kopier alle nodes --> 7 + <xsl:template match="node()"> 8 + <xsl:copy> 9 + <xsl:apply-templates select="@*|node()"/> 10 + </xsl:copy> 11 + </xsl:template> 12 + 13 + <!-- Kopier de text van de nodes en de attributen--> 14 + <xsl:template match="text()"> 15 + <xsl:value-of select="."/> 16 +</xsl:template> 17 + 18 + 19 +<!-- Vervang de attributen--> 20 +<xsl:template match="LabDelivery/@version"> 21 + <xsl:attribute namespace="{namespace-uri()}" name="versie" ><xsl:value-of select="."/></xsl:attribute> 22 + </xsl:template> 23 + 24 +<xsl:template match="LabDelivery/@versionDeliveryData"> 25 + <xsl:attribute namespace="{namespace-uri()}" name="kenmerk" ><xsl:value-of select="."/></xsl:attribute> 26 + </xsl:template> 27 + 28 +<xsl:template match="LabDelivery/@laboratory"> 29 + <xsl:attribute namespace="{namespace-uri()}" name="laboratorium" ><xsl:value-of select="."/></xsl:attribute> 30 + </xsl:template> 31 + 32 +<xsl:template match="LabDelivery/@language"> 33 + <xsl:attribute namespace="{namespace-uri()}" name="taal" ><xsl:value-of select="."/></xsl:attribute> 34 + </xsl:template> 35 + 36 + 37 + <!-- vervang LabDelivery --> 38 +<xsl:template match="LabDelivery"> 39 + <labaanlevering> 40 + <xsl:apply-templates select="@*|node()"/> 41 + </labaanlevering> 42 + </xsl:template> 43 + 44 +<xsl:template match="Links"> 45 + <koppeltabel> 46 + <xsl:apply-templates select="@*|node()"/> 47 + </koppeltabel> 48 + </xsl:template> 49 + 50 + <xsl:template match="AnalysisSets"> 51 + <analysepakketten> 52 + <xsl:apply-templates select="@*|node()"/> 53 + </analysepakketten> 54 + </xsl:template> 55 + 56 + <xsl:template match="Categories"> 57 + <categorieen> 58 + <xsl:apply-templates select="@*|node()"/> 59 + </categorieen> 60 + </xsl:template> 61 + 62 + <xsl:template match="AnalysisLinks"> 63 + <analysetabel> 64 + <xsl:apply-templates select="@*|node()"/> 65 + </analysetabel> 66 + </xsl:template> 67 + 68 + <xsl:template match="Clients"> 69 + <debiteurtabel> 70 + <xsl:apply-templates select="@*|node()"/> 71 + </debiteurtabel> 72 + </xsl:template> 73 + 74 + <xsl:template match="LabSampleMatrices"> 75 + <labmonstersoorttabel> 76 + <xsl:apply-templates select="@*|node()"/> 77 + </labmonstersoorttabel> 78 + </xsl:template> 79 + 80 + <xsl:template match="SpecialAppointments"> 81 + <afspraaktabel> 82 + <xsl:apply-templates select="@*|node()"/> 83 + </afspraaktabel> 84 + </xsl:template> 85 + 86 + <xsl:template match="Urgencies"> 87 + <urgentietabel> 88 + <xsl:apply-templates select="@*|node()"/> 89 + </urgentietabel> 90 + </xsl:template> 91 + 92 + <xsl:template match="StorePeriods"> 93 + <bewaarduurtabel> 94 + <xsl:apply-templates select="@*|node()"/> 95 + </bewaarduurtabel> 96 + </xsl:template> 97 + 98 + <xsl:template match="Reports"> 99 + <rapportagetabel> 100 + <xsl:apply-templates select="@*|node()"/> 101 + </rapportagetabel> 102 + </xsl:template> 103 + 104 + <xsl:template match="FractionLinks"> 105 + <fractietabel> 106 + <xsl:apply-templates select="@*|node()"/> 107 + </fractietabel> 108 + </xsl:template> 109 + 110 + <xsl:template match="Link"> 111 + <koppeling> 112 + <xsl:apply-templates select="@*|node()"/> 113 + </koppeling> 114 + </xsl:template> 115 + 116 + <xsl:template match="AnalysisSetId"> 117 + <analysepakketcode> 118 + <xsl:apply-templates select="@*|node()"/> 119 + </analysepakketcode> 120 + </xsl:template> 121 + 122 + <xsl:template match="ClientId"> 123 + <klantcode> 124 + <xsl:apply-templates select="@*|node()"/> 125 + </klantcode> 126 + </xsl:template> 127 + 128 + <xsl:template match="LabSampleMatrix"> 129 + <labmonstersoort> 130 + <xsl:apply-templates select="@*|node()"/> 131 + </labmonstersoort> 132 + </xsl:template> 133 + 134 + <xsl:template match="CompartimentId"> 135 + <compartimentid> 136 + <xsl:apply-templates select="@*|node()"/> 137 + </compartimentid> 138 + </xsl:template> 139 + <xsl:template match="CompartimentCode"> 140 + <compartimentcode> 141 + <xsl:apply-templates select="@*|node()"/> 142 + </compartimentcode> 143 + </xsl:template> 144 + <xsl:template match="LabSampleMatrixCode"> 145 + <labmonstersoortcode> 146 + <xsl:apply-templates select="@*|node()"/> 147 + </labmonstersoortcode> 148 + </xsl:template> 149 + <!--Omschrijving wordt al gedaan --> 150 + 151 + <xsl:template match="AppointmentTypeCode"> 152 + <afspraakCode> 153 + <xsl:apply-templates select="@*|node()"/> 154 + </afspraakCode> 155 + </xsl:template> 156 + 157 + <xsl:template match="SpecialAppointmentId"> 158 + <afspraaknummer> 159 + <xsl:apply-templates select="@*|node()"/> 160 + </afspraaknummer> 161 + </xsl:template> 162 + 163 + <xsl:template match="SampleKind"> 164 + <monstersoort> 165 + <xsl:apply-templates select="@*|node()"/> 166 + </monstersoort> 167 + </xsl:template> 168 + 169 + <xsl:template match="Price"> 170 + <prijs> 171 + <xsl:apply-templates select="@*|node()"/> 172 + </prijs> 173 + </xsl:template> 174 + 175 + <xsl:template match="CertificationId"> 176 + <certificering> 177 + <xsl:apply-templates select="@*|node()"/> 178 + </certificering> 179 + </xsl:template> 180 + 181 + <xsl:template match="AnalysisSet"> 182 + <analysepakket> 183 + <xsl:apply-templates select="@*|node()"/> 184 + </analysepakket> 185 + </xsl:template> 186 + 187 + <!-- AnalysisSetId Deze kunnen we overslaan, wordt al gedaan als goed is --> 188 + 189 + <xsl:template match="Description"> 190 + <omschrijving> 191 + <xsl:apply-templates select="@*|node()"/> 192 + </omschrijving> 193 + </xsl:template> 194 + 195 + <xsl:template match="CategoryId"> 196 + <categoriecode> 197 + <xsl:apply-templates select="@*|node()"/> 198 + </categoriecode> 199 + </xsl:template> 200 + 201 + <xsl:template match="Sequence"> 202 + <volgorde> 203 + <xsl:apply-templates select="@*|node()"/> 204 + </volgorde> 205 + </xsl:template> 206 + 207 + <xsl:template match="MinimalDeliveryTime"> 208 + <minlevertermijn> 209 + <xsl:apply-templates select="@*|node()"/> 210 + </minlevertermijn> 211 + </xsl:template> 212 + 213 + <xsl:template match="Category"> 214 + <categorie> 215 + <xsl:apply-templates select="@*|node()"/> 216 + </categorie> 217 + </xsl:template> 218 + 219 +<!-- CategoryId kunnen we overslaan, is al gedaan--> 220 + 221 +<!-- Description kunnen we overslaan, is al gedaan--> 222 + 223 +<!-- Sequence kunnen we overslaan, is al gedaan--> 224 + 225 + <xsl:template match="AnalysisLink"> 226 + <pakket> 227 + <xsl:apply-templates select="@*|node()"/> 228 + </pakket> 229 + </xsl:template> 230 + 231 + <!-- AnalysisSetId kunnen we overslaan, is al gedaan --> 232 + 233 + <xsl:template match="Analysis"> 234 + <analysepakketcode> 235 + <xsl:apply-templates select="@*|node()"/> 236 + </analysepakketcode> 237 + </xsl:template> 238 + 239 + <xsl:template match="AnalysisId"> 240 + <analysecode> 241 + <xsl:apply-templates select="@*|node()"/> 242 + </analysecode> 243 + </xsl:template> 244 + 245 +<!--Desciption kunnen we overslaan, wordt al gedaan --> 246 + 247 +<!--MinimalDeliveryTime kunnen we overslaan, wordt al gedaan --> 248 + 249 + <xsl:template match="Client"> 250 + <debiteur> 251 + <xsl:apply-templates select="@*|node()"/> 252 + </debiteur> 253 + </xsl:template> 254 + 255 + <!--ClientId kunnen we overslaan --> 256 + 257 + <!-- Description kunnen we overslaan --> 258 + 259 + <xsl:template match="SpecialAppointment"> 260 + <afspraak> 261 + <xsl:apply-templates select="@*|node()"/> 262 + </afspraak> 263 + </xsl:template> 264 + 265 + <!-- SpecialAppointmentId kunnen we overslaan --> 266 + 267 + <!-- Description kunnen we overslaan --> 268 + 269 + <xsl:template match="startdate"> 270 + <begindatum> 271 + <xsl:apply-templates select="@*|node()"/> 272 + </begindatum> 273 + </xsl:template> 274 + 275 + <xsl:template match="finaldate"> 276 + <einddatum> 277 + <xsl:apply-templates select="@*|node()"/> 278 + </einddatum> 279 + </xsl:template> 280 + 281 + <xsl:template match="Startdate"> 282 + <begindatum> 283 + <xsl:apply-templates select="@*|node()"/> 284 + </begindatum> 285 + </xsl:template> 286 + 287 + <xsl:template match="Finaldate"> 288 + <einddatum> 289 + <xsl:apply-templates select="@*|node()"/> 290 + </einddatum> 291 + </xsl:template> 292 + 293 + <xsl:template match="Urgency"> 294 + <urgentie> 295 + <xsl:apply-templates select="@*|node()"/> 296 + </urgentie> 297 + </xsl:template> 298 + 299 + <xsl:template match="UrgencyId"> 300 + <urgentiecode> 301 + <xsl:apply-templates select="@*|node()"/> 302 + </urgentiecode> 303 + </xsl:template> 304 + 305 + <!-- Description wordt al gedaan--> 306 + 307 + <xsl:template match="StorePeriod"> 308 + <bewaarduur> 309 + <xsl:apply-templates select="@*|node()"/> 310 + </bewaarduur> 311 + </xsl:template> 312 + 313 + <!--StorePeriodId kunnen we overslaan --> 314 + 315 + <!--Description kunnen we overslaan --> 316 + 317 + <xsl:template match="Report"> 318 + <rapportage> 319 + <xsl:apply-templates select="@*|node()"/> 320 + </rapportage> 321 + </xsl:template> 322 + 323 + <xsl:template match="ReportId"> 324 + <rapportcode> 325 + <xsl:apply-templates select="@*|node()"/> 326 + </rapportcode> 327 + </xsl:template> 328 + 329 +<!--Description kunnen we overslaan --> 330 + 331 + <xsl:template match="FractionLink"> 332 + <fracties> 333 + <xsl:apply-templates select="@*|node()"/> 334 + </fracties> 335 + </xsl:template> 336 + 337 + <!--AnalysisSetId kunnen we overslaan --> 338 + 339 + <xsl:template match="Fraction"> 340 + <fractie> 341 + <xsl:apply-templates select="@*|node()"/> 342 + </fractie> 343 + </xsl:template> 344 + 345 + <xsl:template match="FractionId"> 346 + <fractiecode> 347 + <xsl:apply-templates select="@*|node()"/> 348 + </fractiecode> 349 + </xsl:template> 350 + 351 + <!-- SampleKind is al vertaald --> 352 + 353 + <!--Description is al vertaald --> 354 + 355 +</xsl:stylesheet> 356 +