View Issue Details

IDProjectCategoryView StatusLast Update
0004536CaseTalk ModelerExpressionspublic2024-05-01 12:26
ReporterLennart van Ham Assigned ToBCP Software  
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
PlatformIntelOSWindowsOS Version11
Product Version13.2 
Fixed in Version13.3.1 
Summary0004536: Automatic matching not working for very simple example
DescriptionA very simple sequence of expressions cannot be matched automatically. The expressions in question are those in image 1 (just after classification).

Image 2 shows the second expression just before classification.

Image 3 shows the same expression, just after classification. After clicking 'finish', the expression window jumps to the third expression, where it provides the possible matches as expected.

When choosing the suggested match, the algorithm is unable to perform automatic matching (image 4).

So we have to do the classification manually (image 5).

As a result, the OTFT now has three exactly equal Fact sentences (image 6).
TagsNo tags attached.
CaseTalk EditionEducation Edition

Activities

Lennart van Ham

Lennart van Ham

2024-04-09 08:46

reporter  

image.png (33,770 bytes)   
image.png (33,770 bytes)   
image-2.png (156,051 bytes)   
image-2.png (156,051 bytes)   
image-3.png (165,331 bytes)   
image-3.png (165,331 bytes)   
image-4.png (171,622 bytes)   
image-4.png (171,622 bytes)   
image-5.png (153,330 bytes)   
image-5.png (153,330 bytes)   
image-6.png (114,802 bytes)   
image-6.png (114,802 bytes)   
BCP Software

BCP Software

2024-04-09 14:28

administrator   ~0005175

It looks the facts are entered with a first letter capital.
Please check:
- tools\preferences\tasks
  - match
  - expression display

Could the match may be set to identical instead of case insensitive? While the Expression Display is set to something else than 'as entered'?
Lennart van Ham

Lennart van Ham

2024-04-11 12:43

reporter   ~0005181

That was the case! I changed the setting.

But the problem itself seems strange.

1. The capital-letter-expression is classified, then saved without capital letters.
2. The same capital-letter-expression is classified, which cannot be matched to the already saved expression without capital letters, so it is again saved without capital letters.

I do not see a situation in which this would be the desired approach. Perhaps the settings should not allow for this to happen, at all.
BCP Software

BCP Software

2024-05-01 12:26

administrator   ~0005237

A combination of Case Sensitive and Preserve Dot settings may have caused this behaviour.

Issue History

Date Modified Username Field Change
2024-04-09 08:46 Lennart van Ham New Issue
2024-04-09 08:46 Lennart van Ham File Added: image.png
2024-04-09 08:46 Lennart van Ham File Added: image-2.png
2024-04-09 08:46 Lennart van Ham File Added: image-3.png
2024-04-09 08:46 Lennart van Ham File Added: image-4.png
2024-04-09 08:46 Lennart van Ham File Added: image-5.png
2024-04-09 08:46 Lennart van Ham File Added: image-6.png
2024-04-09 14:28 BCP Software Assigned To => BCP Software
2024-04-09 14:28 BCP Software Status new => feedback
2024-04-09 14:28 BCP Software Note Added: 0005175
2024-04-11 12:43 Lennart van Ham Note Added: 0005181
2024-04-11 12:43 Lennart van Ham Status feedback => assigned
2024-05-01 12:26 BCP Software Status assigned => resolved
2024-05-01 12:26 BCP Software Resolution open => fixed
2024-05-01 12:26 BCP Software Fixed in Version => 13.3.1
2024-05-01 12:26 BCP Software Note Added: 0005237