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.

Sign up for GitHub

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

Jump to bottom

Improve Report of Validator #83

Open
3 tasks
JoaoGomes2110 opened this issue Oct 28, 2021 · 1 comment
Open
3 tasks

Improve Report of Validator #83

JoaoGomes2110 opened this issue Oct 28, 2021 · 1 comment
Assignees
@carlosjepard
Milestone
Next Version

Comments

@JoaoGomes2110
Copy link
Contributor

  • Turn issues in List of a new class with location and message
  • Report issues turn into array of Objects
  • Improve EARK JSON report
@JoaoGomes2110 JoaoGomes2110 self-assigned this Oct 28, 2021
@luis100
Copy link
Member

luis100 commented Oct 29, 2021

Every identified issue should identify the location where the issue has happened, which can be the file where the issue was identified (the relative file path to it) and, if possible, the location within the file where the issue is found (line and column, xpath, or another way to locate content within the file).

Examples for location:

  • "obj-id/METS.xml: line 1, column 1"
  • "obj-id/representations/rep1/METS.xml: /mets/metsHdr[1]"
  • "obj-id/schemas"

@JoaoGomes2110 JoaoGomes2110 added this to the Next Version milestone Dec 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@carlosjepard carlosjepard

Labels
None yet
Projects
E-ARK CSP
Status: No status
Milestone
Next Version
Development

No branches or pull requests
3 participants
@luis100 @JoaoGomes2110 @carlosjepard