Bug #159
Confusing differnce in what constitutes an existing marker
| Status: | New | Start: | ||
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assigned to: | Cambell Prince | % Done: | 0% |
|
| Category: | application | Spent time: | - | |
| Target version: | V0.11 | |||
| Resolution: |
Description
In the list, a field like
\xe
counts as one instance.
But when you click on that row, you won't be shown this record, because the field is empty.
I'd be happy to have the count be a non-empty count, unless ther are some fields where a non-empty occurence means something... like maybe sn?
History
Updated by J C almost 2 years ago
Yes, this is inconsistent. I'm not sure I like the idea of switching to a non-empty count, because other fields besides sn can be empty yet important: ps, rf, and even something like ge (if it is set up to imply sn, for instance). Also, an empty field could be in the wrong place, causing an error, but it would be confusing if it therefore only showed up in the error records and not the records shown when you click on its marker. -Jon
Updated by J C almost 2 years ago
This issue is the same as #269. -Jon
Updated by Beth Bryson over 1 year ago
I think it would be good if you could show the records that have the empty markers.
Is there a way to have two kinds of counts? Number of times the marker occurs, and number that are empty? Like FLEx does in its import report.
I'm more concerned with seeing the record than I am with the count.
Updated by Cambell Prince over 1 year ago
TODO: Make empty count and non empty count. Also, make an option for the browsing behaviour. Show all, show empty, show non empty.