--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/f7a41fa9-a79f-426f-b822-67d81ab841f5%40googlegroups.com.
Hi Nick,What's weird is that the dataset you mentioned only has one version with a publication date of Feb 2019 but like you're saying, it has a timestamp of July 2019 from OAI-PMH:- July 2019: https://dataverse.tdl.org/oai?verb=GetRecord&identifier=doi:10.18738/T8/1Z6NGR&metadataPrefix=oai_dcAll that said, can you please share the details of the validation error? Does the validation error have to do with dates?I tried to get the details myself at https://www.openarchives.org/Register/ValidateSite but I think all I did was cause an email to be sent to TDL support judging from the attached screenshot. Sorry!Thanks,Phil
On Wed, Nov 20, 2019 at 12:44 PM Nicholas Woodward <woodward....@gmail.com> wrote:--Hi,We're attempting to validate our OAI-PMH endpoint in our Dataverse (version 4.17) with the Open Archives Initiative, and the process is failing for an odd reason.We have two sets: the DEFAULT one and another set up as per the instructions with "dsPersistenId:doi:/XX.XXXXX". When I look in the Dashboard they contain the same number of Datasets.The only validation failure with Open Archives occurs when the OAI feed gets a record (https://dataverse.tdl.org/oai?verb=GetRecord&identifier=doi%3A10%2E18738/T8/1Z6NGR&metadataPrefix=oai_dc) whose datestamp is 2019-07-16. But the record isn't listed when getting records from that time period (https://dataverse.tdl.org/oai?verb=ListRecords&from=2019-07-16T07:00:04Z&until=2019-07-16T07:00:04Z&metadataPrefix=oai_dc)Yet if you specify the set from the dsPersistentId in the same time period query the record exists (https://dataverse.tdl.org/oai?verb=ListRecords&set=TDR&from=2019-07-16T07:00:04Z&until=2019-07-16T07:00:04Z&metadataPrefix=oai_dc).So the issue is there's a record with two different timestamps that appear to be based on which set it's in (default or dsPersistenId). Has anyone else run into this issue? Is there something else we need to do to fix this one validation failure with OA? We've tried running exports on both sets in the Dashboard, but the difference in datestamps persists.Thanks,Nick
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/98c900bc-82b2-40b8-a8a9-58c74b88b18a%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CADL9p-XLPY9viN0vWZZH6JJb4JG8pNCvaP_%3Dq7F6SS9D9pUMPA%40mail.gmail.com.
Thanks! I grabbed a screenshot (attached) from that link so we can study it later. It's so close to passing!Unfortunately, I'm not very familiar with Dataverse's harvesting feature or the code behind it. I look at quick look at this class but I'm not sure what's going on: https://github.com/IQSS/dataverse/blob/v4.18.1/src/main/java/edu/harvard/iq/dataverse/harvest/server/xoai/XlistRecordsHandler.javaAt this point, I'd suggest emailing sup...@dataverse.org to create a ticket so that someone with more familiarity with harvesting can take a look. Then we can summarize for the list once we get to the bottom of it.My only other thought at the moment is that perhaps some other installations of Dataverse can try running https://www.openarchives.org/Register/ValidateSite to see if it passes or fails.Sorry I couldn't help more.Phil
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/98c900bc-82b2-40b8-a8a9-58c74b88b18a%40googlegroups.com.
Thanks for taking a look, Phil. I posted the same message to sup...@dataverse.org to create a ticket. We're happy to help troubleshoot the issue in any way.
Nick
On Thursday, November 21, 2019 at 3:34:40 PM UTC-6, Philip Durbin wrote:
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/a34b7dce-c43e-4d41-addb-12bd2fe81b6e%40googlegroups.com.
Hi Nick,Thanks for posting this.A little background:When we first added harvesting (back) to Dataverse 4, we saw some failures on validation of our own production and over time fixed them. Whether the issues you are seeing are due to differences in your metadata or a new bug is something we'll have to investigate. So thanks for opening that RT ticket (we'll likely open a github issue, so we can track progress on it).(At the same time, hopefully we can look at addressing Sheery's issue https://github.com/IQSS/dataverse/issues/3619 as well)Do note, that while the validator does find spec compliance issues (and that we want to fix them), in practice, most clients should be able to successfully harvest from you.Thanks,Gustavo
On Fri, Nov 22, 2019 at 12:41 PM Nicholas Woodward <woodward....@gmail.com> wrote:
Thanks for taking a look, Phil. I posted the same message to sup...@dataverse.org to create a ticket. We're happy to help troubleshoot the issue in any way.
Nick
On Thursday, November 21, 2019 at 3:34:40 PM UTC-6, Philip Durbin wrote:
Thanks! I grabbed a screenshot (attached) from that link so we can study it later. It's so close to passing!
Unfortunately, I'm not very familiar with Dataverse's harvesting feature or the code behind it. I look at quick look at this class but I'm not sure what's going on: https://github.com/IQSS/dataverse/blob/v4.18.1/src/main/java/edu/harvard/iq/dataverse/harvest/server/xoai/XlistRecordsHandler.java
At this point, I'd suggest emailing sup...@dataverse.org to create a ticket so that someone with more familiarity with harvesting can take a look. Then we can summarize for the list once we get to the bottom of it.
My only other thought at the moment is that perhaps some other installations of Dataverse can try running https://www.openarchives.org/Register/ValidateSite to see if it passes or fails.
Sorry I couldn't help more.
Phil
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/98c900bc-82b2-40b8-a8a9-58c74b88b18a%40googlegroups.com.
--
Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
Yeah, unfortunately, that :SystemEmail problem is a known issue. Please see "adminEmail field invalid in OAI-PMH Identify response" at https://github.com/IQSS/dataverse/issues/3619Please do report back after you try again!
On Fri, Nov 22, 2019 at 11:03 AM Sherry Lake <shla...@gmail.com> wrote:
I tried running the Validator (via the ValidateSite URL below) and got an error right away with my "adminEmail".FAIL adminEmail 'Libra Data Support ' looks bogus. This must be corrected to a valid email address before tests can continueFAIL ABORT: looks like bogus adminEmail, aborting.Here's what our Dataverse db has:":SystemEmail":"Libra Data Support <li...@virginia.edu>"Which works, but obviously breaks the OAI-PMH validator.FYI: the Dataverse Config guide has an example with the address "text", but the validator doesn't seem to like the text.I'll change my system Email and try again.--Sherry
On Thu, Nov 21, 2019 at 4:34 PM Philip Durbin <philip...@harvard.edu> wrote:
Thanks! I grabbed a screenshot (attached) from that link so we can study it later. It's so close to passing!Unfortunately, I'm not very familiar with Dataverse's harvesting feature or the code behind it. I look at quick look at this class but I'm not sure what's going on: https://github.com/IQSS/dataverse/blob/v4.18.1/src/main/java/edu/harvard/iq/dataverse/harvest/server/xoai/XlistRecordsHandler.javaAt this point, I'd suggest emailing sup...@dataverse.org to create a ticket so that someone with more familiarity with harvesting can take a look. Then we can summarize for the list once we get to the bottom of it.My only other thought at the moment is that perhaps some other installations of Dataverse can try running https://www.openarchives.org/Register/ValidateSite to see if it passes or fails.Sorry I couldn't help more.Phil
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CADL9p-XLPY9viN0vWZZH6JJb4JG8pNCvaP_%3Dq7F6SS9D9pUMPA%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CADL9p-XLPY9viN0vWZZH6JJb4JG8pNCvaP_%3Dq7F6SS9D9pUMPA%40mail.gmail.com.
--Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/012ef218-f4ee-47fb-a9e5-f8e3fe290ce8%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8EV10wBk%3DBx6i_oTh7B9iJhsH4nCKmnL8%3D0YG6z6zbeEQ%40mail.gmail.com.