You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear developer,
I'm very grateful for your work here. It appears to be the easiest OAI-PMH server to setup and configure. I was able to setup everything and to create the records based on the example.xml file.
However, I'm facing few problems while trying to set the SetSpec property for each entry. I would like to move it to the correct header section of the OAI XML response (the header), but apparently whatever I write in the entry XML file goes in the metadata section of the response and the output of the ListSets verb is always:
The repository does not support sets.
Can you suggest the correct way to deal with this verb?
The text was updated successfully, but these errors were encountered:
Unfortuantely, as the README states, this currently doesn't support sets.
However, there is an experimental pull request adding support for sets. It's not feature-complete, but maybe you want to check it out anyway to get a general idea of how you could achieve set support.
Generally, I do not provide support for this any more (except for bugfixes), but started working on a completely new OAI-PMH service provider which also supports sets: opencultureconsulting/oai-pmh2. It's working, but I am still working on documentation.
Dear developer,
I'm very grateful for your work here. It appears to be the easiest OAI-PMH server to setup and configure. I was able to setup everything and to create the records based on the example.xml file.
However, I'm facing few problems while trying to set the SetSpec property for each entry. I would like to move it to the correct header section of the OAI XML response (the header), but apparently whatever I write in the entry XML file goes in the metadata section of the response and the output of the ListSets verb is always:
The repository does not support sets.
Can you suggest the correct way to deal with this verb?
The text was updated successfully, but these errors were encountered: