Re: OAI-PMH Registration - email problem

[Simeon Warner]

Dear Vaso Manojlovic,

I have no easy way to tell why you did not get the confirmation email. I
have run the validation process again manually (log below). Your
repository is compliant and is now included in the list of registered
repositories.

Cheers,
Simeon


>./ValidateSite.pl -u https://metall-mater-eng.com/index.php/index/oai
ValidateSite.pl: Running from command line (no email, DB will be updated).
RUNNING VALIDATION CHECKS (STEP 2)
baseURL is https://metall-mater-eng.com/index.php/index/oai
Registration requested
Request logged from run.locally

### Checking Identify response

REQUEST: https://metall-mater-eng.com/index.php/index/oai?verb=Identify GET
PASS: Administrator email address is 'v.mano...@itnms.ac.rs'
PASS: Correctly reports OAI-PMH protocol version 2.0
PASS: baseURL supplied matches the Identify response
PASS: Datestamp granularity is 'seconds'
PASS: Extracted earliestDatestamp 2016-04-10T12:26:29Z
PASS: oai-identifier description for version 2.0 is being used
PASS: namespace-identifier (repositoryIdentifier element) in
oai-identifier declaration is ojs.localhost

### Checking ListSets response

REQUEST: https://metall-mater-eng.com/index.php/index/oai?verb=ListSets GET
PASS: responseDate has correct format: 2018-11-30T10:14:11Z
PASS: Extracted 11 set names: { home home:FLRP home:PC ... }, will
use setSpec &set=home in tests

### Checking ListIdentifiers response

REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=home
GET
PASS: responseDate has correct format: 2018-11-30T10:14:11Z
WARN: Identifier 1, 'oai:ojs.metall-mater-eng.com:article/3', is for
a deleted record, skipping
WARN: Identifier 2, 'oai:ojs.metall-mater-eng.com:article/6', is for
a deleted record, skipping
WARN: Identifier 3, 'oai:ojs.metall-mater-eng.com:article/7', is for
a deleted record, skipping
WARN: Identifier 4, 'oai:ojs.metall-mater-eng.com:article/8', is for
a deleted record, skipping
WARN: Identifier 5, 'oai:ojs.metall-mater-eng.com:article/9', is for
a deleted record, skipping
WARN: Identifier 6, 'oai:ojs.metall-mater-eng.com:article/10', is for
a deleted record, skipping
WARN: Identifier 7, 'oai:ojs.metall-mater-eng.com:article/11', is for
a deleted record, skipping
WARN: Identifier 8, 'oai:ojs.metall-mater-eng.com:article/41', is for
a deleted record, skipping
WARN: Identifier 9, 'oai:ojs.metall-mater-eng.com:article/42', is for
a deleted record, skipping
WARN: Identifier 10, 'oai:ojs.metall-mater-eng.com:article/43', is
for a deleted record, skipping
WARN: Identifier 11, 'oai:ojs.metall-mater-eng.com:article/44', is
for a deleted record, skipping
WARN: Identifier 12, 'oai:ojs.metall-mater-eng.com:article/45', is
for a deleted record, skipping
WARN: Identifier 13, 'oai:ojs.metall-mater-eng.com:article/46', is
for a deleted record, skipping
WARN: Identifier 14, 'oai:ojs.metall-mater-eng.com:article/47', is
for a deleted record, skipping
WARN: Identifier 15, 'oai:ojs.metall-mater-eng.com:article/48', is
for a deleted record, skipping
WARN: Identifier 16, 'oai:ojs.metall-mater-eng.com:article/49', is
for a deleted record, skipping
WARN: Identifier 17, 'oai:ojs.metall-mater-eng.com:article/50', is
for a deleted record, skipping
WARN: Identifier 18, 'oai:ojs.metall-mater-eng.com:article/51', is
for a deleted record, skipping
WARN: Identifier 19, 'oai:ojs.metall-mater-eng.com:article/52', is
for a deleted record, skipping
WARN: Identifier 20, 'oai:ojs.metall-mater-eng.com:article/53', is
for a deleted record, skipping
WARN: Identifier 21, 'oai:ojs.metall-mater-eng.com:article/54', is
for a deleted record, skipping
WARN: Identifier 22, 'oai:ojs.metall-mater-eng.com:article/62', is
for a deleted record, skipping
WARN: Identifier 23, 'oai:ojs.metall-mater-eng.com:article/63', is
for a deleted record, skipping
WARN: Identifier 24, 'oai:ojs.metall-mater-eng.com:article/64', is
for a deleted record, skipping
WARN: Identifier 25, 'oai:ojs.metall-mater-eng.com:article/65', is
for a deleted record, skipping
WARN: Identifier 26, 'oai:ojs.metall-mater-eng.com:article/66', is
for a deleted record, skipping
WARN: Identifier 27, 'oai:ojs.metall-mater-eng.com:article/67', is
for a deleted record, skipping
WARN: Identifier 28, 'oai:ojs.metall-mater-eng.com:article/68', is
for a deleted record, skipping
PASS: Good ListIdentifiers response, extracted id
'oai:ojs.localhost:article/69' for use in future tests.

### Checking ListMetadataFormats response

REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=ListMetadataFormats&identifier=oai%3Aojs%2Elocalhost%3Aarticle/69
GET
PASS: responseDate has correct format: 2018-11-30T10:14:12Z
PASS: Good ListMetadataFormats response, includes oai_dc
PASS: Data provider supports oai_dc metadataPrefix

### Checking GetRecord response

REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=GetRecord&identifier=oai%3Aojs%2Elocalhost%3Aarticle/69&metadataPrefix=oai_dc
GET
PASS: responseDate has correct format: 2018-11-30T10:14:12Z
PASS: Datestamp in GetRecord response (2018-07-20T09:21:11Z) has the
correct form for seconds granularity.
PASS: Datestamp in GetRecord response (2018-07-20T09:21:11Z) matched
the seconds granularity specified in the Identify response.
PASS: Expected setSpec was returned in the response (implied by a
descendant setSpec)

### Checking ListRecords response

REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=ListRecords&from=2018-07-20T09:21:11Z&until=2018-07-20T09:21:11Z&metadataPrefix=oai_dc
GET
PASS: responseDate has correct format: 2018-11-30T10:14:12Z
PASS: Response is well formed
PASS: ListRecords response correctly included record with identifier
oai:ojs.localhost:article/69

### Checking exception handling (errors)

REQUEST: https://metall-mater-eng.com/index.php/index/oai?junk GET
PASS: Error response correctly includes error code 'badVerb'
REQUEST: https://metall-mater-eng.com/index.php/index/oai?verb=junk GET
PASS: Error response correctly includes error code 'badVerb'
REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=GetRecord&metadataPrefix=oai_dc
GET
PASS: Error response correctly includes error code 'badArgument'
REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=GetRecord&identifier=oai:ojs.localhost:article/69
GET
PASS: Error response correctly includes error code 'badArgument'
REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=GetRecord&identifier=invalid"id&metadataPrefix=oai_dc
GET
PASS: Error response correctly includes error code 'badArgument'
REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=ListIdentifiers&until=junk
GET
PASS: Error response correctly includes error code 'badArgument'
REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=ListIdentifiers&from=junk
GET
PASS: Error response correctly includes error code 'badArgument'
REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=ListIdentifiers&resumptionToken=junk&until=2000-02-05
GET
PASS: Error response correctly includes error code 'badArgument'
REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=ListRecords&metadataPrefix=oai_dc&from=junk
GET
PASS: Error response correctly includes error code 'badArgument'
REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=ListRecords&resumptionToken=junk
GET
PASS: Error response correctly includes error code 'badResumptionToken'
REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=ListRecords&metadataPrefix=oai_dc&resumptionToken=junk&until=1990-01-10
GET
PASS: Error response correctly includes error code 'badArgument'
REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=ListRecords&metadataPrefix=oai_dc&until=junk
GET
PASS: Error response correctly includes error code 'badArgument'
REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=ListRecords GET
PASS: Error response correctly includes error code 'badArgument'
PASS: All 13 error requests properly handled

### Checking for version 2.0 specific exceptions

REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=ListRecords&metadataPrefix=oai_dc&from=2002-02-05&until=2002-02-06T05:35:00Z
GET
PASS: Error response correctly includes error code 'badArgument'
REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=ListRecords&metadataPrefix=oai_dc&until=2015-04-10T12:26:29Z
GET
PASS: Error response correctly includes error code 'noRecordsMatch'

### Checking that HTTP POST requests are handled correctly

REQUEST: https://metall-mater-eng.com/index.php/index/oai POST verb:Identify
PASS: POST test 1 for Identify was successful
REQUEST: https://metall-mater-eng.com/index.php/index/oai POST
identifier:oai:ojs.localhost:article/69 metadataPrefix:oai_dc verb:GetRecord
PASS: POST test 2 for GetRecord was successful

### Checking for correct use of resumptionToken (if used)

REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=ListRecords&metadataPrefix=oai_dc
GET
NOTE: Got resumptionToken 4786980a6914d1e6f7eec8c44cc1c438
REQUEST:
https://metall-mater-eng.com/index.php/index/oai?verb=ListRecords&resumptionToken=4786980a6914d1e6f7eec8c44cc1c438
GET
PASS: Resumption tokens appear to work
SUMMARY - <EM>SUCCESS</EM>

<ul>
<li>Namespace declared for v2.0 oai-identifiers is ojs.localhost</li>
<li>Uses https URIs (not specified in protocol)</li>
<li>Total tests passed: 40</li>
<li>Total warnings: 28</li>
<li>Total error count: 0</li>
<li>Validation status: COMPLIANT</li>
</ul>
The namespace-identifier for oai-identifiers declared in the
repositoryIdentifier element a is already registered to another base
URL, namely http://ojs.sttjaffray.ac.id/index.php/JJV71/oai. We trust
that this is another repository operated by your organization.

Successfully updated OAI registration database to status COMPLIANT.


Validation process complete

On 11/28/18 10:34 AM, Vaso Manojlović wrote:
> Dear OAI team,
>
> I'm trying to register our Journal
> https://metall-mater-eng.com/index.php/index/oai through your website
> https://www.openarchives.org/Register/ValidateSite
> Our URL has passed initial validation, but e-mail for continuing
> registration was never sent to me.
> Can you please help me with this?
>
> Kind regards,
> Vaso Manojlovic
> Journal Manager at MME
> --
> Assistant professor at
> University of Belgrade
> Faculty of Technology and Metallurgy
> 4 Carnegie St., 11120 Belgrade, Serbia

[Vaso Manojlović]

Thank you Simeon for including our journal in the list of registered repositories.

Kind regrads,

Vaso