In my library, this "error" in tagging a scriptural reference occurs approximately 10, 731 times in 5, 842 articles in 807 resources i.e. more than 10% of my resources. Running the following query will give your error rate."(1, 2, 3, 4, 5, 6, 7, 8, 9, 0) LXX" (quotations required). This is where the book containing the reference explicitly points the reader to a Septuagint based translation. This is not verse mapping or specification of a specific translation but rather a case where the LXX text supports the point being made but the Masoretic does not.
Suggestion:
- users should be able to prioritize LXX translations independent of Masoretic translations
- have tagging and parsing recognize references in the format of <verse map> <book> <chapter/verse> <LXX> as pointing to Septuagint translations Note that Psalms add a minor wrinkle to this general rule - an identifiable wrinkle.
- if UI design considers it necessary display both the standard highest priority and the LXX highest priority when an LXX reference is specified. I personally would be satisfied with only the LXX translation.
