| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
About this checklist: To ensure a smooth transition to use DI - Update workflow, we need to maintain existing quickMARC behavior and ensure a seamless user experience for users. This checklist represents items that need to be verified before we move to DI - Update workflow. The Bibliographic/Holdings/Authority columns are where statuses of each action will be documented. Please update with additional checklist items.
| Checklist item | Bibliographic | Holdings | Authority | ||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Use job profile to edit quickMARC record | Support (Morning Glory) | Not support | Support (Morning Glory) | ||||||||||||||||||||||||||||||||||||||||||||
Show Last person to update record and Last updated date/time stamp - no different from today |
| Support (Morning Glory) | " " | Support (Morning Glory) | ||||||||||||||||||||||||||||||||||||||||||||
| Show quickMARC status | Do not support showing Error status it will only say Current Action item: We need to show Error status. In progress will no longer be applicable. Review how we handle derive with errors. | Do not support showing Error status it will only say Current Action item: We need to show Error status. In progress will no longer be applicable. Review how we handle derive with errors. | |||||||||||||||||||||||||||||||||||||||||||||
| Any changes to quickMARC display? | No | No | No | ||||||||||||||||||||||||||||||||||||||||||||
| Any impact to handling diacritics? | No | No | No | ||||||||||||||||||||||||||||||||||||||||||||
| Any impact for entering subfield delimiter $ | No | No | No | ||||||||||||||||||||||||||||||||||||||||||||
| Maintain existing quickMARC permissions. Any additional permissions required? | Backend needs to review. Frontend should have no changes BUT we should test.
| Backend needs to review. Frontend should have no changes BUT we should test.
| Backend needs to review. Frontend should have no changes BUT we should test.
| ||||||||||||||||||||||||||||||||||||||||||||
Enforce Optimistic Locking on mod-source-record-storage
|
Will also not send updates to mod-inventory-storage |
Will also not send updates to mod-inventory-storage |
Will also not send updates to mod-inventory-storage | ||||||||||||||||||||||||||||||||||||||||||||
| Maintain Move holdings from one instance to another behavior - this workflow updates 004 | N/A | Will need check - when change this flow. | N/A | ||||||||||||||||||||||||||||||||||||||||||||
| Maintain quickMARC ability to override field data protection | Should be implemented | Should be implemented | Should be implemented | ||||||||||||||||||||||||||||||||||||||||||||
| Performance: Make sure quickMARC updates are saved in less than 2 seconds and updates corresponding mod-inventory-storage record | Need to verify (may need PTF environment) | Need to verify (may need PTF environment) | |||||||||||||||||||||||||||||||||||||||||||||
Performance: Flow control to improve single-record updates
| Need to verify
| Need to verify
| Need to verify
| ||||||||||||||||||||||||||||||||||||||||||||
Maintain quickMARC error handling AND allow for future updates that differ from data import | Support | Support | Support | ||||||||||||||||||||||||||||||||||||||||||||
Maintain quickMARC rules validation AND allow for future updates that differ from data import
| Support | Support | Support | ||||||||||||||||||||||||||||||||||||||||||||
| Data import - Logs What is it about? | |||||||||||||||||||||||||||||||||||||||||||||||
| Any impact to mod-inventory-storage? | No | No | No | ||||||||||||||||||||||||||||||||||||||||||||
| Data import - default mapping/rules updates - what is impact to quickMARC? What is it about? | Support | Not Applicable | Support | ||||||||||||||||||||||||||||||||||||||||||||
| Addresses 500 errors issue | Yes | Yes | Yes | ||||||||||||||||||||||||||||||||||||||||||||
| Impact for users that load directly to source-record-storage and bypass DI | No | No | No |