Hello - I have a local OAI repository that behaves normally - answers requests of all kinds, but the records in it are not in native dc format, rather they are formatted according to the ncs_item format from NSDL (affiliated with DLESE).

I have the following problem and two questions: When I enter my endpoint in the new feed record, I get the following errors:

* warning: strtr() [function.strtr]: The second argument is not an array in /var/www/html/[my sitename]>>/modules/syslog/syslog.module on line 112.
* OAI repository at url is not avaliable, please check URL is correct.

I've configured another feed using the 'file upload' fetcher and XML parser, and it creates new nodes (with 15 CCK fields) fine. I can browse to my OAI endpoint, no problem.

My two questions are 1) do I have to have only dc: records to use this module? and 2) any ideas why it doesn't see a valid OAI endpoint as valid?

Comments

StevenWill’s picture

StevenWill commented

I am guessing all your fields are defined under section IV.1 NSDL_DC metadata fields . Can you provide a link to your OAI endpoint.

Update: I located a oai enpoint at nsdl.org, http://nsdl.org/oai. This module does not currently support the nsdl_dc metadataPrefix, but a feature request with a patch ( http://drupal.org/node/1065452 ) has started that will add support for other metadataPrefix formats, in addition to oai_dc.

kgeographer’s picture

kgeographer commented

Thanks for the link to a very relevant patch and discussion. The NSDL prefix ncs_item: refers to a schema/framework based on nsdl_dc and used in their repository application; comm_anno: is another NSDL-supported format I'll use.
I will post my endpoint as soon as I've figured out how to secure the admin of this particular OAI software -- turning out to be non-trivial as they say...Also, I'm not set up to work with patches yet so that will take a little time to sort out.

janusman’s picture

janusman commented

@kgeographer: is it safe to say this is a duplicate of #1065452: Allow fetcher to specify among the possible metadata formats offered by the repository then?

janusman’s picture

janusman commented
Status: Active » Postponed (maintainer needs more info)

Need more info to know what's going on. The endpoint SHOULD be accepted as a source by feeds_oai_pmh module independently of the metadata formats it has available...

I tried http://nsdl.org/oai and it worked on my current D7 test environment.

kgeographer’s picture

kgeographer commented

Sorry for the delay -- I don't know why my OAI endpoint is recognized by other clients and not this module, but it doesn't matter, because without being able to parse non-DC formats the feed would do me no good. So yes, it duplicates the request towards the end of #1065452. I'm not in a position to try to adapt the XML parser, which works fine on files, so I've gone to plan B, where I retrieve files in non-dc: formats via a non-OAI api and import them that way. Thanks for following up though.

janusman’s picture

janusman commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)