Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wrong image is associated with transcribed record #177

Closed
dreams-togo opened this issue Jan 29, 2025 · 4 comments
Closed

wrong image is associated with transcribed record #177

dreams-togo opened this issue Jan 29, 2025 · 4 comments

Comments

@dreams-togo
Copy link
Collaborator

Create an assignment with Local PC images and choose 2 images to upload. Go to the Transcribe page, and go to the second image and transcribe a record. Then go back to the Assignments page and look at the list of images in the assignment. The Transcription Complete Date is associated with the first image, which means that the second image can be deleted, but that's the one from which the record was transcribed.

@nurifreembd
Copy link
Collaborator

@dreams-togo will you have the capacity to look into this bug in this sprint please?

@DeniseColbert DeniseColbert removed the bug label Feb 6, 2025
@dreams-togo
Copy link
Collaborator Author

freeregdev said: This isn't a bug.

What happens is this,
When creating an assignment with images from any source, FreeComETT assumes that you will transcribe the images one by one starting from the first and moving to the last. Thus, on transcribing an assignment for the first time, it will present the first image for you to transcribe.
When you move forward to the next image in the image set, FreeComETT marks the current image as transcribed and shows you the next image. The current image then becomes the one you moved to. FreeComETT keeps track of the current image in the assignment and shows you which one it is in the TP home page.
You can always move back to the previous image and transcribe it. As you start to transcribe, it become the current image.

FreeComETT has no way to know whether an image has been transcribed or how many records are on the image.

@stsccfr
Copy link
Collaborator

stsccfr commented Feb 15, 2025

It isn't safe to assume that the first image will always be the first one to be transcribed, nor is it safe to assume that the images will be transcribed in the order of their filenames, or any particular order for that matter. The first few images of any image set are often of the cover of the register, the front flyleaf, title page, and other prefacing material. The image filenames don't always follow the order of the pages in the register, because sometimes pages are inadvertently skipped during filming and are filmed later and added to the final image set. The DSC numbers used by digital cameras turn over, from 9999 back to 0001, so an alphanumeric file listing won't put these in the right order. And any register whose initial filming was cut off at some date (usually 1900, which applies to practically everything that FamilySearch filmed back in the 1980s) and then completed later, isn't necessarily going to have filenames that make it clear which set comes first.

The only reasonable assumption is that whatever record is currently being keyed is also being displayed, but let's document that because someone is bound to violate this assumption eventually.

It's fine for FreeComETT to list the images in the same order as one would see in a folder listing (alphanumeric), but the order in which those images are actually transcribed must be left up to the transcriber.

@nurifreembd
Copy link
Collaborator

@stsccfr please reproduce this test and provide details here for fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants