Authority control | Validation flow

Edit Authority record via UI

Scenario #Authority record linked to a bib recordDelete a field (1)Delete a field (2)Edit a field (1)Edit a field (2)Expected outcome 
1Y

1XX or 010 (regardless if user edits record before deleting field)

N/A

Option 1 (Show message on hitting Save):

  • For the 1XX:
    • Show the ...Cannot delete a 1XX because it is required error message. 
    • Do not show the delete field(s) confirmation modal
    • User must correct error to Save record

For the 010

  • Show the... Cannot delete 010 $a because it is linked to a MARC bib record error message
  • Do not show the delete field(s) confirmation modal
  • User must correct error to Save record

Option 2 (error validation on deleted field):

  • For the 1XX: When the clicks the trash can button on the 1XX  THEN show the ...Cannot delete a 1XX because it is required error message AND do not proceed with replacing 1XX with the deleted row placeholder. 
  • For the 010: When the clicks the trash can button on the 010$a THEN show the Cannot delete 010 $a because it is linked to a MARC bib record error message AND do not proceed with replacing 1XX with the deleted row placeholder. 


2Y

1XX or 010 (regardless if user edits record before deleting field)



Leader bad value for a position (unsuccessful save)

Option 1 (Show message on hitting Save):

  • For the 1XX:
    • Show the ...Cannot delete a 1XX because it is required error message. 
    • Do not show the delete field(s) confirmation modal
    • User must correct error to Save record

For the 010

  • User hits Save AND if the 010 still persist THEN
  • Show the... Cannot delete 010 $a because it is linked to a MARC bib record error message
  • Do not show the delete field(s) confirmation modal
  • User must correct error to Save record

For Leader or any other error:

    • If user hits Save again When the error still persist Then show the Leader bad value message
    • User must correct error to Save record

Option 2 (error validation on deleted field): When the clicks the trash can button on the 1XX  THEN show the ...Cannot delete a 1XX because it is required error message. AND do not proceed with replacing 1XX with the deleted row placeholder. . 

When the clicks the trash can button on the 010$a THEN show the Cannot delete 010 $a because it is linked to a MARC bib record error message AND do not proceed with replacing 1XX with the deleted row placeholder. 

When user clicks Save THEN show the Leader bad value message. 


Option 3 (on Save): Show all validation errors on the same message.

User cannot save until all errors are resolved

Option 4 (on Save) - Support inline error messaging



Y

1XX or 010 (regardless if user edits record before deleting field)

680 

Option 1 (Show message on hitting Save):

  • For the 1XX:
    • Show the ...Cannot delete a 1XX because it is required error message. 
    • Do not show the delete field(s) confirmation modal
    • User must correct error to Save record

For the 010

  • User hits Save AND if the 010 still persist THEN
  • Show the... Cannot delete 010 $a because it is linked to a MARC bib record error message
  • Do not show the delete field(s) confirmation modal
  • User must correct error to Save record

For Leader or any other error:

    • If user hits Save again When the error still persist Then show the Leader bad value message
    • User must correct error to Save record


Then show the delete field(s) confirmation modal once all errors have been resolved


Option 2 (error validation on deleted field): When the clicks the trash can button on the 1XX  THEN show the ...Cannot delete a 1XX because it is required error message. AND do not proceed with replacing 1XX with the deleted row placeholder. 

When the clicks the trash can button on the 010$a THEN show the Cannot delete 010 $a because it is linked to a MARC bib record error message AND do not proceed with replacing 010 with the deleted row placeholder.  

Then show the delete field(s) confirmation modal once all errors have been resolved

Option 3 (on Save): Show all validation errors on the same message.

User cannot save until all errors are resolved

Then show the delete field(s) confirmation modal once all errors have been resolved

Option 4 (on Save) - Support inline error messaging

Then show the delete field(s) confirmation modal once all errors have been resolved


N

1XX or 010 (regardless if user edits record before deleting field)




Option 1 (Show message on hitting Save): Show are you sure want to delete field(s) confirmation modal when user clicks Save on the delete field(s) confirmation modal THEN show the ...Cannot delete a 1XX because it is required.  error message


Option 2 (error validation on deleted field): When the clicks the trash can button on the 1XX  THEN show the ...Cannot delete a 1XX because it is required error message. AND do not proceed with showing the deleted row placeholder. 


Regardless of option: 010 -  allow the user to successfully delete field  and follow the flow we support for deleted fields currently


N

1XX or 010 (regardless if user edits record before deleting field)


Invalid values entered in 008 (unsuccessful save)

Option 1 (Show message on hitting Save): Cannot delete a 1XX because it is required error message

When user clicks Save THEN show the Leader bad value message. 


Option 2 (error validation on deleted field): When the user clicks the trash can button on the 1XX THEN show the ...Cannot delete a 1XX because it is required error message AND do not proceed with showing the deleted row placeholder.

When user clicks Save THEN show the Leader bad value message.  

Option 3 (on Save): Show all validation errors on the same message.

Regardless of option: 010 -  allow the user to successfully delete field and follow the flow we support for deleted fields currently


Y680 

Edit 1XX or 010$a (successful)



Option 1 (Show message on hitting Save): First - Show the Delete field(s) confirmation modal AND when user hits Save on the modal THEN save the changes (IOW acts like Save & keep editing behavior) AND Second - then immediately show the 'Are you sure you want to update MARC authority 1XX or 010 because it will make changes to linked bib field modal' When user hits Save then it should either Save and keep editing OR Save return user to View Source. 


Option 2 (show message based on change to 1XX or 010 field) - When user makes the Edit 1XX or 010$ Then show the 'Are you sure you want to update MARC authority 1XX or 010 because it will make changes to linked bib field modal' WHEN user hits Save then  THEN save the changes (IOW acts like Save & keep editing behavior)

THEN 680 -  allow the user to successfully delete field and follow the flow we support for deleted fields currently


N680

Edit 1XX or 010$a (successful) 


680 -  allow the user to successfully delete field and follow the flow we support for deleted fields currently

Y680  5XX 

Edit 1XX  (unsuccessful because user removed/added a subfield $t or changed 1XX field number)  


Option 1: Show the Cannot add a $t because this authority heading is already linked to a bib field that is a 100/110/111 message 

IF user resolves the error THEN allow the user to Save AND when the user clicks Save THEN allow the user to successfully delete field and follow the flow we support for deleted fields currently.


Option 2 : Show all validation errors on the same message. When user corrects all errors then allow them to complete deleting fields AND then keep user on edit form to immediately ask user to confirm authority link update (if applicable)


Y

010 $a or 1XX


  • 010 $a or 1XX (successful)
  • Whatever is  NOT deleted is edited

Option 1 (Show message on hitting Save): Show are you sure want to delete field(s) confirmation modal when user clicks Save on the delete field(s) confirmation modal THEN show the ...Cannot delete a 1XX because it is required.  error message

If it is 010 $a WHEN user hits Save on the delete field(s) confirmation modal show the toast notification message - Cannot delete 010 $a because it is linked to a MARC bib record error message

IF user resolves the error THEN allow the user to Save AND when the user clicks Save THEN show the 'Are you sure you want to update MARC authority 1XX or 010 because it will make changes to linked bib field modal'

Option 2 (error validation on deleted field): When the clicks the trash can button on the 1XX  THEN show the ...Cannot delete a 1XX because it is required error message. AND do not proceed with showing the deleted row placeholder. 

When the clicks the trash can button on the 010$a THEN show the Cannot delete 010 $a because it is linked to a MARC bib record error message AND do not proceed with showing the deleted row placeholder. 

IF user resolves the error THEN allow the user to Save AND when the user clicks Save THEN show the 'Are you sure you want to update MARC authority 1XX or 010 because it will make changes to linked bib field modal'



Y680 5XX 

Edit 1XX  (unsuccessful because user removed/added a subfield $t or changed 1XX field number  

Invalid values entered in 008 (unsuccessful save)

Option 1 (Show message on hitting Save)

First Show the Cannot add a $t because this authority heading is already linked to a bib field that is a 100/110/111 message 

Second - Disable Save button until error is fixed - once the issue has been fixed then show the invalid values message 

Once that error is fixed then enable Save AND Show the Delete field(s) confirmation modal AND when user hits Save on the modal THEN save the changes (IOW acts like Save & keep editing behavior) AND THEN immediately show the 'Are you sure you want to update MARC authority 1XX or 010 because it will make changes to linked bib field modal'  (if applicable) When user hits Save then it should either Save and keep editing OR Save return user to View Source. 

Option 2 (error validation on 1XX or 010$a)

Show the Cannot add a $t because this authority heading is already linked to a bib field that is a 100/110/111 message 

IF user resolves the error THEN allow the user to Save AND when the user clicks Save THEN

Show the leader validation error AND IF user resolves the error THEN allow the user to Save AND when the user clicks Save THEN

allow the user to successfully delete field and follow the flow we support for deleted fields currently.


Option 3 (on Save): Show all validation errors on the same message. When user corrects all errors then allow them to complete deleting fields AND then keep user on edit form to immediately ask user to confirm authority link update (if applicable)


N/A680 (regardless of authority record linked to a bib record) 


680 -  allow the user to successfully delete field and follow the flow we support for deleted fields currently