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

[Feature] Support for multi-page OMRs #145

Open
Udayraj123 opened this issue Jul 4, 2023 · 6 comments
Open

[Feature] Support for multi-page OMRs #145

Udayraj123 opened this issue Jul 4, 2023 · 6 comments
Labels
Discussion enhancement New feature or request Hard

Comments

@Udayraj123
Copy link
Owner

Udayraj123 commented Jul 4, 2023

Is your feature request related to a problem? Please describe.
We have discovered use cases for OMRs having multiple pages. Need a discussion on how to standardise the process of creating multi-page OMRs so that OMRChecker can identify that the two images are part of the same OMR sheet.

Discord message link: https://discord.com/channels/590134763784896514/1122965202997096549/1122966382137573596

Describe the solution you'd like
We will rely on file naming conventions and file structure:
Consider adding a special new file template-multi.json with a rough draft schema:

{
    "templateNames":{
        "page1": {
            "relative_path": "template-page1.json",
            "imageNameSelector": {
                "type": "OMR_ID_PAGE_NUMBER",
                "imageNameSuffix": "_1"
            }
        },
        "page2": {
            "relative_path": "template-page2.json",
            "imageNameSelector": {
                "type": "OMR_ID_PAGE_NUMBER",
                "imageNameSuffix": "_2"
            }
        }
    },
    "outputColumns": ["q1", "q2", "q3", "q4"]
}

Describe alternatives you've considered

  • A central file could also be used. Same as above config, but instead of template path we directly pass full template json
  • One more way is to add a QR code to indicate omr identifier

Additional context
Many directions will be affected with change in the central schema for template files. Some items to start thinking upon:

  • Strong Validation will be needed to avoid bad UX
    • Restrictions over particular plugins in inner template configs
    • Column overlaps
    • Presence of files
    • Absence of extra files
  • Supporting regex and file naming patterns
  • Concatenation config requirements
  • Output file location and structure changes
  • Evaluation logic changes
@Udayraj123 Udayraj123 added enhancement New feature or request Discussion Hard labels Jul 6, 2023
@ghplvh
Copy link

ghplvh commented Oct 1, 2023

把图片拼成一张,不就行了,虽然不是很提倡,但是也是个办法

@Udayraj123
Copy link
Owner Author

@ghplvh English please?

@ghplvh
Copy link

ghplvh commented Oct 9, 2023

@ghplvh English please?

Merge the images?

@Udayraj123
Copy link
Owner Author

@ghplvh merging the images can be desirable too, but if the number of pages is too high, we would prefer creating a single folder per OMR id

@Sadhgun
Copy link

Sadhgun commented Oct 14, 2023

Here's a brief idea:
Having two markers - one for identifying the participant details and one for describing the page number.
The marker for page number could also be used to make sure the paper is correctly aligned.
Pre processor to be created - Person identifier to rename the omr sheet. Page identifier to sort the files into two folders with each having their template.json
Two csv created will be merged using person identifier as common marker

@Udayraj123
Copy link
Owner Author

@Sadhgun we will discuss on discord and put the minutes of the call here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion enhancement New feature or request Hard
Projects
Status: No status
Development

No branches or pull requests

3 participants