dev:browser_staff:patron_editor_reqs
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
dev:browser_staff:patron_editor_reqs [2015/04/13 18:58] – klussier | dev:browser_staff:patron_editor_reqs [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Re-write Patron Editor in AngularJS | + | ===== Re-write Patron Editor in AngularJS |
Line 15: | Line 15: | ||
- Users should be able to tab to the Save button from the last field in the form. | - Users should be able to tab to the Save button from the last field in the form. | ||
- A keyboard shortcut should also be available to save the form. | - A keyboard shortcut should also be available to save the form. | ||
- | - Example text should be provided for the following fields: date of birth, email address, all phone fields, and postal code. The default example text should honor the regexes | + | |
+ | | ||
- The user should NOT be able to change the barcode field directly. Instead, there should be a separate option the user must explicitly choose that allows the user to update the barcode. | - The user should NOT be able to change the barcode field directly. Instead, there should be a separate option the user must explicitly choose that allows the user to update the barcode. | ||
- When the barcode is updated, the old barcode should be set to inactive and not primary, and the new barcode set to active and primary. | - When the barcode is updated, the old barcode should be set to inactive and not primary, and the new barcode set to active and primary. | ||
Line 34: | Line 35: | ||
- add a message to the patron record with an invalid email or invalid phone alert. | - add a message to the patron record with an invalid email or invalid phone alert. | ||
- Adding a new email address or phone number to these patron records should clear the message from the record. | - Adding a new email address or phone number to these patron records should clear the message from the record. | ||
- | - An option should be available to add a secondary permission group to the user account. | + | - An option should be available to add a secondary permission group to the user account. |
- The interface should allow users to apply user statistical categories that have been configured for the workstation OU or a parent of the workstation OU. | - The interface should allow users to apply user statistical categories that have been configured for the workstation OU or a parent of the workstation OU. | ||
+ | - Any field documentation configured for the workstation OU should display as a hovertip for the corresponding field label. | ||
- The system should continue to identify possible duplicate patrons and display an alert if potential matches are found. The alert should provide a link allowing staff to open up a search results screen that retrieves potential matches. The system could continue to use the same logic as is currently used to identify potential duplicates, using the following fields as match points: | - The system should continue to identify possible duplicate patrons and display an alert if potential matches are found. The alert should provide a link allowing staff to open up a search results screen that retrieves potential matches. The system could continue to use the same logic as is currently used to identify potential duplicates, using the following fields as match points: | ||
- First and Last Name | - First and Last Name |
dev/browser_staff/patron_editor_reqs.1428965902.txt.gz · Last modified: 2022/02/10 13:34 (external edit)