[Solved] Failed to register database at OAI

Software Support
1

Trying to register my journal database at OAI (https://www.openarchives.org), and this is the error log

Showing validation log

Running validation checks (step 2)

baseURL is http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai 
Registration requested 
Request logged from 189.41.52.118

Checking Identify response

REQUEST http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=Identify GET
PASS Administrator email address is 'editor@xxx.com.br'
PASS Correctly reports OAI-PMH protocol version 2.0
PASS baseURL supplied matches the Identify response
PASS Datestamp granularity is 'seconds'
PASS Extracted earliestDatestamp 2017-08-12T15:51:13Z
PASS oai-identifier description for version 2.0 is being used
PASS namespace-identifier (repositoryIdentifier element) in oai-identifier declaration is ojs2.psicodebate.dpgpsifpm.com.br
Checking ListSets response

REQUEST http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListSets GET
PASS responseDate has correct format: 2017-11-12T20:14:16Z
PASS Extracted 8 set names: { periodico periodico:ART periodico:REV ... }, will use setSpec &set=periodico in tests
Checking ListIdentifiers response

REQUEST http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=periodico GET
PASS responseDate has correct format: 2017-11-12T20:14:17Z
PASS Good ListIdentifiers response, extracted id 'oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3' for use in future tests.
Checking ListMetadataFormats response

REQUEST http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListMetadataFormats&identifier=oai%3Aojs2%2Epsicodebate%2Edpgpsifpm%2Ecom%2Ebr%3Aarticle/3 GET
PASS responseDate has correct format: 2017-11-12T20:14:17Z
FAIL No metadata formats are listed in the response to a ListMetadataFormats request for item oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3.
FAIL There are no metadata formats available to use with the GetRecord request. The metadataPrefix oai_dc will be used for later tests even though it seems unsupported.
Checking GetRecord response

REQUEST http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=GetRecord&identifier=oai%3Aojs2%2Epsicodebate%2Edpgpsifpm%2Ecom%2Ebr%3Aarticle/3&metadataPrefix=oai_dc GET
PASS responseDate has correct format: 2017-11-12T20:14:17Z
FAIL The response to the GetRecord verb was the OAI exception [badArgument: Identifier is not in a valid format] . It is this not possible to extract a valid datestamp for remaining tests
FAIL ABORT: Unexpected OAI exception response
Summary - failure

Namespace declared for v2.0 oai-identifiers is ojs2.psicodebate.dpgpsifpm.com.br
Total tests passed: 13
Total warnings: 0
Total error count: 4
Validation status: FAILED
Successfully updated OAI registration database to status FAILED.

I tried at BASE too (https://www.base-search.net/) and get a slight different description of the error:

Repository Information
Name:
Psicologia e Saúde em debate
Admin:
editor@xxx.com.br
Server communication
 SUCCESS: Server supports both GET and POST requests.
 SUCCESS: OAI-PMH version is 2.0
XML Validation
 SUCCESS: Identify response well-formed and valid.
 SUCCESS: ListRecords response well-formed and valid.
Harvesting
 SUCCESS: Deleting strategy is "persistent"
 UNVERIFIED: ListRecords batch size could not be checked: Only one batch.
 UNVERIFIED: Resumption requests could not be checked: No resumptionToken found
 ERROR: No incremental (day granularity) harvesting of ListRecords. Harvest for reference date 2017-08-23 returned record with date 2017-08-22.
 ERROR: No incremental (full granularity) harvesting of ListRecords. Harvest for reference date 2017-08-23T20:55:46Z returned record with date 2017-08-23T20:49:43Z.
 SUCCESS: dc:language elements conform to ISO 639-3.
 SUCCESS: dc:date elements conform to ISO 8601.
 SUCCESS: Minimal DC elements (date, creator, identifier, type, title) are present.

Any help is welcome.

2

In the first case, it appears that the server is escaping the identifiers in the request, and this is not not being processed within OJS.

For example, the request specified fails:
http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListMetadataFormats&identifier=oai%3Aojs2.psicodebate.dpgpsifpm.com.br%3Aarticle/3
but the following request works:
http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListMetadataFormats&identifier=oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3

From a URL perspective, these should be identical, so I’m guessing this is a bug in OJS.

It looks like you are running 3.1, and I’ve replicated this in 3.0.2. The functionality appears to work as expected in OJS 2.4.8.

Issue opened here: OAI-PMH does not respect URLencoded identifiers as parameters · Issue #3053 · pkp/pkp-lib · GitHub

3

@ctgraham Thank you for the assistance.

This is the error report from Open Archives Initiative - Repository Explorer

RE Protocol Tester 1.47 :: UCT AIM :: September 2014

(1) Testing : Identify
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=Identify
------ Response from Xerces Schema Validation ------
[Warning] re.0iygB5:24:63: schema_reference.4: Failed to read schema document 'http://www.openarchives.org/OAI/2.0/oai-identifier.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
[Error] re.0iygB5:24:63: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'oai-identifier'.
[Warning] re.0iygB5:25:13: schema_reference.4: Failed to read schema document 'http://www.openarchives.org/OAI/2.0/oai-identifier.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
[Warning] re.0iygB5:26:27: schema_reference.4: Failed to read schema document 'http://www.openarchives.org/OAI/2.0/oai-identifier.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
[Warning] re.0iygB5:27:16: schema_reference.4: Failed to read schema document 'http://www.openarchives.org/OAI/2.0/oai-identifier.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
[Warning] re.0iygB5:28:23: schema_reference.4: Failed to read schema document 'http://www.openarchives.org/OAI/2.0/oai-identifier.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
/tmp/re.0iygB5: 3200;8;0 ms (27 elems, 9 attrs, 0 spaces, 552 chars)
------- End of Xerces Schema Validation Report  -------
------ Start of XML Response ------
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="http://psicodebate.dpgpsifpm.com.br/lib/pkp/xml/oai2.xsl" ?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/
		http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
	<responseDate>2017-11-13T17:10:23Z</responseDate>
	<request verb="Identify">http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai</request>
	<Identify>
		<repositoryName>Psicologia e Saúde em debate</repositoryName>
		<baseURL>http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai</baseURL>
		<protocolVersion>2.0</protocolVersion>
		<adminEmail>editor@dpgpsifpm.com.br</adminEmail>
		<earliestDatestamp>2017-08-12T23:51:59Z</earliestDatestamp>
		<deletedRecord>persistent</deletedRecord>
		<granularity>YYYY-MM-DDThh:mm:ssZ</granularity>
		<compression>gzip</compression>
		<compression>deflate</compression>
		<description>
			<oai-identifier
				xmlns="http://www.openarchives.org/OAI/2.0/oai-identifier"
				xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
				xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai-identifier
					http://www.openarchives.org/OAI/2.0/oai-identifier.xsd">
				<scheme>oai</scheme>
				<repositoryIdentifier>ojs2.psicodebate.dpgpsifpm.com.br</repositoryIdentifier>
				<delimiter>:</delimiter>
				<sampleIdentifier>oai:ojs2.psicodebate.dpgpsifpm.com.br:article/1</sampleIdentifier>
			</oai-identifier>
		</description>
		<description>
			<toolkit
				xmlns="http://oai.dlib.vt.edu/OAI/metadata/toolkit"
				xsi:schemaLocation="http://oai.dlib.vt.edu/OAI/metadata/toolkit
					http://oai.dlib.vt.edu/OAI/metadata/toolkit.xsd">
				<title>Open Journal Systems</title>
				<author>
					<name>Public Knowledge Project</name>
					<email>pkp.contact@gmail.com</email>
				</author>
				<version>3.1.0.0</version>
				<URL>http://pkp.sfu.ca/ojs/</URL>
			</toolkit>
		</description>
	</Identify>
</OAI-PMH>

------- End of XML Response -------
Test Result : FAIL!
**** [ERROR] XML Schema validation failed

(7) Skipping : ListIdentifiers (resumptionToken)
This test is being skipped because it cannot or should not be performed.

(8) Skipping : ListIdentifiers (resumptionToken, oai_dc)
This test is being skipped because it cannot or should not be performed.

(20) Testing : ListIdentifiers (oai_dc, from YYYY-MM-DDThh:mm:ssZ)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&from=2001-01-01T00:00:00Z
------ Start of XML Response ------
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="http://psicodebate.dpgpsifpm.com.br/lib/pkp/xml/oai2.xsl" ?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/
		http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
	<responseDate>2017-11-13T17:11:11Z</responseDate>
	<request verb="ListIdentifiers" metadataPrefix="oai_dc" from="2001-01-01T00:00:00Z">http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai</request>
	<ListIdentifiers>
		<header>
			<identifier>oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3</identifier>
			<datestamp>2017-11-05T20:25:26Z</datestamp>
			<setSpec>periodico:ART</setSpec>
			<setSpec>driver</setSpec>
		</header>

IT TESTS ALL ARTICLES HERE, DATA EXTRACTED DUE TO CARACTERS LIMIT

	</ListIdentifiers>
</OAI-PMH>

------- End of XML Response -------
Test Result : FAIL!
**** [ERROR] Error tag expected but not found : badArgument

(21) Testing : ListIdentifiers (oai_dc, from YYYY)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&from=2001
Test Result : OK

(22) Testing : ListMetadataFormats (identifier)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListMetadataFormats&identifier=oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3
Test Result : OK
---- [ Sample Metadata Format = oai_marc ]

(23) Testing : ListMetadataFormats (illegal_id)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListMetadataFormats&identifier=really_wrong_id
Test Result : OK

(24) Testing : GetRecord (identifier, metadataPrefix)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=GetRecord&identifier=oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3&metadataPrefix=oai_marc
------ Response from Xerces Schema Validation ------
[Error] re.7Xm347:22:43: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:22:43: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:22:43: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:22:43: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.7Xm347:22:43: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.7Xm347:22:43: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.7Xm347:23:25: cvc-pattern-valid: Value '$a' is not facet-valid with respect to pattern '[0-9a-z]' for type 'subfieldType'.
[Error] re.7Xm347:23:25: cvc-attribute.3: The value '$a' of attribute 'label' on element 'subfield' is not valid with respect to its type, 'subfieldType'.
[Error] re.7Xm347:25:42: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:25:42: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:25:42: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:25:42: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.7Xm347:25:42: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.7Xm347:25:42: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.7Xm347:28:40: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:28:40: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:28:40: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:28:40: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.7Xm347:28:40: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.7Xm347:28:40: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.7Xm347:32:43: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:32:43: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:32:43: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:32:43: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.7Xm347:32:43: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.7Xm347:32:43: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.7Xm347:35:42: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:35:42: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:35:42: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:35:42: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.7Xm347:35:42: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.7Xm347:35:42: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.7Xm347:38:42: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:38:42: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:38:42: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:38:42: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.7Xm347:38:42: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.7Xm347:38:42: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.7Xm347:53:45: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:53:45: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:53:45: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:53:45: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.7Xm347:53:45: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.7Xm347:53:45: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.7Xm347:56:41: cvc-complex-type.2.4.a: Invalid content was found starting with element 'dataField'. One of '{"http://www.openarchives.org/OAI/1.1/oai_marc":varfield}' is expected.
[Error] re.7Xm347:61:42: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:61:42: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:61:42: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:61:42: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.7Xm347:61:42: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.7Xm347:61:42: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.7Xm347:64:41: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:64:41: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:64:41: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:64:41: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.7Xm347:64:41: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.7Xm347:64:41: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.7Xm347:68:40: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:68:40: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:68:40: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:68:40: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.7Xm347:68:40: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.7Xm347:68:40: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.7Xm347:72:40: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:72:40: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:72:40: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:72:40: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.7Xm347:72:40: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.7Xm347:72:40: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.7Xm347:77:40: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:77:40: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:77:40: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.7Xm347:77:40: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.7Xm347:77:40: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.7Xm347:77:40: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
/tmp/re.7Xm347: 702;20;1 ms (39 elems, 67 attrs, 0 spaces, 1754 chars)
------- End of Xerces Schema Validation Report  -------
------ Start of XML Response ------
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="http://psicodebate.dpgpsifpm.com.br/lib/pkp/xml/oai2.xsl" ?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/
		http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
	<responseDate>2017-11-13T17:11:20Z</responseDate>
	<request verb="GetRecord" identifier="oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3" metadataPrefix="oai_marc">http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai</request>
	<GetRecord>
		<record>
			<header>
				<identifier>oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3</identifier>
				<datestamp>2017-11-05T20:25:26Z</datestamp>
				<setSpec>periodico:ART</setSpec>
				<setSpec>driver</setSpec>
			</header>
			<metadata>
<oai_marc status="c" type="a" level="m" encLvl="3" catForm="u"
	xmlns="http://www.openarchives.org/OAI/1.1/oai_marc" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.openarchives.org/OAI/1.1/oai_marc http://www.openarchives.org/OAI/1.1/oai_marc.xsd">
			<fixfield id="008">"150411 2015                        eng  "</fixfield>
				<varfield tag="022" ind1="#" ind2="#">
			<subfield label="$a">2446-922X</subfield>
		</varfield>
			<varfield tag="042" ind1=" " ind2=" ">
		<subfield label="a">dc</subfield>
	</varfield>
	<varfield tag="245" ind1="0" ind2="0">
		<subfield label="a">A CONTEMPORANEIDADE ACERCA DA ADOLESCÊNCIA E A SEXUALIDADE</subfield>
	</varfield>

				<varfield tag="720" ind1="1" ind2=" ">
			<subfield label="a">Silva, Tatiane Cristina da</subfield>
														</varfield>
			<varfield tag="720" ind1="1" ind2=" ">
			<subfield label="a">Mendes, Delza Ferreira</subfield>
														</varfield>
			<varfield tag="520" ind1=" " ind2=" ">
		<subfield label="a">
A sexualidade na adolescência contemporânea apresenta diversas configurações as quais
 levam o adolescente a permanecer na ilusão de imagens, incentivando-o a vivenciar a
 sexualidade no corpo e não em si por completo. O objetivo da pesquisa foi compreender como
 o adolescente contemporâneo lida com a sexualidade, e para isto foi utilizada como
 metodologia a revisão de literatura. O estudo apontou que a sexualidade é um dispositivo
 histórico e cultural, a qual tem características diferenciadas em cada sociedade. Evidenciou
 também que a adolescência é um período de transição caracterizada por diversas perdas e
 significativas mudanças, visando a construção do sujeito. E ficou claro ainda que a
 sexualidade na adolescência conceitua se a partir da relação do adolescente com o próprio
 corpo, com a mente e no relacionamento com os outros. Compreende se que o adolescente
 contemporâneo apresenta diversos dilemas, sendo assim a psicologia tem o papel de auxilialo no enfrentamento de barreiras.
</subfield>
	</varfield>
						<varfield tag="260" ind1=" " ind2=" ">
		<subfield label="b">Faculdade Patos de Minas</subfield>
	</varfield>
	<dataField tag="260" ind1=" " ind2=" ">
		<subfield label="c">2015-04-11 00:00:00</subfield>
	</dataField>

		
			<varfield tag="856" ind1=" " ind2=" ">
			<subfield label="q">application/pdf</subfield>
		</varfield>
		<varfield tag="856" ind1="4" ind2="0">
		<subfield label="u">http://psicodebate.dpgpsifpm.com.br/index.php/periodico/article/view/V1A1</subfield>
	</varfield>

	<varfield tag="786" ind1="0" ind2=" ">
		<subfield label="n">Psicologia e Saúde em debate; v. 1 n. 1 (2015)</subfield>
	</varfield>

	<varfield tag="546" ind1=" " ind2=" ">
		<subfield label="a">por</subfield>
	</varfield>

	
	<varfield tag="540" ind1=" " ind2=" ">
		<subfield label="a">##submission.copyrightStatement##</subfield>
	</varfield>
</oai_marc>			</metadata>
		</record>
	</GetRecord>
</OAI-PMH>

------- End of XML Response -------
Test Result : FAIL!
**** [ERROR] XML Schema validation failed

(25) Testing : GetRecord (identifier, oai_dc)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=GetRecord&identifier=oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3&metadataPrefix=oai_dc
Test Result : OK

(26) Testing : GetRecord (identifier)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=GetRecord&identifier=oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3
Test Result : OK

(27) Testing : GetRecord (identifier, illegal_mdp)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=GetRecord&identifier=oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3&metadataPrefix=really_wrong_mdp
Test Result : OK

(28) Testing : GetRecord (oai_dc)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=GetRecord&metadataPrefix=oai_dc
Test Result : OK

(29) Testing : GetRecord (illegal_id, oai_dc)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=GetRecord&identifier=really_wrong_id&metadataPrefix=oai_dc
Test Result : OK

(30) Testing : GetRecord (invalid_id, oai_dc)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=GetRecord&identifier=invalid\"id&metadataPrefix=oai_dc
Test Result : OK

(31) Testing : ListRecords (oai_dc, from/until)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListRecords&metadataPrefix=oai_dc&from=2000-01-01&until=2000-01-01
Test Result : OK

(32) Skipping : ListRecords (resumptionToken)
This test is being skipped because it cannot or should not be performed.

(33) Testing : ListRecords (metadataPrefix, from/until)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListRecords&metadataPrefix=oai_marc&from=2000-01-01&until=2000-01-01
Test Result : OK

(34) Testing : ListRecords (oai_dc, illegal_set, illegal_from/until)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListRecords&metadataPrefix=oai_dc&set=really_wrong_set&from=some_random_date&until=some_random_date
Test Result : OK

(35) Testing : ListRecords
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListRecords
Test Result : OK

(36) Testing : ListRecords (oai_dc, from granularity != until granularity)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListRecords&metadataPrefix=oai_dc&from=2001-01-01&until=2002-01-01T00:00:00Z
Test Result : OK

(37) Testing : ListRecords (oai_dc, until before earliestDatestamp)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListRecords&metadataPrefix=oai_dc&until=1969-01-01T00:00:00Z
Test Result : OK

(38) Testing : ListRecords (oai_dc)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListRecords&metadataPrefix=oai_dc
Test Result : OK

(39) Testing : ListRecords (illegal_resumptiontoken)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListRecords&resumptionToken=junktoken
Test Result : OK

(40) Testing : ListIdentifiers (oai_dc, set)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=periodico
Test Result : OK

(41) Testing : GetRecord (identifier, oai_dc)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=GetRecord&identifier=oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3&metadataPrefix=oai_dc
Test Result : OK
---- [ Found setSpec in header ]

(42) Testing : IllegalVerb
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=IllegalVerb
Test Result : OK


---- Total Errors : 3
4

There are several different warnings in those messages:

  • www.openarchives.org schema not accessible (it seems like the whole site is down right now)
  • resumptionToken skipped (you don’t have enough records to be split up into multiple requests with resumption)
  • a missing “badArgument” error tag (I’m not sure what this is referencing)
  • invalid attributes for the oai_marc export (this we may need to look at as a different issue).
5

Hi @Hugo_Melo

I think we have two bugs: OAI record datestamp · Issue #3051 · pkp/pkp-lib · GitHub and consider URL encoding for oai identifiers · Issue #3052 · pkp/pkp-lib · GitHub.
If you apply these changes those major failures should not occur any more:
– pkp/pkp-lib#3051 fix oai record datestamp by bozana · Pull Request #1685 · pkp/ojs · GitHub
– pkp/pkp-lib#3052 consider url encoding for oai record identifiers by bozana · Pull Request #1687 · pkp/ojs · GitHub

Maybe you can wait just a little bit longer, till Alec have seen those changes and they are finally merged…

Best,
Bozana

6

Well @bozana, I did those changes and the errors seems the same when tested at Open Archives Initiative - Repository Explorer:

(1) Testing : Identify
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=Identify
------ Response from Xerces Schema Validation ------
[Warning] re.CdMIT9:24:63: schema_reference.4: Failed to read schema document 'http://www.openarchives.org/OAI/2.0/oai-identifier.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
[Error] re.CdMIT9:24:63: cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'oai-identifier'.
[Warning] re.CdMIT9:25:13: schema_reference.4: Failed to read schema document 'http://www.openarchives.org/OAI/2.0/oai-identifier.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
[Warning] re.CdMIT9:26:27: schema_reference.4: Failed to read schema document 'http://www.openarchives.org/OAI/2.0/oai-identifier.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
[Warning] re.CdMIT9:27:16: schema_reference.4: Failed to read schema document 'http://www.openarchives.org/OAI/2.0/oai-identifier.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
[Warning] re.CdMIT9:28:23: schema_reference.4: Failed to read schema document 'http://www.openarchives.org/OAI/2.0/oai-identifier.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
/tmp/re.CdMIT9: 2678;7;0 ms (27 elems, 9 attrs, 0 spaces, 552 chars)
------- End of Xerces Schema Validation Report  -------
------ Start of XML Response ------
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="http://psicodebate.dpgpsifpm.com.br/lib/pkp/xml/oai2.xsl" ?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/
		http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
	<responseDate>2017-11-14T12:46:57Z</responseDate>
	<request verb="Identify">http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai</request>
	<Identify>
		<repositoryName>Psicologia e Saúde em debate</repositoryName>
		<baseURL>http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai</baseURL>
		<protocolVersion>2.0</protocolVersion>
		<adminEmail>editor@***.com.br</adminEmail>
		<earliestDatestamp>2017-11-05T20:25:26Z</earliestDatestamp>
		<deletedRecord>persistent</deletedRecord>
		<granularity>YYYY-MM-DDThh:mm:ssZ</granularity>
		<compression>gzip</compression>
		<compression>deflate</compression>
		<description>
			<oai-identifier
				xmlns="http://www.openarchives.org/OAI/2.0/oai-identifier"
				xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
				xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai-identifier
					http://www.openarchives.org/OAI/2.0/oai-identifier.xsd">
				<scheme>oai</scheme>
				<repositoryIdentifier>ojs2.psicodebate.dpgpsifpm.com.br</repositoryIdentifier>
				<delimiter>:</delimiter>
				<sampleIdentifier>oai:ojs2.psicodebate.dpgpsifpm.com.br:article/1</sampleIdentifier>
			</oai-identifier>
		</description>
		<description>
			<toolkit
				xmlns="http://oai.dlib.vt.edu/OAI/metadata/toolkit"
				xsi:schemaLocation="http://oai.dlib.vt.edu/OAI/metadata/toolkit
					http://oai.dlib.vt.edu/OAI/metadata/toolkit.xsd">
				<title>Open Journal Systems</title>
				<author>
					<name>Public Knowledge Project</name>
					<email>pkp.contact@gmail.com</email>
				</author>
				<version>3.1.0.0</version>
				<URL>http://pkp.sfu.ca/ojs/</URL>
			</toolkit>
		</description>
	</Identify>
</OAI-PMH>

------- End of XML Response -------
Test Result : FAIL!
**** [ERROR] XML Schema validation failed 


(20) Testing : ListIdentifiers (oai_dc, from YYYY-MM-DDThh:mm:ssZ)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&from=2001-01-01T00:00:00Z
------ Start of XML Response ------
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="http://psicodebate.dpgpsifpm.com.br/lib/pkp/xml/oai2.xsl" ?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/
		http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
	<responseDate>2017-11-14T12:47:39Z</responseDate>
	<request verb="ListIdentifiers" metadataPrefix="oai_dc" from="2001-01-01T00:00:00Z">http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai</request>
	<ListIdentifiers>
		<header>
			<identifier>oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3</identifier>
			<datestamp>2017-11-12T21:01:50Z</datestamp>
			<setSpec>periodico:ART</setSpec>
			<setSpec>driver</setSpec>
		</header>

ALL TESTS IN HERE

</ListIdentifiers>
</OAI-PMH>

------- End of XML Response -------
Test Result : FAIL!
**** [ERROR] Error tag expected but not found : badArgument


(24) Testing : GetRecord (identifier, metadataPrefix)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=GetRecord&identifier=oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3&metadataPrefix=oai_marc
------ Response from Xerces Schema Validation ------
[Error] re.NvJffq:22:43: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:22:43: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:22:43: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:22:43: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.NvJffq:22:43: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.NvJffq:22:43: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.NvJffq:23:25: cvc-pattern-valid: Value '$a' is not facet-valid with respect to pattern '[0-9a-z]' for type 'subfieldType'.
[Error] re.NvJffq:23:25: cvc-attribute.3: The value '$a' of attribute 'label' on element 'subfield' is not valid with respect to its type, 'subfieldType'.
[Error] re.NvJffq:25:42: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:25:42: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:25:42: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:25:42: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.NvJffq:25:42: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.NvJffq:25:42: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.NvJffq:28:40: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:28:40: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:28:40: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:28:40: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.NvJffq:28:40: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.NvJffq:28:40: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.NvJffq:32:43: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:32:43: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:32:43: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:32:43: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.NvJffq:32:43: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.NvJffq:32:43: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.NvJffq:35:42: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:35:42: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:35:42: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:35:42: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.NvJffq:35:42: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.NvJffq:35:42: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.NvJffq:38:42: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:38:42: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:38:42: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:38:42: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.NvJffq:38:42: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.NvJffq:38:42: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.NvJffq:53:45: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:53:45: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:53:45: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:53:45: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.NvJffq:53:45: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.NvJffq:53:45: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.NvJffq:56:41: cvc-complex-type.2.4.a: Invalid content was found starting with element 'dataField'. One of '{"http://www.openarchives.org/OAI/1.1/oai_marc":varfield}' is expected.
[Error] re.NvJffq:61:42: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:61:42: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:61:42: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:61:42: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.NvJffq:61:42: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.NvJffq:61:42: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.NvJffq:64:41: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:64:41: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:64:41: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:64:41: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.NvJffq:64:41: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.NvJffq:64:41: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.NvJffq:68:40: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:68:40: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:68:40: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:68:40: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.NvJffq:68:40: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.NvJffq:68:40: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.NvJffq:72:40: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:72:40: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:72:40: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:72:40: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.NvJffq:72:40: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.NvJffq:72:40: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.NvJffq:77:40: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:77:40: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:77:40: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.NvJffq:77:40: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.NvJffq:77:40: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.NvJffq:77:40: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
/tmp/re.NvJffq: 589;20;0 ms (39 elems, 67 attrs, 0 spaces, 1754 chars)
------- End of Xerces Schema Validation Report  -------
------ Start of XML Response ------
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="http://psicodebate.dpgpsifpm.com.br/lib/pkp/xml/oai2.xsl" ?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/
		http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
	<responseDate>2017-11-14T12:47:47Z</responseDate>
	<request verb="GetRecord" identifier="oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3" metadataPrefix="oai_marc">http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai</request>
	<GetRecord>
		<record>
			<header>
				<identifier>oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3</identifier>
				<datestamp>2017-11-12T21:01:50Z</datestamp>
				<setSpec>periodico:ART</setSpec>
				<setSpec>driver</setSpec>
			</header>
			<metadata>
<oai_marc status="c" type="a" level="m" encLvl="3" catForm="u"
	xmlns="http://www.openarchives.org/OAI/1.1/oai_marc" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.openarchives.org/OAI/1.1/oai_marc http://www.openarchives.org/OAI/1.1/oai_marc.xsd">
			<fixfield id="008">"150411 2015                        eng  "</fixfield>
				<varfield tag="022" ind1="#" ind2="#">
			<subfield label="$a">2446-922X</subfield>
		</varfield>
			<varfield tag="042" ind1=" " ind2=" ">
		<subfield label="a">dc</subfield>
	</varfield>
	<varfield tag="245" ind1="0" ind2="0">
		<subfield label="a">A CONTEMPORANEIDADE ACERCA DA ADOLESCÊNCIA E A SEXUALIDADE</subfield>
	</varfield>

				<varfield tag="720" ind1="1" ind2=" ">
			<subfield label="a">Silva, Tatiane Cristina da</subfield>
														</varfield>
			<varfield tag="720" ind1="1" ind2=" ">
			<subfield label="a">Mendes, Delza Ferreira</subfield>
														</varfield>
			<varfield tag="520" ind1=" " ind2=" ">
		<subfield label="a">
A sexualidade na adolescência contemporânea apresenta diversas configurações as quais
 levam o adolescente a permanecer na ilusão de imagens, incentivando-o a vivenciar a
 sexualidade no corpo e não em si por completo. O objetivo da pesquisa foi compreender como
 o adolescente contemporâneo lida com a sexualidade, e para isto foi utilizada como
 metodologia a revisão de literatura. O estudo apontou que a sexualidade é um dispositivo
 histórico e cultural, a qual tem características diferenciadas em cada sociedade. Evidenciou
 também que a adolescência é um período de transição caracterizada por diversas perdas e
 significativas mudanças, visando a construção do sujeito. E ficou claro ainda que a
 sexualidade na adolescência conceitua se a partir da relação do adolescente com o próprio
 corpo, com a mente e no relacionamento com os outros. Compreende se que o adolescente
 contemporâneo apresenta diversos dilemas, sendo assim a psicologia tem o papel de auxilialo no enfrentamento de barreiras.
</subfield>
	</varfield>
						<varfield tag="260" ind1=" " ind2=" ">
		<subfield label="b">Faculdade Patos de Minas</subfield>
	</varfield>
	<dataField tag="260" ind1=" " ind2=" ">
		<subfield label="c">2015-04-11 00:00:00</subfield>
	</dataField>

		
			<varfield tag="856" ind1=" " ind2=" ">
			<subfield label="q">application/pdf</subfield>
		</varfield>
		<varfield tag="856" ind1="4" ind2="0">
		<subfield label="u">http://psicodebate.dpgpsifpm.com.br/index.php/periodico/article/view/V1A1</subfield>
	</varfield>

	<varfield tag="786" ind1="0" ind2=" ">
		<subfield label="n">Psicologia e Saúde em debate; v. 1 n. 1 (2015)</subfield>
	</varfield>

	<varfield tag="546" ind1=" " ind2=" ">
		<subfield label="a">por</subfield>
	</varfield>

	
	<varfield tag="540" ind1=" " ind2=" ">
		<subfield label="a">##submission.copyrightStatement##</subfield>
	</varfield>
</oai_marc>			</metadata>
		</record>
	</GetRecord>
</OAI-PMH>

------- End of XML Response -------
Test Result : FAIL!
**** [ERROR] XML Schema validation failed
7

I am still unable to connect to openarchives.org, which would be a cause of the error in (1).

I remain uncertain why a response of “Error tag expected but not found : badArgument” is expected for (20).

For (24), without seeing the schema at openarchives.org, I can’t be sure what is going on with the oai_marc format, but the sample schema at NDLTD suggest that the attributes should be i1, i2, and id for ind1, ind2, and tag:
Metadata - ndltd
If so, this has been a bug even on OJS 2.x.

Your latest report seems to indicate that @bozana’s fixes resolved the identifier parsing.

8

@Hugo_Melo

Hmmm… what are you exactly doing when you get that errors – could you explain it step by step, so that I can do/test it as well? – All those errors are super strange :slight_smile:

Note, that one of my earlier fixes changed: instead of applying this change: pkp/pkp-lib#3052 consider url encoding for oai record identifiers by bozana · Pull Request #1687 · pkp/ojs · GitHub, you would need to apply this change: pkp/pkp-lib#3052 fix wrong parameter reference by bozana · Pull Request #3059 · pkp/pkp-lib · GitHub.
This has noting to do with these last strange errors you have gotten… but with the first one you have posted here… :slight_smile:

Best,
Bozana

9

Alright, I enter the Open Archives Initiative - Repository Explorer (http://re.cs.uct.ac.za/) put my oai url and click “Test the specified/selected baseURL” then after a few minutes it shows the results of testing.
I reverted the pkp/pkp-lib#3052 consider url encoding for oai record identifiers by bozana · Pull Request #1687 · pkp/ojs · GitHub and applied pkp/pkp-lib#3052 fix wrong parameter reference by bozana · Pull Request #3059 · pkp/pkp-lib · GitHub.

Here are the results:

(1) Testing : Identify
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=Identify
Test Result : OK
---- [ Repository Name = Psicologia e Saúde em debate ]
---- [ Protocol Version = 2.0 ]
---- [ Base URL = http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai ]
---- [ Admin Email = editor@dpgpsifpm.com.br ]
---- [ Granularity = YYYY-MM-DDThh:mm:ssZ ]
---- [ Earliest Datestamp = 2017-11-05T20:25:26Z ]

(20) Testing : ListIdentifiers (oai_dc, from YYYY-MM-DDThh:mm:ssZ)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&from=2001-01-01T00:00:00Z
Test Result : OK

(24) Testing : GetRecord (identifier, metadataPrefix)
URL : http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai?verb=GetRecord&identifier=oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3&metadataPrefix=oai_marc
------ Response from Xerces Schema Validation ------
[Error] re.ytT0hV:22:43: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:22:43: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:22:43: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:22:43: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.ytT0hV:22:43: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.ytT0hV:22:43: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.ytT0hV:23:25: cvc-pattern-valid: Value '$a' is not facet-valid with respect to pattern '[0-9a-z]' for type 'subfieldType'.
[Error] re.ytT0hV:23:25: cvc-attribute.3: The value '$a' of attribute 'label' on element 'subfield' is not valid with respect to its type, 'subfieldType'.
[Error] re.ytT0hV:25:42: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:25:42: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:25:42: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:25:42: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.ytT0hV:25:42: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.ytT0hV:25:42: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.ytT0hV:28:40: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:28:40: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:28:40: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:28:40: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.ytT0hV:28:40: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.ytT0hV:28:40: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.ytT0hV:32:43: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:32:43: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:32:43: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:32:43: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.ytT0hV:32:43: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.ytT0hV:32:43: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.ytT0hV:35:42: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:35:42: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:35:42: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:35:42: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.ytT0hV:35:42: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.ytT0hV:35:42: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.ytT0hV:38:42: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:38:42: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:38:42: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:38:42: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.ytT0hV:38:42: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.ytT0hV:38:42: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.ytT0hV:53:45: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:53:45: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:53:45: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:53:45: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.ytT0hV:53:45: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.ytT0hV:53:45: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.ytT0hV:56:41: cvc-complex-type.2.4.a: Invalid content was found starting with element 'dataField'. One of '{"http://www.openarchives.org/OAI/1.1/oai_marc":varfield}' is expected.
[Error] re.ytT0hV:61:42: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:61:42: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:61:42: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:61:42: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.ytT0hV:61:42: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.ytT0hV:61:42: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.ytT0hV:64:41: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:64:41: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:64:41: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:64:41: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.ytT0hV:64:41: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.ytT0hV:64:41: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.ytT0hV:68:40: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:68:40: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:68:40: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:68:40: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.ytT0hV:68:40: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.ytT0hV:68:40: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.ytT0hV:72:40: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:72:40: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:72:40: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:72:40: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.ytT0hV:72:40: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.ytT0hV:72:40: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
[Error] re.ytT0hV:77:40: cvc-complex-type.3.2.2: Attribute 'tag' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:77:40: cvc-complex-type.3.2.2: Attribute 'ind1' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:77:40: cvc-complex-type.3.2.2: Attribute 'ind2' is not allowed to appear in element 'varfield'.
[Error] re.ytT0hV:77:40: cvc-complex-type.4: Attribute 'id' must appear on element 'varfield'.
[Error] re.ytT0hV:77:40: cvc-complex-type.4: Attribute 'i1' must appear on element 'varfield'.
[Error] re.ytT0hV:77:40: cvc-complex-type.4: Attribute 'i2' must appear on element 'varfield'.
/tmp/re.ytT0hV: 742;8;0 ms (39 elems, 67 attrs, 0 spaces, 1754 chars)
------- End of Xerces Schema Validation Report  -------
------ Start of XML Response ------
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="http://psicodebate.dpgpsifpm.com.br/lib/pkp/xml/oai2.xsl" ?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/
		http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
	<responseDate>2017-11-14T16:52:40Z</responseDate>
	<request verb="GetRecord" identifier="oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3" metadataPrefix="oai_marc">http://psicodebate.dpgpsifpm.com.br/index.php/periodico/oai</request>
	<GetRecord>
		<record>
			<header>
				<identifier>oai:ojs2.psicodebate.dpgpsifpm.com.br:article/3</identifier>
				<datestamp>2017-11-12T21:01:50Z</datestamp>
				<setSpec>periodico:ART</setSpec>
				<setSpec>driver</setSpec>
			</header>
			<metadata>
<oai_marc status="c" type="a" level="m" encLvl="3" catForm="u"
	xmlns="http://www.openarchives.org/OAI/1.1/oai_marc" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.openarchives.org/OAI/1.1/oai_marc http://www.openarchives.org/OAI/1.1/oai_marc.xsd">
			<fixfield id="008">"150411 2015                        eng  "</fixfield>
				<varfield tag="022" ind1="#" ind2="#">
			<subfield label="$a">2446-922X</subfield>
		</varfield>
			<varfield tag="042" ind1=" " ind2=" ">
		<subfield label="a">dc</subfield>
	</varfield>
	<varfield tag="245" ind1="0" ind2="0">
		<subfield label="a">A CONTEMPORANEIDADE ACERCA DA ADOLESCÊNCIA E A SEXUALIDADE</subfield>
	</varfield>

				<varfield tag="720" ind1="1" ind2=" ">
			<subfield label="a">Silva, Tatiane Cristina da</subfield>
														</varfield>
			<varfield tag="720" ind1="1" ind2=" ">
			<subfield label="a">Mendes, Delza Ferreira</subfield>
														</varfield>
			<varfield tag="520" ind1=" " ind2=" ">
		<subfield label="a">
A sexualidade na adolescência contemporânea apresenta diversas configurações as quais
 levam o adolescente a permanecer na ilusão de imagens, incentivando-o a vivenciar a
 sexualidade no corpo e não em si por completo. O objetivo da pesquisa foi compreender como
 o adolescente contemporâneo lida com a sexualidade, e para isto foi utilizada como
 metodologia a revisão de literatura. O estudo apontou que a sexualidade é um dispositivo
 histórico e cultural, a qual tem características diferenciadas em cada sociedade. Evidenciou
 também que a adolescência é um período de transição caracterizada por diversas perdas e
 significativas mudanças, visando a construção do sujeito. E ficou claro ainda que a
 sexualidade na adolescência conceitua se a partir da relação do adolescente com o próprio
 corpo, com a mente e no relacionamento com os outros. Compreende se que o adolescente
 contemporâneo apresenta diversos dilemas, sendo assim a psicologia tem o papel de auxilialo no enfrentamento de barreiras.
</subfield>
	</varfield>
						<varfield tag="260" ind1=" " ind2=" ">
		<subfield label="b">Faculdade Patos de Minas</subfield>
	</varfield>
	<dataField tag="260" ind1=" " ind2=" ">
		<subfield label="c">2015-04-11 00:00:00</subfield>
	</dataField>

		
			<varfield tag="856" ind1=" " ind2=" ">
			<subfield label="q">application/pdf</subfield>
		</varfield>
		<varfield tag="856" ind1="4" ind2="0">
		<subfield label="u">http://psicodebate.dpgpsifpm.com.br/index.php/periodico/article/view/V1A1</subfield>
	</varfield>

	<varfield tag="786" ind1="0" ind2=" ">
		<subfield label="n">Psicologia e Saúde em debate; v. 1 n. 1 (2015)</subfield>
	</varfield>

	<varfield tag="546" ind1=" " ind2=" ">
		<subfield label="a">por</subfield>
	</varfield>

	
	<varfield tag="540" ind1=" " ind2=" ">
		<subfield label="a">##submission.copyrightStatement##</subfield>
	</varfield>
</oai_marc>			</metadata>
		</record>
	</GetRecord>
</OAI-PMH>

------- End of XML Response -------
Test Result : FAIL!
**** [ERROR] XML Schema validation failed

(1) and (20) is fixed by the last patch.

Thank you @bozana!

10

Crazy… The schema http://www.openarchives.org/OAI/1.1/oai_marc.xsd really does not allow those attributes, but instead id, i1 and i2 :open_mouth:
Apparently the OAI format changed in OJS 2.4.6: the new template record.tpl came (s. ojs/record.tpl at ojs-stable-2_4_6 · pkp/ojs · GitHub) instead of the class ojs/OAIMetadataFormat_MARC.inc.php at ojs-stable-2_4_5 · pkp/ojs · GitHub.
I opened an GitHub Issue: wrong element attributes in oai_marc · Issue #3062 · pkp/pkp-lib · GitHub. Lets see if Alec will know the story behind it…

:open_mouth: Bozana

11

Hello guys.
I’ve made a second test to register at OVAL (http://oval.base-search.net/). The result is as follow:

Validation Results
Repository Information
Name:
Psicologia e Saúde em debate
Admin:
editor@dpgpsifpm.com.br
Server communication
 SUCCESS: Server supports both GET and POST requests.
 SUCCESS: OAI-PMH version is 2.0
XML Validation
 SUCCESS: Identify response well-formed and valid.
 SUCCESS: ListRecords response well-formed and valid.
Harvesting
 SUCCESS: Deleting strategy is "persistent"
 SUCCESS: ListRecords batch size is 100.
 SUCCESS: Resumption requests work
 SUCCESS: Resumption token lasts 23 hours.
 SUCCESS: completeListSize: 101 records.
 SUCCESS: Incremental harvesting (day granularity) of ListRecords works.
 ERROR: No incremental (full granularity) harvesting of ListRecords. Harvest for reference date 2017-11-05T20:28:09Z returned record with date 2017-11-05T20:29:17Z.
 SUCCESS: dc:language elements conform to ISO 639-3.
 SUCCESS: dc:date elements conform to ISO 8601.
 SUCCESS: Minimal DC elements (date, creator, identifier, type, title) are present.
12

Hmmm… I think we have one more bug, s. my question here: OAI record datestamp · Issue #3051 · pkp/pkp-lib · GitHub…
THANKS!!!

13

Good Morning @bozana. You have any news about the issue? I still getting that error:

ERROR: No incremental (day granularity) harvesting of ListRecords. Harvest for reference date 2017-11-15 returned record with date 2017-11-20.
ERROR: No incremental (full granularity) harvesting of ListRecords. Harvest for reference date 2017-11-15T13:34:06Z returned record with date 2017-11-20T15:26:36Z.

Thanx for helping me out!

14

Hi @Hugo_Melo

Did you apply this change: pkp/pkp-lib#3051 use GRATEST for OAI until date by bozana · Pull Request #1715 · pkp/ojs · GitHub ?

Thanks!
Bozana

15

No, I will test it right now!

16

Very nice @bozana!
Thx a lot!

Validation Results
Repository Information
Name:
Psicologia e Saúde em debate
Admin:
editor@dpgpsifpm.com.br
Server communication
SUCCESS: Server supports both GET and POST requests.
SUCCESS: OAI-PMH version is 2.0
XML Validation
SUCCESS: Identify response well-formed and valid.
SUCCESS: ListRecords response well-formed and valid.
Harvesting
SUCCESS: Deleting strategy is “persistent”
SUCCESS: ListRecords batch size is 100.
SUCCESS: Resumption requests work
SUCCESS: Resumption token lasts 23 hours.
SUCCESS: completeListSize: 101 records.
SUCCESS: Incremental harvesting (day granularity) of ListRecords works.
SUCCESS: Incremental harvesting (full granularity) of ListRecords works.
SUCCESS: dc:language elements conform to ISO 639-3.
SUCCESS: dc:date elements conform to ISO 8601.
SUCCESS: Minimal DC elements (date, creator, identifier, type, title) are present.

17

Hi @Hugo_Melo, glad to see/hear that! :clap: :slight_smile:

18

Server communication

SUCCESS: Server supports both GET and POST requests.

SUCCESS: OAI-PMH version is 2.0

XML Validation

SUCCESS: Identify response well-formed and valid.

ERROR: ListRecords response well-formed but invalid: Element ‘{XML Schema}element’, attribute ‘ref’: The QName value ‘{http://purl.org/dc/elements/1.1/}title’ does not resolve to a(n) element declaration., line 23

Harvesting

SUCCESS: Deleting strategy is “persistent”

UNVERIFIED: ListRecords batch size could not be checked: Only one batch.

UNVERIFIED: Resumption requests could not be checked: No resumptionToken found

SUCCESS: Incremental harvesting (day granularity) of ListRecords works.

SUCCESS: Incremental harvesting (full granularity) of ListRecords works.

SUCCESS: dc:language elements conform to ISO 639-3.

SUCCESS: dc:date elements conform to ISO 8601.

SUCCESS: Minimal DC elements (date, creator, identifier, type, title) are present.

Explanation of message categories:

  • INFO: Potentially interesting information
  • RECOMMENDATION: Deprecated protocol feature or content-related issue
  • WARNING: Protocol violation or malformed content data
  • ERROR: Serious protocol violation that will affect the harvesting process
  • UNVERIFIED: Feature could not be checked for some reason

Please help me out my listrecord is error

19

Hi all

We have already applied the change. In fact, OJS 3.3.0-3 has added the change, but we are still facing the same error message:

Server communication

SUCCESS: Server supports both GET and POST requests.
SUCCESS: OAI-PMH version is 2.0

XML Validation

SUCCESS: Identify response well-formed and valid.
ERROR: ListRecords response well-formed but invalid: Element ‘{XML Schema}element’, attribute ‘ref’: The QName value ‘{http://purl.org/dc/elements/1.1/}title’ does not resolve to a(n) element declaration., line 23

Harvesting

SUCCESS: Deleting strategy is “persistent”
UNVERIFIED: ListRecords batch size could not be checked: Only one batch.
UNVERIFIED: Resumption requests could not be checked: No resumptionToken found
SUCCESS: Incremental harvesting (day granularity) of ListRecords works.
SUCCESS: Incremental harvesting (full granularity) of ListRecords works.
SUCCESS: dc:language elements conform to ISO 639-3.
SUCCESS: dc:date elements conform to ISO 8601.
SUCCESS: Minimal DC elements (date, creator, identifier, type, title) are present.

Any idea about how to solve it?

Thanks in advance