Re: [Dspace-devel] OAI validation - [email protected]

Tim Donohue Fri, 12 Oct 2012 09:34:05 -0700

I just ran the OAI Validation fromhttp://www.openarchives.org/Register/ValidateSite on the demo.dspace.orgsite


Most tests passed, but there were some failures.

I'm attaching the HTML results to this email. I'll also put them over inJIRA.


- Tim

On 10/12/2012 11:23 AM, Tim Donohue wrote:

Hi Claudia & helix84,

I've temporarily changed the demo.dspace.org server to have:

mail.admin = [email protected]

Hopefully this will let us run the validation tool at openarchives.org.

(That email address is managed by me/DuraSpace, but it is not actively
monitored. Technically any Committer with SSH access to demo.dspace.org
can easily lookup the password to that 'dspacedemo' Gmail acct.  If you
need that access, let me know.)

- Tim

On 10/12/2012 7:25 AM, Claudia Juergen wrote:

Hello Helix,

yes I know this is a valid email address and already contacted
openarchives.org, but this may take longer than the testathon. So just
out
of expedience an email accepted by the validation tool would be great or
someone else with a test server doing the validation.

Claudia

Maybe we can supply another email address, which appears more
"credible".


Admin email as presented by OAI Identify can't be changed unless we
also change the mail.admin property.

https://github.com/DSpace/DSpace/blob/master/dspace-oai/src/main/java/org/dspace/xoai/data/DSpaceIdentify.java#L61

[FAIL] adminEmail '[email protected]' looks bogus. This
must
be corrected to a valid email address before tests can continue.


Regarding openarchives, they should fix their email format
verification, because "+" is a valid character in email addresses and
is commonly used for filtering mail.

[email protected]
(Btw. who does manage this?)


That would be Duraspace sysadmins, i.e. Tim.

Regards,
~~helix84



Mit freundlichen Gruessen

Claudia Juergen
Universitaetsbibliothek Dortmund
Eldorado
0231/755-4043
https://eldorado.tu-dortmund.de/
Tel.: 0049-231-755-4043




------------------------------------------------------------------------------

Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Title: Data Provider Validation and Registration

D a t a P r o v i d e r V a l i d a t i o n a n d R e g i s t r a t i o n

Showing validation log

Running validation checks

baseURL is http://demo.dspace.org/oai/request
Validation only
Request logged from 67.177.108.221

Checking Identify response

Request: GET http://demo.dspace.org/oai/request?verb=Identify

Administrator email address [email protected]

[PASS] Correctly reports OAI-PMH protocol version 2.0

[PASS] baseURL supplied matches the Identify response

[PASS] Datestamp granularity is 'seconds'

[PASS] earliestDatestamp is 2012-06-26T19:58:24Z

Checking ListSets response

Request: GET http://demo.dspace.org/oai/request?verb=ListSets

[PASS] responseDate has correct format: 2012-10-12T16:30:11Z

[PASS] Extracted 15 set names: { com_10673_1 com_10673_10 com_10673_13 ... }, will use setSpec=com_10673_1 in tests

Checking ListIdentifiers response

Request: GET http://demo.dspace.org/oai/request?verb=ListIdentifiers&metadataPrefix=oai_dc

[PASS] responseDate has correct format: 2012-10-12T16:30:12Z

[PASS] Good ListIdentifiers response, extracted id 'oai:demo.dspace.org:10673/4' for use in future tests.

Checking ListMetadataFormats response

Request: GET http://demo.dspace.org/oai/request?verb=ListMetadataFormats&identifier=oai%3Ademo%2Edspace%2Eorg%3A10673/4

[PASS] responseDate has correct format: 2012-10-12T16:30:12Z

[PASS] Good ListMetadataFormats response, includes oai_dc

Checking GetRecord response

Request: GET http://demo.dspace.org/oai/request?verb=GetRecord&identifier=oai%3Ademo%2Edspace%2Eorg%3A10673/4&metadataPrefix=oai_dc

[PASS] responseDate has correct format: 2012-10-12T16:30:14Z

[PASS] Datestamp in GetRecord response (2012-10-07T02:00:13Z) has the correct form for seconds granularity.

[PASS] Datestamp in GetRecord response (2012-10-07T02:00:13Z) matched the seconds granularity specified in the Identify response.

[PASS] Valid GetRecord response

Checking ListRecords response

Request: GET http://demo.dspace.org/oai/request?verb=ListRecords&from=2012-10-07T02:00:13Z&until=2012-10-07T02:00:13Z&metadataPrefix=oai_dc

[PASS] responseDate has correct format: 2012-10-12T16:30:15Z

[PASS] Response is well formed

[FAIL] ListRecords response gave a noRecordsMatch error when it should have included at least the record with identifier oai:demo.dspace.org:10673/4. The from and until parameters of the request were set to the datestamp of this record (2012-10-07T02:00:13Z). The from and until parameters are inclusive, see protocol spec section 2.7.1. The message included in the error response was: 'No matches for the query'

Checking exception handling (errors)

Request: GET http://demo.dspace.org/oai/request?junk

[PASS] Error response correctly includes error code 'badVerb'

Request: GET http://demo.dspace.org/oai/request?verb=junk

[PASS] Error response correctly includes error code 'badVerb'

Request: GET http://demo.dspace.org/oai/request?verb=GetRecord&metadataPrefix=oai_dc