Dear DSpace Community/Techies I am still on DSpace 5.x and leveraging on oai interface to sync DSpace metadata with WorldCat.
When I configure my repository oai profile in the OCLC Gateway, upon refreshing collection list, the generated list contains communities, sub-communities and collections - which is expected behavior. When I map/sync (with default list), the process results in duplication. Item instances are created for each community, subcommunity and collection in the tree. Is there a way I can disable communities and sub-communities from being exposed via oai ListSets? I have tried disabling communities and sub-communities from Gateway end but such changes are reversed at next "collection data REFRESH" since it is based on oai response from DSpace. Anyone who has found workaround for this sync workflow, kindly share some tips to exclude communities and subcommunities. Thanking you in anticipation Regards /Bravismore -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/PA4PR04MB7600F87344E7AA91BE6A4AFFC4A6A%40PA4PR04MB7600.eurprd04.prod.outlook.com.
