Setup harvesting for the UCLA Library Licensed Data.
If you run:
curl -s "https://dataverse.ucla.edu/api/search?q=*&subtree=ucla-library-restricted" | jq '.data.items[] | {name: .name, global_id: .global_id}'
It only returns with the LARIAC files. From Gemini:
Why the OAI-PMH "Set" is different
The OAI-PMH Set (ucla_library_licensed_datasets) you looked at earlier is a "virtual collection" defined by the admins. It includes these items manually.
The Search API, however, follows the physical folder structure. Since COCA is "inside" the Text Mining folder, and the Text Mining folder is "inside" the Restricted folder, the search doesn't always recurse the way you'd expect unless you target the specific branch where they reside.
Setup harvesting for the UCLA Library Licensed Data.
If you run:
curl -s "https://dataverse.ucla.edu/api/search?q=*&subtree=ucla-library-restricted" | jq '.data.items[] | {name: .name, global_id: .global_id}'
It only returns with the LARIAC files. From Gemini:
Why the OAI-PMH "Set" is different
The OAI-PMH Set (ucla_library_licensed_datasets) you looked at earlier is a "virtual collection" defined by the admins. It includes these items manually.
The Search API, however, follows the physical folder structure. Since COCA is "inside" the Text Mining folder, and the Text Mining folder is "inside" the Restricted folder, the search doesn't always recurse the way you'd expect unless you target the specific branch where they reside.