Fast way to get total count of found items, resources, and sources
Posted: Fri May 05, 2023 2:06 am
Hello!
In OxygenXML Author 25.0, I'm looking for a fast and simple way to see a count of total search results across a count of files in a count of sources. I searched the oxygenxml website and forum, and I watched a related video , but I didn't quite see what I'm looking for.
Details:
In OxygenXML Author 25.0, I'm looking for a fast and simple way to see a count of total search results across a count of files in a count of sources. I searched the oxygenxml website and forum, and I watched a related video , but I didn't quite see what I'm looking for.
Details:
- Open/Find Resource gives a count of matching resources, but not an obvious total count of found items when 'In content' is selected.
- Find/Replace in Files gives a count of found items, but not an obvious total count of matching resources.
- In Preferences, Open/Find Resource prefs include a mandatory search results limiter. Fortunately, in Open/Find Resource a count still appears of total matching resources despite the limiter, but only the limited number appear in the result set. This limit can be out of proportion with web-based search results that hit the same doc collection.
- One string that gives a total count of found items in a total count of resources. Example: "452 items found in 126 files".
- An option similar to the above that includes multiple linked sources, along with a details option that could offer a breakdown:
- Example: 17,362 items found in 887 files across 3 sources (Details)
- 13,002 items found in 686 files in source MyProject
- 3300 items found in 100 files in source OtherTeam'sProject
- 1060 items found in 101 files in source OtherDepartment'sProject
- Example: 17,362 items found in 887 files across 3 sources (Details)
- In Open/Find Resources, a string that shows how many times an item is found in each matching resource.
- An option (maybe a checkbox) associated with the results limiter in Open/Find Resource prefs to page large found sets if they exceed the limit. Example: "Use multiple pages to display all results". Even better would be to just do this by default. That way, you can keep the Open/Find Resource window performant and responsive by displaying the first X results (where X is a settable integer, as it is today) and then lazy-loading subsequent found items across additional 'pages' (separated lists) within the Open/Find Resource window.