status of a record (can see the date/time and in-progress, as well as noting the existence of an error
(Laura W notes an issue with 'in-progress' and source record storage in Cornell's test database; changes are not being made in SRS)
Christie suggests that if there is ONLY one holdings and item, the instance updates quickly, but the more the holdings or items, the slower the delay)
Stephanie says this makes sense but that more work will need to be done to speed up this change)
references item posted in slack channel
Notes that records with errors in fixed fields can be loaded, but if changes are made, the bad fixed fields will not allow the record from being saved (in order to restrict bad fixed fields from disrupting data in SRS)
talked about issues of language codes
feedback from MSU on the delete icon ( required new release will highlight delete row in next release Q3)
saved button being grayed out (because no changes have been made - then some data change triggers the change to blue in order to save)
In the slide deck there is a slide per tenant. The idea is by using drag and drop of X's and numbers, then the library in an easy way can design it's preferred view.
Notes:
UChicago and public libraries want to add copy no.
Libraries might be able to arrange order of and could suppress some columns (to use that space for other information)
configurable at the tenant level (as noted in the google slides linked above)
Please also rank features Ann-Marie links to in the Implementers & Data Import Slack Channels