wishlist: relocatable buckets

[James Fournie]

When staff leave my institution or change roles, it would be nice to have a way so their buckets are moved to another account.

Shared buckets are nice, but you have to memorize the bucket IDs. It would be nice to have a way to either move the bucket to another account, or have org-owned buckets.

[Elaine Hardy (ehardy)]

+1 on both the ability to move buckets to another account and to have org owned buckets.

[John Merriam (jmerriam)]

Hello. I had posted a message to the dev list with some functions I had created to move or copy bib record and copy buckets. I had not noticed this ticket. Here is a link to that message:

http://libmail.georgialibraries.org/pipermail/open-ils-dev/2019-May/010751.html

We use these functions on the back end in the database to move or copy buckets for our libraries. Something like these functions could be used as the basis for integrating this type of functionality into the Evergreen UI.

I had posted that dev list message in case someone found them useful and possibly to start a discussion about this type of functionality. I didn't make a Git branch with them since I didn't know what the reaction would be, if I had duplicated functionality that already existed, or if there was a better way to do what I was doing (I am not an SQL expert). If any of the developers would like me to make a branch, let me know. I'm not sure exactly how you would like to see new functions laid out in a Git branch. If you want to take what I have done and use it as the basis for something better, please feel free to do so.