Hi Rufus, Out of the box, DSpace's OAI-PMH interface will display all Communities & Collections as OAI "Sets". See for example the demo site: http://demo.dspace.org/oai/request?verb=ListSets
So, there's no need to customize OAI-PMH settings unless you find its default settings to be insufficient. I get the sense that most institutions leave OAI-PMH settings them as-is, except they might tweak the metadata "crosswalks" if they have added custom metadata fields that they want displayed different in OAI-PMH. The "Projects" you refer to in the OAI-PMH 2.0 docs are for more complex scenarios, specifically OpenAIRE or DRIVER (which no longer exists): https://wiki.duraspace.org/display/DSDOC5x/OAI+2.0+Server#OAI2.0Server-WhyOAI2.0? Some external projects like these require very specific metadata fields to be available in OAI-PMH, so OAI 2.0 provides a way to configure those separately from your default OAI configs. These projects end up displayed as separate "contexts" in OAI-PMH. See for example the demo site: http://demo.dspace.org/oai/ Again though, all of this is usually not necessary to touch or customize. The default settings often work perfectly fine. If you have a more advanced use case though, you are welcome to describe it on this list (or on the Tech Support list, dspace-tech), and we can give you more specific advice. Good luck, Tim ________________________________ From: [email protected] <[email protected]> on behalf of Rufus <[email protected]> Sent: Thursday, August 1, 2019 3:38 PM To: DSpace Community <[email protected]> Subject: [dspace-community] OAI2.0 interface for each project? Hi, I'm afraid I have not quite understood the functions of OAI 2.0. Please correct me, if I am wrong: provided the case my DSpace repository contains two communities. Could I treat each of my communities as a project and provide a separate OAI interface for it? Is it that what is meant by "defining an interface for each project?" Regards, Rufus -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/7898741a-6262-4da6-9f02-7492ef62b183%40googlegroups.com<https://groups.google.com/d/msgid/dspace-community/7898741a-6262-4da6-9f02-7492ef62b183%40googlegroups.com?utm_medium=email&utm_source=footer>. -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/DM5PR22MB0572A01F8948A3D0A02DF07FEDDE0%40DM5PR22MB0572.namprd22.prod.outlook.com.
