Comment 27 for bug 1750894

I tested the migration of workstation settings earlier today. I have a few bits of feedback for continuing my testing.

I confirmed that the Console displays a message when it moves settings to the server and when there isn't a matching setting type in the database. From the perspective of most end users, the migration will happen seamlessly.

I loaded lp1750894-ws-settings-on-server-squash1-grid-limits, but I'm not seeing the grid limits in the database. Bill, to be clear, when you say grid limits, you mean the number of rows to display per page, right? As far as I can tell, this setting is still being stored in local storage. I haven't seen any Console messages saying that it's been moved to the server when I had a pre-existing local storage setting, nor do I see any changes in the database when I set a new value in the checkin grid.

This was strange. I had a preexisting local storage value of true for eg.circ.checkin.clear_expired. When I used the checkin interface, this setting did not move to the database and there was no Console message saying that there wasn't a matching setting type. The checkin screen also didn't automatically default to clearing the holds shelf. However, when I then manually set this checkin modifier, the setting did get stored in the database and worked as expected when I subsequently retrieved the checkin interface. I didn't test any other checkin modifiers to see if they show the same behavior.

There were a few local storage settings I encountered that did not have an entry in config.workstation_setting_type, but probably should have one.

  * circ.checkout.strict_barcode - I think this was an oversight since every other strict barcode entry setting seems to be covered.
  * cat.holdings_show_empty_org - all checkboxes at the top of holdings view are covered except this one.
  * cat.copy.defaults
  * cat.printlabels.default_template and cat.printlabels.templates

Everything else looks great so far! Thanks Bill!