-
Notifications
You must be signed in to change notification settings - Fork 25
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
getAnnotationsOnPage.xql could return "wrong" data. #83
Comments
this is true, while the annotation list is populated from the |
I would suggest to define corresponding |
4 tasks
@hizclick yet another one for the collection? |
Merged
Merged
@nikobeer, is this issue already resolved or how can we reproduce the issue? |
Merged
github-project-automation
bot
moved this from In Progress
to Done
in Edirom Development
Dec 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It should be possible to exactly specify where annotations are gathered from. As I understand annotations are searched everywhere in '/db/contents/'? So if you have multiple MEI files with annotations you will possibly get "wrong" annotations (see l. 78).
Example from OPERA: working with two MEI files for prerelease final correction -> only "the first" (archived) MEI file is taken into account?
Further problem: This seems to be completely independent from getting annotations for the Annotations List and View? Here the correct file is found (specified). As a consequence you could get different annotations in annotation view compared to source view.
Would it be possible to centralize annotation management within Edirom?
The text was updated successfully, but these errors were encountered: