Extend bibliographic API to create/update/delete bibliographic sets
Currently, the only way you can interact with sets via API is to have permission to configuration read/write. This is unnecessarily broad - it allows the user to change integration profiles, update some mapping and configuration tables, and change location configurations.
The Bibliographic API needs to be extended to allow manipulation of bibliographic record sets. Anyone working with bibliographic records via API should be able to use sets as part of that workflow without also exposing configuration changes to the same API key.
1
vote