dcm4che/dcm4chee-arc-light#4450 : Improve and normalize Rule Priority…

… descriptions in applicable language schema json file
dcm4che · Apr 12, 2024 · a936658 · a936658
1 parent 31975de
commit a936658
Show file tree

Hide file tree

Showing 60 changed files with 60 additions and 60 deletions.
diff --git a/src/props/de/archiveAttributeCoercion.props b/src/props/de/archiveAttributeCoercion.props
@@ -1,6 +1,6 @@
 archiveAttributeCoercion:Archive Attribute Coercion - Legacy|Archive Attribute Coercion of received/sent DIMSE
 archiveAttributeCoercion.cn:Name|Arbitrary/Meaningful name of the Archive Attribute Coercion
-archiveAttributeCoercion.dcmRulePriority:Rule Priority|Rule Priority. Higher priority rule applied.
+archiveAttributeCoercion.dcmRulePriority:Rule Priority|If the condition of several archive attribute coercion (legacy) matches for a received image, higher priority coercion is applied. If there are several matching coercions with equal priority, it is undefined which coercion gets applied.
 archiveAttributeCoercion.dcmDIMSE:DIMSE|DICOM Message Element on which this Attribute Coercion shall be applied. Also <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/Legacy-Archive-Attribute-Coercion---Application-of-multiple-coercions-using-one-coercion-rule#dimse" target="_blank">applicable if the requests are received over web.</a>
 archiveAttributeCoercion.dicomTransferRole:DICOM Transfer Role|DICOM Transfer Role of peer DICOM AE.
 archiveAttributeCoercion.dcmSOPClass:SOP Class UID|UID of SOP Class for which this Attribute Coercion shall be applied. Apply on any if absent.

diff --git a/src/props/de/archiveAttributeCoercion2.props b/src/props/de/archiveAttributeCoercion2.props
@@ -4,7 +4,7 @@ archiveAttributeCoercion2.dicomDescription:Attribute Coercion Description|Uncons
 archiveAttributeCoercion2.dcmURI:Attribute Coercion URI|Identifies Attribute Coercion by Uniform Resource Identifier. Refer values you can set for <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/New-Archive-Attribute-Coercion---Application-of-multiple-coercions-for-one-use-case-using-multiple-rules#attribute-coercion-uri" target="_blank">Attribute Coercion URI</a> field depending on the coercion type.
 archiveAttributeCoercion2.dcmCoercionSufficient:Attribute Coercion Sufficient|Do not apply other matching Attribute Coercions of lesser priority, if this Attribute Coercion was applied effectively.
 archiveAttributeCoercion2.dcmCoercionOnFailure:Attribute Coercion on Failure|Behavior on failure applying this Attribute Coercion. Refer <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/New-Archive-Attribute-Coercion---Application-of-multiple-coercions-for-one-use-case-using-multiple-rules#attribute-coercion-on-failure" target="_blank">Attribute Coercion on Failure meanings.</a>
-archiveAttributeCoercion2.dcmRulePriority:Attribute Coercion Priority|Rule Priority. Higher priority rule takes precedence.
+archiveAttributeCoercion2.dcmRulePriority:Attribute Coercion Priority|If the condition of several archive attribute coercion (new) matches for a received image, higher priority coercion takes precedence. If there are several matching coercions with equal priority, it is undefined which coercion takes precedence.
 archiveAttributeCoercion2.dcmDIMSE:DIMSE|DICOM Message Element on which this Attribute Coercion shall be applied. Also <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/New-Archive-Attribute-Coercion---Application-of-multiple-coercions-for-one-use-case-using-multiple-rules#dimse" target="_blank">applicable if the requests are received over web.</a>
 archiveAttributeCoercion2.dicomTransferRole:DICOM Transfer Role|DICOM Transfer Role of peer DICOM AE.
 archiveAttributeCoercion2.dcmSOPClass:SOP Class UID|UID of SOP Class for which this Attribute Coercion shall be applied. Apply on any if absent.

diff --git a/src/props/de/hl7OrderScheduledStation.props b/src/props/de/hl7OrderScheduledStation.props
@@ -1,5 +1,5 @@
 hl7OrderScheduledStation:Scheduled Station for HL7 Order|Scheduled Station selected on MWL HL7 Order Feed
 hl7OrderScheduledStation.cn:Name|Arbitrary/Meaningful name for the Scheduled Station Order Mapping
 hl7OrderScheduledStation.hl7OrderScheduledStationDeviceName:Scheduled Station Device Name|Device name of Scheduled Station used for HL7 Order Messages.
-hl7OrderScheduledStation.dcmRulePriority:Mapping Priority|Mapping Priority.
+hl7OrderScheduledStation.dcmRulePriority:Mapping Priority|If the condition of several Scheduled Station for HL7 Order rules match for a received HL7 message and each have different priority, Scheduled Station Device Name of highest priority is applied. If the condition of several Scheduled Station for HL7 Order rules match for a received HL7 message and each have equal priority, Scheduled Station Device Name of each is applied.
 hl7OrderScheduledStation.dcmProperty:Conditions|Conditions in format {SEG}-{Seq#}[.{Comp#}[.{SubComp#}]][!]={regEx}. Examples: MSH-4=FORWARD or MSH-9=ADT\\^A28\\^ADT_A05 or PID-3[.3]=PIDIssuer or PID-3[.3[.2]]=PIDIssuerUniversalEntityIDType
diff --git a/src/props/de/hl7StudyRetentionPolicy.props b/src/props/de/hl7StudyRetentionPolicy.props
@@ -3,7 +3,7 @@ hl7StudyRetentionPolicy.cn:Name|Arbitrary/Meaningful name of the HL7 Study Reten
 hl7StudyRetentionPolicy.dicomAETitle:Application Entity (AE) title|Application Entity (AE) title
 hl7StudyRetentionPolicy.dcmRetentionPeriod:Minimal Study Retention Period|Minimal Study Retention Period in ISO-8601 period format PnYnMnD or PnW. Ineffective if 'Maximal Study Retention Period' is also set.
 hl7StudyRetentionPolicy.dcmMaxRetentionPeriod:Maximal Study Retention Period|Maximal Study Retention Period in ISO-8601 period format PnYnMnD or PnW
-hl7StudyRetentionPolicy.dcmRulePriority:Rule Priority|Rule Priority.
+hl7StudyRetentionPolicy.dcmRulePriority:Rule Priority|If the condition of several HL7 Study Retention policies match for a received HL7 message, higher priority policy is applied. If there are several matching policies with equal priority, it is undefined which policy gets applied.
 hl7StudyRetentionPolicy.dcmProperty:Conditions|Conditions in format {SEG}-{Seq#}[.{Comp#}[.{SubComp#}]][!]={regEx}. Examples: MSH-4=FORWARD or MSH-9=ADT\\^A28\\^ADT_A05 or PID-3[.3]=PIDIssuer or PID-3[.3[.2]]=PIDIssuerUniversalEntityIDType
 hl7StudyRetentionPolicy.dcmStartRetentionPeriodOnStudyDate:Start Retention Period on Study Date|Indicates if retention period should be started on individual Study Dates instead on receive of the HL7 message triggering this rule.
 hl7StudyRetentionPolicy.dcmExporterID:Export expired Study|Export expired Study/Series using the specified Exporter

diff --git a/src/props/de/storeAccessControlIDRule.props b/src/props/de/storeAccessControlIDRule.props
@@ -1,5 +1,5 @@
 storeAccessControlIDRule:Store Access Control ID Rule|Store Access Control ID Rule
 storeAccessControlIDRule.cn:Name|Arbitrary/Meaningful name of the Store Access Control ID Rule
 storeAccessControlIDRule.dcmStoreAccessControlID:Store Access Control ID|Access Control ID assigned to Studies which attributes match all conditions
-storeAccessControlIDRule.dcmRulePriority:Rule Priority|Rule Priority.
+storeAccessControlIDRule.dcmRulePriority:Rule Priority|If the condition of several Store Access Control ID rules match for a received image, higher priority rule is applied. If there are several matching rules with equal priority, it is undefined which rule gets applied.
 storeAccessControlIDRule.dcmProperty:Conditions|Conditions in format {key}[!]={value}. Refer <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/Conditions" target="_blank">applicability, format and some examples.</a>
diff --git a/src/props/de/studyRetentionPolicy.props b/src/props/de/studyRetentionPolicy.props
@@ -1,7 +1,7 @@
 studyRetentionPolicy:Study Retention Policy|Study Retention Policy
 studyRetentionPolicy.cn:Name|Arbitrary/Meaningful name of the Study Retention Policy
 studyRetentionPolicy.dcmRetentionPeriod:Study Retention Period|Study Retention Period in ISO-8601 period format PnYnMnD or PnW
-studyRetentionPolicy.dcmRulePriority:Rule Priority|Rule Priority.
+studyRetentionPolicy.dcmRulePriority:Rule Priority|If the condition of several Study Retention policies match for a received image, higher priority policy is applied. If there are several matching policies with equal priority, it is undefined which policy gets applied.
 studyRetentionPolicy.dcmProperty:Conditions|Conditions in format {key}[!]={value}. Refer <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/Conditions" target="_blank">applicability, format and some examples.</a>
 studyRetentionPolicy.dcmExpireSeriesIndividually:Expire Series Individually|Indicates if series should be expired individually or not.
 studyRetentionPolicy.dcmStartRetentionPeriodOnStudyDate:Start Retention Period on Study Date|Indicates if retention period should be started on Study Date instead on receive of an object of the Study

diff --git a/src/props/en/archiveAttributeCoercion.props b/src/props/en/archiveAttributeCoercion.props
@@ -1,6 +1,6 @@
 archiveAttributeCoercion:Archive Attribute Coercion - Legacy|Archive Attribute Coercion of received/sent DIMSE
 archiveAttributeCoercion.cn:Name|Arbitrary/Meaningful name of the Archive Attribute Coercion
-archiveAttributeCoercion.dcmRulePriority:Rule Priority|Rule Priority. Higher priority rule applied.
+archiveAttributeCoercion.dcmRulePriority:Rule Priority|If the condition of several archive attribute coercion (legacy) matches for a received image, higher priority coercion is applied. If there are several matching coercions with equal priority, it is undefined which coercion gets applied.
 archiveAttributeCoercion.dcmDIMSE:DIMSE|DICOM Message Element on which this Attribute Coercion shall be applied. Also <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/Legacy-Archive-Attribute-Coercion---Application-of-multiple-coercions-using-one-coercion-rule#dimse" target="_blank">applicable if the requests are received over web.</a>
 archiveAttributeCoercion.dicomTransferRole:DICOM Transfer Role|DICOM Transfer Role of peer DICOM AE.
 archiveAttributeCoercion.dcmSOPClass:SOP Class UID|UID of SOP Class for which this Attribute Coercion shall be applied. Apply on any if absent.

diff --git a/src/props/en/archiveAttributeCoercion2.props b/src/props/en/archiveAttributeCoercion2.props
@@ -4,7 +4,7 @@ archiveAttributeCoercion2.dicomDescription:Attribute Coercion Description|Uncons
 archiveAttributeCoercion2.dcmURI:Attribute Coercion URI|Identifies Attribute Coercion by Uniform Resource Identifier. Refer values you can set for <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/New-Archive-Attribute-Coercion---Application-of-multiple-coercions-for-one-use-case-using-multiple-rules#attribute-coercion-uri" target="_blank">Attribute Coercion URI</a> field depending on the coercion type.
 archiveAttributeCoercion2.dcmCoercionSufficient:Attribute Coercion Sufficient|Do not apply other matching Attribute Coercions of lesser priority, if this Attribute Coercion was applied effectively.
 archiveAttributeCoercion2.dcmCoercionOnFailure:Attribute Coercion on Failure|Behavior on failure applying this Attribute Coercion. Refer <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/New-Archive-Attribute-Coercion---Application-of-multiple-coercions-for-one-use-case-using-multiple-rules#attribute-coercion-on-failure" target="_blank">Attribute Coercion on Failure meanings.</a>
-archiveAttributeCoercion2.dcmRulePriority:Attribute Coercion Priority|Rule Priority. Higher priority rule takes precedence.
+archiveAttributeCoercion2.dcmRulePriority:Attribute Coercion Priority|If the condition of several archive attribute coercion (new) matches for a received image, higher priority coercion takes precedence. If there are several matching coercions with equal priority, it is undefined which coercion takes precedence.
 archiveAttributeCoercion2.dcmDIMSE:DIMSE|DICOM Message Element on which this Attribute Coercion shall be applied. Also <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/New-Archive-Attribute-Coercion---Application-of-multiple-coercions-for-one-use-case-using-multiple-rules#dimse" target="_blank">applicable if the requests are received over web.</a>
 archiveAttributeCoercion2.dicomTransferRole:DICOM Transfer Role|DICOM Transfer Role of peer DICOM AE.
 archiveAttributeCoercion2.dcmSOPClass:SOP Class UID|UID of SOP Class for which this Attribute Coercion shall be applied. Apply on any if absent.

diff --git a/src/props/en/hl7OrderScheduledStation.props b/src/props/en/hl7OrderScheduledStation.props
@@ -1,5 +1,5 @@
 hl7OrderScheduledStation:Scheduled Station for HL7 Order|Scheduled Station selected on MWL HL7 Order Feed
 hl7OrderScheduledStation.cn:Name|Arbitrary/Meaningful name for the Scheduled Station Order Mapping
 hl7OrderScheduledStation.hl7OrderScheduledStationDeviceName:Scheduled Station Device Name|Device name of Scheduled Station used for HL7 Order Messages.
-hl7OrderScheduledStation.dcmRulePriority:Mapping Priority|Mapping Priority.
+hl7OrderScheduledStation.dcmRulePriority:Mapping Priority|If the condition of several Scheduled Station for HL7 Order rules match for a received HL7 message and each have different priority, Scheduled Station Device Name of highest priority is applied. If the condition of several Scheduled Station for HL7 Order rules match for a received HL7 message and each have equal priority, Scheduled Station Device Name of each is applied.
 hl7OrderScheduledStation.dcmProperty:Conditions|Conditions in format {SEG}-{Seq#}[.{Comp#}[.{SubComp#}]][!]={regEx}. Examples: MSH-4=FORWARD or MSH-9=ADT\\^A28\\^ADT_A05 or PID-3[.3]=PIDIssuer or PID-3[.3[.2]]=PIDIssuerUniversalEntityIDType
diff --git a/src/props/en/hl7StudyRetentionPolicy.props b/src/props/en/hl7StudyRetentionPolicy.props
@@ -3,7 +3,7 @@ hl7StudyRetentionPolicy.cn:Name|Arbitrary/Meaningful name of the HL7 Study Reten
 hl7StudyRetentionPolicy.dicomAETitle:Application Entity (AE) title|Application Entity (AE) title
 hl7StudyRetentionPolicy.dcmRetentionPeriod:Minimal Study Retention Period|Minimal Study Retention Period in ISO-8601 period format PnYnMnD or PnW. Ineffective if 'Maximal Study Retention Period' is also set.
 hl7StudyRetentionPolicy.dcmMaxRetentionPeriod:Maximal Study Retention Period|Maximal Study Retention Period in ISO-8601 period format PnYnMnD or PnW
-hl7StudyRetentionPolicy.dcmRulePriority:Rule Priority|Rule Priority.
+hl7StudyRetentionPolicy.dcmRulePriority:Rule Priority|If the condition of several HL7 Study Retention policies match for a received HL7 message, higher priority policy is applied. If there are several matching policies with equal priority, it is undefined which policy gets applied.
 hl7StudyRetentionPolicy.dcmProperty:Conditions|Conditions in format {SEG}-{Seq#}[.{Comp#}[.{SubComp#}]][!]={regEx}. Examples: MSH-4=FORWARD or MSH-9=ADT\\^A28\\^ADT_A05 or PID-3[.3]=PIDIssuer or PID-3[.3[.2]]=PIDIssuerUniversalEntityIDType
 hl7StudyRetentionPolicy.dcmStartRetentionPeriodOnStudyDate:Start Retention Period on Study Date|Indicates if retention period should be started on individual Study Dates instead on receive of the HL7 message triggering this rule.
 hl7StudyRetentionPolicy.dcmExporterID:Export expired Study|Export expired Study/Series using the specified Exporter

diff --git a/src/props/en/storeAccessControlIDRule.props b/src/props/en/storeAccessControlIDRule.props
@@ -1,5 +1,5 @@
 storeAccessControlIDRule:Store Access Control ID Rule|Store Access Control ID Rule
 storeAccessControlIDRule.cn:Name|Arbitrary/Meaningful name of the Store Access Control ID Rule
 storeAccessControlIDRule.dcmStoreAccessControlID:Store Access Control ID|Access Control ID assigned to Studies which attributes match all conditions
-storeAccessControlIDRule.dcmRulePriority:Rule Priority|Rule Priority.
+storeAccessControlIDRule.dcmRulePriority:Rule Priority|If the condition of several Store Access Control ID rules match for a received image, higher priority rule is applied. If there are several matching rules with equal priority, it is undefined which rule gets applied.
 storeAccessControlIDRule.dcmProperty:Conditions|Conditions in format {key}[!]={value}. Refer <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/Conditions" target="_blank">applicability, format and some examples.</a>
diff --git a/src/props/en/studyRetentionPolicy.props b/src/props/en/studyRetentionPolicy.props
@@ -1,7 +1,7 @@
 studyRetentionPolicy:Study Retention Policy|Study Retention Policy
 studyRetentionPolicy.cn:Name|Arbitrary/Meaningful name of the Study Retention Policy
 studyRetentionPolicy.dcmRetentionPeriod:Study Retention Period|Study Retention Period in ISO-8601 period format PnYnMnD or PnW
-studyRetentionPolicy.dcmRulePriority:Rule Priority|Rule Priority.
+studyRetentionPolicy.dcmRulePriority:Rule Priority|If the condition of several Study Retention policies match for a received image, higher priority policy is applied. If there are several matching policies with equal priority, it is undefined which policy gets applied.
 studyRetentionPolicy.dcmProperty:Conditions|Conditions in format {key}[!]={value}. Refer <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/Conditions" target="_blank">applicability, format and some examples.</a>
 studyRetentionPolicy.dcmExpireSeriesIndividually:Expire Series Individually|Indicates if series should be expired individually or not.
 studyRetentionPolicy.dcmStartRetentionPeriodOnStudyDate:Start Retention Period on Study Date|Indicates if retention period should be started on Study Date instead on receive of an object of the Study

diff --git a/src/props/es/archiveAttributeCoercion.props b/src/props/es/archiveAttributeCoercion.props
@@ -1,6 +1,6 @@
 archiveAttributeCoercion:Coerción de atributos de archivo - Legacy|Coerción de atributos de archivo de DIMSE recibidos/enviados
 archiveAttributeCoercion.cn:Nombre|Nombre arbitrario/significativo del atributo de archivo Coerción
-archiveAttributeCoercion.dcmRulePriority:Prioridad de regla|Prioridad de regla. Se aplica la regla de mayor prioridad.
+archiveAttributeCoercion.dcmRulePriority:Prioridad de regla|Si la condición de varias coerciones de atributos de archivo (legado) coincide para una imagen recibida, se aplica la coerción de mayor prioridad. Si hay varias coerciones coincidentes con la misma prioridad, no se define qué coerción se aplica.
 archiveAttributeCoercion.dcmDIMSE:DIMSE|Elemento de mensaje DICOM sobre el que se aplicará esta coerción de atributo. También <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/Legacy-Archive-Attribute-Coercion---Application-of-multiple-coercions-using-one-coercion-rule#dimse" target="_blank">aplicable si las peticiones se reciben a través de web.</a>
 archiveAttributeCoercion.dicomTransferRole:Rol de transferencia DICOM|Rol de transferencia DICOM del peer DICOM AE.
 archiveAttributeCoercion.dcmSOPClass:Clase SOP UID|UID de la clase SOP a la que se aplicará esta coerción de atributos. Aplicar sobre cualquiera si está ausente.

diff --git a/src/props/es/archiveAttributeCoercion2.props b/src/props/es/archiveAttributeCoercion2.props
@@ -4,7 +4,7 @@ archiveAttributeCoercion2.dicomDescription:Descripción de la coerción de atrib
 archiveAttributeCoercion2.dcmURI:URI de coerción de atributos|Identifica la coerción de atributos mediante un identificador uniforme de recursos. Valores de referencia que puede establecer para <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/New-Archive-Attribute-Coercion---Application-of-multiple-coercions-for-one-use-case-using-multiple-rules#attribute-coercion-uri" target="_blank"> URI de coerción de atributos </a> en función del tipo de coerción.
 archiveAttributeCoercion2.dcmCoercionSufficient:Atributo Coerción Suficiente|No aplicar otras Coerciones de Atributo coincidentes de menor prioridad, si esta Coerción de Atributo fue aplicada efectivamente.
 archiveAttributeCoercion2.dcmCoercionOnFailure:: Coerción de atributos en caso de fallo|Comportamiento en caso de fallo al aplicar esta coacción de atributo. Consulte <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/New-Archive-Attribute-Coercion---Application-of-multiple-coercions-for-one-use-case-using-multiple-rules#attribute-coercion-on-failure" target="_blank"> Atributo Coacción sobre significados de fallo.</a>
-archiveAttributeCoercion2.dcmRulePriority:Atributo Prioridad de Coerción|Prioridad de la regla. La regla de mayor prioridad tiene prioridad.
+archiveAttributeCoercion2.dcmRulePriority:Atributo Prioridad de Coerción|Si la condición de varias coerciones de atributos de archivo (nuevo) coincide para una imagen recibida, tiene prioridad la coerción de mayor prioridad. Si hay varias coerciones coincidentes con la misma prioridad, no se define qué coerción tiene prioridad
 archiveAttributeCoercion2.dcmDIMSE:DIMSE|Elemento de mensaje DICOM al que se aplicará esta coerción de atributo. También <a href="https://github.com/dcm4che/dcm4chee-arc-light/wiki/New-Archive-Attribute-Coercion---Application-of-multiple-coercions-for-one-use-case-using-multiple-rules#dimse" target="_blank">aplicable si las solicitudes se reciben a través de la web.</a>
 archiveAttributeCoercion2.dicomTransferRole:Función de transferencia DICOM|Función de transferencia DICOM del par DICOM AE.
 archiveAttributeCoercion2.dcmSOPClass:SOP Class UID|UID de la clase SOP a la que se aplicará esta coerción de atributos. Aplicar sobre cualquiera si está ausente.