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

Invalid EML during publication - version 3.1.0 #2561

Open
AaronWilton opened this issue Oct 28, 2024 · 3 comments
Open

Invalid EML during publication - version 3.1.0 #2561

AaronWilton opened this issue Oct 28, 2024 · 3 comments
Assignees
Milestone

Comments

@AaronWilton
Copy link

What
Attempting to publish a new resource on hosted IPT.gbif.org.nz:
https://ipt.gbif.org.nz/manage/resource.do?r=ncc_bird_counts_until_2023
IPT version 3.1.0

When publish get the message: "Invalid EML file: org.xml.sax.SAXParseException; lineNumber: 40; columnNumber: 36; cvc-complex-type.2.4.a: Invalid content was found starting with element 'electronicMailAddress'. One of '{organizationName, individualName, positionName}' is expected."

Additional info

  •  (probably not related) It had originally been incorrectly mapped by the data publisher as a checklist, removed mappings, changed core to occurrence, re-mapped to updated core
  • Have been through the metadata and cannot see anything obvious

Image

@mike-podolskiy90
Copy link
Contributor

mike-podolskiy90 commented Oct 28, 2024

Thanks for reporting this issue.
I'll get back to you

@mike-podolskiy90
Copy link
Contributor

mike-podolskiy90 commented Oct 29, 2024

It seems you have an effectively empty block in the Associated parties (only role is provided). Remove it or add more data to it (at least last name or organization).
I'll address IPT validation to prevent it from happening

@AaronWilton
Copy link
Author

@mike-podolskiy90 - thanks - have removed for data provider and successfully published.

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

2 participants