-
Notifications
You must be signed in to change notification settings - Fork 501
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
adminEmail field invalid in OAI-PMH Identify response #3619
Comments
Ah, |
As of 4.7 we are further promoting the addition of a name to the email address. For now, see "Branding Your Installation" at https://github.com/IQSS/dataverse/blob/a7242a92eb5173977fff6eadc984ce22ec55f3ba/doc/sphinx-guides/source/installation/config.rst#id75 |
I just noticed the post by @poikilotherm about Hacktoberfest ( https://hacktoberfest.digitalocean.com ) at https://groups.google.com/d/msg/dataverse-community/ootwCQL-4K4/00QO3__8CQAJ and the fact that he started using the label "hacktoberfest" over at https://github.com/IQSS/dataverse-kubernetes/issues He's inviting IQSS to use this label as well and this issue seems to meet "Choose issues that have a well-defined scope and are self-contained" guidance at https://hacktoberfest.digitalocean.com/details First, it's easy to see that Harvard Dataverse is returning an invalid response (red ERROR at the bottom of the screenshot below) by going to http://oval.base-search.net and entering https://dataverse.harvard.edu/oai I think the fix could be a one line change (plus adding an import statement). Maybe something like the untested diff below:
The starting point for anyone picking this up should be the Dataverse Developer Guide at http://guides.dataverse.org/en/4.16/developers/index.html I'm happy to answer questions here or at http://chat.dataverse.org or at https://groups.google.com/forum/#!forum/dataverse-dev I'd like to note that this bug affects on just Harvard Dataverse. It was also reported here: ualbertalib#63 |
This bug was also noticed by @shlake at https://groups.google.com/d/msg/dataverse-community/C-HLdPQwf70/I9SgmsPECAAJ |
I just made pull request #6513 to fix this. |
only show email portion system email via Harvesting #3619
Shoot. I made a mistake in pull request #6513 and now we're seeing errors in "develop" at I'm reopening this issue and will submit another pull request. |
I just made pull request #6538 to fix the error above. A null pointer exception was being thrown. |
avoid null pointer when getting email for OAI-PMH #3619
Unless the :SystemEmail setting contains only a mailbox addr-spec (just the address, no spaces or angle brackets), the Dataverse 4 OAI-PMH provider will return an invalid value for the adminEmail field, since that field should not contain a mailbox display name.
For example, the sample command in the :SystemEmail section of the Configuration section of the Installation Guide:
would result in this error.
Ideally, the OAI-PMH provider code would check for a value ending in "<.*>" and, if present, emit only the string between the angle brackets (i.e., like to sed -e 's/^[^<]*<\([^>]*\)>$/\1/ ').
The text was updated successfully, but these errors were encountered: