Skip to end of banner
Go to start of banner

Checklist | Move quickMARC edit workflow to DI - Update workflow

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

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 itemBibliographic HoldingsAuthority
Use job profile to edit quickMARC record Support (Morning Glory) Not supportSupport (Morning Glory)

Show Last person to update record and Last updated date/time stamp - no different from today | MODQM-224 - Getting issue details... STATUS

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?NoNoNo
Any impact to handling diacritics? NoNoNo
Any impact for entering subfield delimiter $NoNoNo
Maintain existing quickMARC permissions. Any additional permissions required? 

Backend needs to review. Frontend should have no changes BUT we should test. 


Action item: Pavlo will create user story


Backend needs to review. Frontend should have no changes BUT we should test. 


Action item: Pavlo will create user story

Backend needs to review. Frontend should have no changes BUT we should test.


Action item: Pavlo will create user story



Enforce Optimistic Locking on mod-source-record-storage 

UIQM-243 - Getting issue details... STATUS

UIQM-243 - Getting issue details... STATUS

Will also not send updates to mod-inventory-storage

UIQM-243 - Getting issue details... STATUS

Will also not send updates to mod-inventory-storage

UIQM-243 - Getting issue details... STATUS

Will also not send updates to mod-inventory-storage

Maintain Move holdings from one instance to another behavior - this workflow updates 004N/AWill need check - when change this flow. N/A
Maintain quickMARC ability to override field data protectionShould be implementedShould be implementedShould be implemented
Performance: Make sure quickMARC updates are saved in less than 2 seconds and updates corresponding mod-inventory-storage recordNeed to verify (may need PTF environment)
Need to verify (may need PTF environment)

Performance: Flow control to improve single-record updates

MODSOURMAN-662 - Getting issue details... STATUS

Need to verify

MODQM-241 - Getting issue details... STATUS

Need to verify
MODQM-241 - Getting issue details... STATUS

Need to verify

MODQM-241 - Getting issue details... STATUS

Maintain quickMARC error handling AND allow for future updates that differ from data import

SupportSupportSupport

Maintain quickMARC rules validation AND allow for future updates that differ from data import

SupportSupportSupport
Data import - Logs 


Any impact to mod-inventory-storage?


Data import - default mapping/rules updates - what is impact to quickMARC? 


Addresses 500 errors issue 


Impact for users that load directly to source-record-storage and bypass DI


  • No labels