bookops-cat / babel Goto Github PK

line 124 Funds.py
'Fund code and constrains' should be 'Fund code and constraints'

Any parenthesis entered by a user in a cart name could cause problems when there is a duplicate name - since the name has to be unique babel adds numbers in parenthesis to resolve the confli
Add entry validation on user input in ImportView

When list price is given and user wants to populate discount price it seems she should apply discount 0% to all records in the cart. This does not work - discount price still shows 0$

What's maximum number of characters a vendor code can have in Sierra, @Mfgloger ?

Test the resource editing widget in the cart (after validation is added #46)

coming back or clicking on different cart or changing system or profile should trigger reset of the summary text widget

A cart summary in CartsView displays incorrectly calculated number of titles.

When editing an individual grid and removing a location, pressing + button to add new row hides last row - it appears the new empty row is displayed on top of the last row.

Add validation especially for:

• ISBNs,
• UPC,
• prices
• date

for allowed length of data rely on sqlalchemy error msg to rollback and alert user

Records that must be transfered:

• funds
• vendors (cleanup needed - often vendor record has code of only one system)
• distributions/grids

Records not migrated:

• order records
• used wlo numbers

What else?

Copying a grid to a template allows overwriting of DistSet and DistGrid records when user enters a name of existing distribution.
A good way would be to alert the user that they are about to overwrite data.

It's possible to made changes to records after funds were applied which will invalidate data. Validation should include verification that all orders have correct funds.

allow adding new status codes in TableView

Add hovering description of a button to the TableView

When activated a "validation mode" will highlight (change background) boxes that are missing or have incorrect data. Only applicable to displayed records.

investigate structure of user_data db and see if it can be reused or should be created from scratch

Comboboxes' values should automatically update if a new value is entered into one of the tables, for example after adding a new fund or shelf code, new values should be added to comboboxes when user comes back to the cart

Find a way to speed up retrieval and display of a fund data. At the moment the operation takes 1-2 seconds.

• NYPL & BPL branch codes
• materials types
• selectors codes
• etc.

Babel should save user input before funds or globals are applied.

switching sheet template or creating a new one should reset mapping mask, otherwise the previous stays

use keyring to store securely DBs credentials in Windows credential manager

changing system while in cart does not serve any purpose, disable while user in the CartView.

Per Libbhy's request the CartView should provide a information on amount spend.
Datastore cart view can be used for that purpose.

Investigate and figure a path forward for records that failed validation, but were forcefully finalized by a user. What kind of order record MARC field they should have?
There are certain cases where we want user to be able to override validation and produce records (no funds for example for gift materials ).

log & display msg for user

traversing records sets in finalized carts triggers validation - no need.

• for manual & auto input of db credentials
• updates settings
• etc.

use an icon, or some other short label to indicate in the list that all orders in the cart have been linked.

User should be able to edit any resource data

When cart is finalized wlo numbers are assigned. They should be in a sequence.

add 'archived' status to cart records - they can be suppressed from CartsView;
when user sets status to archived she should confirm that's what she wants to happen so to minimize accidental suppression of carts;
in SettingsView add option to archive carts automatically if older than a year.

move distr name entrybox into the same column as dist list - this will allow to lift grids and locations giving them more space

in the CartView keep current should be the default value in global update boxes

Since most of the windows have similar if not the same sets of icons it make sense to create them once and share the references via app_data vehicle, similar to global variables such as system or profile. This will be more memory efficient.

develop Babel reporting tool showing various metrics (discuss with Libbhy and Alex)
examples:

• $ per fund in particular time period
• orders for particular language or vendor in specific time period
• fiscal year comparisons

When viewing data only all widgets should be inactive, only when adding new data or editing existing one input widgets should be enabled.

add filtering of carts by right click on the column header and selecting value from pop-up menu (this will save space)

add validation routines for branch, shelf, and qty comboboxes.

add a label that displays current number of branches and copies in a grid

prevent reassigning a new blanketPO when cart is saved (CartView)

edits to Resouce records / more tabs

In case of batch processing failure (for whatever reason) stat data should be reset to blank or showing errors instead of displaying the previous batch stats

develop search functionality similar to Babel 1

verify and correct if needed updating of cart update timestamp whenever any data is saved

Include wlo and oid numbers in the summary (first and last) for user's convenience.

develop a tool that searches Sierra and displays branches holding particular resource

Develop a validation mode which when turn on would highlight missing data in displayed records. This could be done in addition to regular validation of entire cart.

It would be great if users were able to apply via global update a particular grid to all orders in cart.

Datastore throws error with lengthy summaries because of table restrictions. Shorten or lessen restriction?