but its not worked for me, i’ve tried. please tell me what else you did to resolve the issue,
your reply shall be appreciated,
thanks in advance.
but its not worked for me, i’ve tried. please tell me what else you did to resolve the issue,
your reply shall be appreciated,
thanks in advance.
Respected @ asmecher Sir,
I’ve tried following points :
When i saw error from OCLC, i’ve changed domain from https to http
Point 1st didn’t work, so that i’ve have cleaned all the OJS and reinstalled back to same domain.
Again Point 1 and 2 didn’t work, so that i decided to install on different domain to check whether problem might be only with my domain.
All above points did not worked form me, so that i’ve checked all other related replies from PKP support and tried to check my oai to http://oval.base-search.net/
ERROR: Identify response well-formed but invalid: Element ‘{https://www.openarchives.org/OAI/2.0/}OAI-PMH’: No matching global declaration available for the validation root., line 6
ERROR: ListRecords response well-formed but invalid: Element ‘{https://www.openarchives.org/OAI/2.0/}OAI-PMH’: No matching global declaration available for the validation root., line 6
Kindly review the issue and help me.
Best regards
Rahul Jain
Hi @jain034567,
- When i saw error from OCLC, i’ve changed domain from https to http
Where specifically did you modify this?
Thanks,
Alec Smecher
Public Knowledge Project Team
I’d made changes into base url (i.e. base_url = “https://”) of config.inc.php file also changed the option into security setting force_ssl = On and force_login_ssl = On
tried to check http and Off setting for both ssl
thank you sir for your reply
regards
Hi @jain034567,
If you’re using OJS 3.1.2-0, you’ll need to apply Revert "#4466 oai links updated" · pkp/pkp-lib@0e21a53 · GitHub to resolve the problem. Note that as far as I’m aware the problem only affects validation tools like Wordcat’s OAI tester; it should not prevent anything from actually using the OAI interface.
Regards,
Alec Smecher
Public Knowledge Project Team
Respected sir,
There are 6 changes in above links of github, so do i need to replace with file or open all file and make changes, i’m not good in coding.
kindly guide me.
many many thanks
Hi @jain034567,
This is more a question about github and patch files than a question about OJS, but there are resources on the web about this (e.g. git - Apply github commit / pull request as a patch - Stack Overflow).
Regards,
Alec Smecher
Public Knowledge Project Team
Sir,
Are there files located inside https://sjindia.org/lib/pkp folder?
classes/oai/OAI.inc.php
plugins/oaiMetadataFormats/dc/PKPOAIMetadataFormatPlugin_DC.inc.php
plugins/oaiMetadataFormats/dc/PKPOAIMetadataFormat_DC.inc.php
tests/functional/oai/FunctionalOaiBaseTestCase.inc.php
xml/oai2.xsl
xml/onixFilter.xsl
so that i can change manually because it has one another location
Thanks and Regards
Respected @asmecher sir
There are two different paths to access these files, which one is correct?
1- / lib/pkp
2- /
Please guide me.
Thanks and regards
Hi @jain034567,
The patch is to the pkp-lib
repository, which lives inside lib/pkp
in your OJS installation.
Regards,
Alec Smecher
Public Knowledge Project Team
@asmecher
After I updated to OJS 3.1.2 (3/4 day ago) and just now I have realized that OAI-PMH is not harvesting any of my records.
https://journal.seisense.com/index.php/jom/oai
When I run the BASE OAI-PMH validator, It is giving me the following errors:
ERROR: Identify response well-formed but invalid: Element ‘{https://www.openarchives.org/OAI/2.0/}OAI-PMH’: No matching global declaration available for the validation root., line 6
ERROR: ListRecords response well-formed but invalid: Element ‘{https://www.openarchives.org/OAI/2.0/}OAI-PMH’: No matching global declaration available for the validation root., line 6
UNVERIFIED: Deleting strategy could not be checked: deletedRecord element not found.
UNVERIFIED: ListRecords batch size could not be checked: Only one batch.
Looking forward for a positive and prompt reply.
Thanks
Hi @seisense,
Did you try the solution posted above?
Regards,
Alec Smecher
Public Knowledge Project Team
I changed the config.inc.php file with the following only
force_ssl = On and force_login_ssl = On
but it did not work.
Do you want me to apply the patch?
Hi @seisense,
Yes, the patch described above is the solution I meant.
Regards,
Alec Smecher
Public Knowledge Project Team
Thanks @asmecher
I dont have much skills to apply patch automatically. Yet, I have applied the patch manually to five of the six files.
The one file which I am not able to change is
tests/functional/oai/FunctionalOaiBaseTestCase.inc.php
I am not able to find this test folder at all. Screenshot is attached of lib/pkp OJS installation of mine.
Thanks
Hi @seisense,
The tests are only in the github repository and are excluded from the .tar.gz
package when it is built. You should be OK to skip that one.
Regards,
Alec Smecher
Public Knowledge Project Team
@asmecher Great, But there is nothing changed as far as OAI-PMH is concerned. It is still not showing any records of my journal.
http://journal.seisense.com/index.php/jom/oai
The only changes are
XML Validation errors are gone now and under harvesting, first line is green as well.
Hi @seisense,
Is the OAI interface enabled in distribution settings?
Regards,
Alec Smecher
Public Knowledge Project Team
Hi @asmecher
Ooops, My mistake. Somehow overlooked this checkbox. I have check marked the box and now it is working.
Yet Base OAI-MPH Validator shows two fields as “unverified”.
SUCCESS: Server supports both GET and POST requests.
SUCCESS: OAI-PMH version is 2.0
SUCCESS: Identify response well-formed and valid.
SUCCESS: ListRecords response well-formed and valid.
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.
Is this the matter of concern?
Thanks for your continued support.