Why are some collections images being overtaken by the newer Images viewer?
I learned something new today!
I was just editing a 1930 Census record and the first time from the older indexing app it opened the older image viewer (Search> Records). I went back to explain what I had done to the OP here in Community and another Community member had responded. I went back and this time when opening the image it opened in the new image viewer (Search> Images). The first time - prior to editing in the old viewer there had been no index on the new image viewer (yes I actually had checked) - after editing in the old viewer there was an index in the new viewer (it actually had both the original and new entries for Birth Name)! Freaky... seeing it in real-time while editing one it wrote/appeared in the other.
Anyway I suppose that what is occurring is the Community initiated index of the Search> Images new viewer index through migration of the old viewer index ... cool (hope that makes sense to everyone).
So I guess the question is - is that right? Is that how the index is going to be created/migrated to the new image viewer? Cool! because not only does that take advantage of all the Indexing app indexers hard work (over many years) - but also allows correction (a new indexing pass) if need be! I had thought the computer/AI indexer would have done the initial pass (as it has or appears to have done on some collections) and then the 'edit every index' field would be available in the new viewer - but this way works as well.
I just hope the record/page is locked when possibly there might be several indexing the same page at the same time?!
Here's another post/example that may help explain.
N Tychonievich mod
@genthusiast FamilySearch is working to make more of the record collections fully editable. As collections become fully editable, they open in the new image viewer. As you discovered, the 1930 US Census is one of the records where you can now edit all fields in the new viewer.
As far as I know, there is no lock on an image when you are in the process of editing it. The chances of 2 people editing a given page at the same moment are pretty remote.1
The chances of 2 people editing a given page at the same moment are pretty remote.
Those chances greatly increase if multiple people attempt responding to a person's query here in Community. I think it might be good for the engineers to implement a token ring/library checkout type model such that users are not competing for highlights/edits? Likely the engineers have already considered/implemented something - I just don't know what that is. Having experienced disappearing highlights several times (and given feedback) - it would be nice to know what was the cause (yes I tried to carefully select Done each time).0
I work on the team that created the new image viewer. Thank you for your comments and insights! Eventually we'll work on restricting access though as of now it's not an issue since multiple people working on a single record is rather remote. Though any suggestions you have please let me know and I'd love to look into them!