Glitch in reserving ordinances
I recently found what I consider to be a glitch in the system. Normally, when you try to reserve ordinances the system will not let you if there is a possible duplicate. You have to resolve the duplicate issue before you can reserve the ordinances. But this is not the case with using ordinances ready. Last week I was helping some young men in our ward reserve ordinances for baptism. I had the helper number and birthdate of each person and afterwords checked to make sure that they had reserved ordinances. One of them reserved the ordinances for an ancestor. But when I checked the person there was a possible duplicate. It was obvious that they were a match, and I merged them. The duplicate already have the work done. And so it took away one of his reservations.
As far as I am aware, that checking for duplicates occurs when a reservation is requested. The vast majority of reservations provided through Ordinances Ready are already reserved by someone else and shared with the temple.
So it must be that when the original reservation was made, that possible duplicate flag was not there. It must have been sometime later that enough information was added to one of the two records, or both, that the possible duplicates routine was able to flag them.
That then raises the question, if a reservation is made, then months to years later a possible duplicate is found by the system due to updates on a person's records, should that reservation be canceled? Somehow that doesn't sound like a good idea.
This is a good argument that people should always make use of the "Learn more about this person" link that Ordinances Ready provides and do some quick scanning of the record for such issues.1