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