use the matching of custom states number value to the current cells index value if you are using repeating groups.
Also, use workflows to set custom states based off of conditionals when information in another custom state changes. You can set workflow events to trigger when a condition is true.
But when you talk about a last obstacle of indexing, are you referring to putting the sorted and filtered votes into some kind of category or grouping?
Are you trying to get the information saved to D.B. or just be used in another custom state?
If you are trying to categories or group the sorted and filtered votes you would create a custom state that is a list of things ( ie: votes that match to the sort and filter criteria ) Then use a workflow to set the states, be sure to add list of the items.
Another technique is not to download the information from the D.B. but to save it to the database and then use it to be added to a custom state in the workflows by referencing the step number in the value section; ( ie: value = result of step 2 create new vote )
From there you have the information that was just saved to the D.B. automatically and I believe without much time delay, as a custom state and be able to link to the info for all kinds of workflows and functionality on the page. For example, if I had a vote that was for President A from a student who was 18 in the City of Big City at a polling station of number 4568; I would be able to have access to all of the information in a custom state on the page to use as much as I want, without ever needing to download the information itself through a search of the D.B.
Custom states are great…they are truly inspiring once you play around with them and see all the different ways to use them. Really helps to creatively get over hurdles.