/Table 1 - Requirements according to MODSOURCE-562 :
| When Incoming $0 | Then the existing linked bib field |
|---|---|
| Is same as existing $0 value |
|
| Is Null |
|
| Field is deleted or removed in imported file |
|
| Is a Different $0 |
|
Testing scenarios:
Table 2 Update using default mapping profile; match by 999 ff $s.
| Test # | Description | Expected result | Actual result | Passed? | Test-case | Issue |
|---|---|---|---|---|---|---|
| 1 | Delete repeatable linked field | Remove field from the bib record; Unlink bib field as it no longer exist | Remove field from the bib record; Unlink bib field as it no longer exis | Yes | https://foliotest.testrail.io/index.php?/cases/view/375108 | MODSOURCE-589 |
| 2 | Delete unique linked field | Remove field from the bib record; Unlink bib field as it no longer exist | Remove field from the bib record; Unlink bib field as it no longer exist | Yes | https://foliotest.testrail.io/index.php?/cases/view/376946 | |
| 3 | Delete subfield "$9" in linked field | Keeps linked to authority record Update uncontrolled subfields | Keeps linked to authority record Update uncontrolled subfields | Yes | https://foliotest.testrail.io/index.php?/cases/view/375104 | |
| 4 | Edit not controlled subfield in linked field | Keeps linked to authority record Update uncontrolled subfields | Keeps linked to authority record Update uncontrolled subfields | Yes | https://foliotest.testrail.io/index.php?/cases/view/375104 | |
| 5 | Delete "$0" value of linked field ($9 is present) | Unlink bib field; Update values as standard data import process Delete $9; Show as not linked on UI | Unlink bib field; Update values as standard data import process Delete $9; Show as not linked on UI | Yes | https://foliotest.testrail.io//index.php?/cases/view/375107 | |
| 6 | Delete "$0" and "$9" value of linked field | Unlink bib field; Update values as standard data import process | Unlink bib field; Update values as standard data import process | Yes | https://foliotest.testrail.io/index.php?/cases/view/376949 | |
| 7 | Edit $0 value of linked field | Unlink bib field; Update values as standard data import process | Unlink bib field; Update values as standard data import process | Yes | https://foliotest.testrail.io//index.php?/cases/view/375101 | |
| 8 | Edit not linked field | Keep the link; Update values as standard data import process | Keep the link; Update values as standard data import process | Yes | https://foliotest.testrail.io//index.php?/cases/view/375098 | |
| 9 | Edit controlled subfield in linked field | Keeps linked to authority record Update uncontrolled subfields | Keeps linked to authority record Update uncontrolled subfields | Yes | https://foliotest.testrail.io//index.php?/cases/view/375098 | |
| 10 | Edit not controlled subfield in linked field | Keeps linked to authority record Update uncontrolled subfields | Keeps linked to authority record Update uncontrolled subfields | Yes | https://foliotest.testrail.io//index.php?/cases/view/375098 | |
| 11 | Add a new subfield with value which is eligible for linking in linked field. | Keeps linked to authority record Update uncontrolled subfields | Keeps linked to authority record Update uncontrolled subfields | Yes | https://foliotest.testrail.io//index.php?/cases/view/375098 | |
| 12 | Add new not controlled digit subfield with value | Keeps linked to authority record Create uncontrolled subfields | Keeps linked to authority record Create uncontrolled subfields | Yes | https://foliotest.testrail.io//index.php?/cases/view/375098 | |
| 13 | Add new not controlled letter subfield with value | Keeps linked to authority record Create uncontrolled subfields | Keeps linked to authority record Create uncontrolled subfields | Yes | https://foliotest.testrail.io//index.php?/cases/view/375098 | |
| 14 | Edit tag value + delete $9 | Unlink bib field; Update values as standard data import process | Unlink bib field; Update values as standard data import process | Yes | https://foliotest.testrail.io//index.php?/cases/view/374189 | |
| 15 | Import new Instance record with $9 in the field that eligible for linking | Successful import; Delete $9; Show as not linked on UI | Successful import; $9 is existing Show as linked on UI | No | https://foliotest.testrail.io/index.php?/cases/view/369080 | |
| 16 | Delete not controlled subfields (letter and digit) | Keeps linked to authority record; Delete uncontrolled subfields | Keeps linked to authority record; Delete uncontrolled subfields | Yes | https://foliotest.testrail.io/index.php?/cases/view/376967 |
Table 3 - Update using mapping profile with enabled "Field mapping · MARC Bibliographic · Updates" setting; match by 999 ff $s.
See screenshot for example of mapping profile setting:
| Test # | Description | Expected result | Actual result | Passed? | Test-case | Issue |
|---|---|---|---|---|---|---|
| 1 | If mapping profile has only $a and record has only $0 changed. | No updates and links persist | No updates and links persist | Yes | https://foliotest.testrail.io/index.php?/cases/view/377000 | |
| 2 | If mapping profile has only $a and record has only $0 removed. | No updates and links persist | No updates and links persist | Yes | https://foliotest.testrail.io/index.php?/cases/view/377001 | |
| 3 | If mapping profile has * for subfields or all of $a, $0, $9 and record has only $0 changed. | $0 update is made and link is removed and therefore $9 should be gone. | If a, 0, 9 specified: Link retained but field is duplicated If * specified: Link removed | NO Yes | ||
| 4 | If mapping profile has * for subfields or all of $a, $0, $9 and record has field removed. | Remove field and link and therefore $9 | If * specified: Link removed (but field is shown and the boxes stay divided) If a, 0, 9 specified: Link removed (but field is shown and the boxes stay divided) | NO | https://foliotest.testrail.io/index.php?/cases/view/377005 | |
| 5 | If mapping profile doesn't have any fields (empty list for fields) and the field is removed from record. | Remove field and link and therefore $9 | Field and link removed | Yes | https://foliotest.testrail.io/index.php?/cases/view/376946 |
Table 4 - Update using mapping profile with selected "Modifications" option; match by 999 ff $s.
| Test # | Description | Expected result | Actual result | Passed? |
|---|---|---|---|---|
| 1 | Action: Add 100 field (same as linked) | 1) No updates to linked field 2) 100 field was added | 1) Controlled subfield was updated | NO |
| 2 | Action: Delete 100 field (same as linked) | 1) Linked field ("100") was deleted? 2) 245 $a was updated. | 1) only controlled subfield $a was deleted from linked field | NO |
| 3 | Action: Edit 100 $a > Insert value | 1) No updates to linked controlled subfield 2) Not-controlled subfield was updated 3) 245 $a was updated. | 1) Linked and controlled subfield was added | NO |
| 4 | Action: Edit 100 $a > Remove value
| 1) ? 2) Not-controlled subfield was updated 3) 245 $a was updated. | 1) Nothing happens
| ?? |
Table 5 - Orchid >> Subfield $9 handling in the fields which NOT linkable / NOT controlled
Match by 999 ff $s used for "MARC bibliographic" records updates.
| Test # | Existing bib record: | Record used for update: | Expected result | Actual result | Passed? | Test-case: | Issue |
|---|---|---|---|---|---|---|---|
| 1 | Doesn't have $9 in the field, which is NOT eligible for linking | 1) add new field with $9 (not UUID): =035 \\$9(AuCNLDY)3360609 2) Update any other field: 245 | Subfields $9 are created Record updated | Subfields $9 are created Record updated | Yes | - | |
| 2 | 1) add one new $9 subfield in field which can't be linked: $9(AuCNLDY)3360611 2) Update any other field: 245 | - | |||||
| 3 | 1) add two $9 subfields in field which can't be linked: "$9(AuCNLDY)3360600$9(AuCNLDY)3360622" 2) Update any other field: 245 | - | |||||
| Update action: | |||||||
| 4 | Has field with only one $9 in the field. 035 \\ $9 (AuCNLDY)3360609 | 1) update value of $9: | Subfield $9 was updated Record updated | Subfield $9 was updated. Record updated | Yes | https://foliotest.testrail.io/index.php?/cases/view/380494
| |
| 5 | Has field with two $9 in the field. =050 \4$9(AuCNLDY)3360600$9(AuCNLDY)3360622 | 1) update one value of $9: =050 \4$9(AuCNLDY)33606UPD$9(AuCNLDY)3360622 2) Update any other field: 245 | Subfield $9 was updated Record updated | ||||
| 6 | Has field with one $9 and others subfields =338 \\$avolume$2rdacarrier$9(AuCNLDY)3360633 | 1) Update other subfield (not $9) from =338 \\$achapter$2rdacarrier$9(AuCNLDY)3360633 2) Update any other field: 245 | Edited subfield was updated Record updated | ||||
| 7 | Has field with two $9 and others subfields =264 \1$aChicago, Illinois :$bHaymarket Books,$c2019. $9testing $9testing again again | 1) update both values $9: =264 \1$aChicago, Illinois :$bHaymarket Books,$c2019. $9testing updated field $9testing again again updated field 2) Update any other field: 245 | Subfields $9 was updated Record updated | ||||
| Delete action: | |||||||
| 8 | Has two fields with only one $9 in the field. =040 \\$9(AuCNLDY)3360444 =035 \\$9(AuCNLDY)3360609 | 1) Delete one field with $9, don't change another one: =035 \\$9(AuCNLDY)3360609 - remains 2) Update any other field: 245 | Field was deleted Record updated | Field was deleted Record updated | Yes | https://foliotest.testrail.io/index.php?/cases/view/380495 | |
| 9 | Has field with two $9 in the field. =050 \4$9(AuCNLDY)3360600$9(AuCNLDY)3360622 | 1) Delete one subfield with $9, don't change another one: =050 \4$9(AuCNLDY)3360600 - remains 2) Update any other field: 245 | One subfield $9 was deleted. Record updated | One subfield $9 was deleted. Record updated | |||
| 10 | Has field with one $9 and others subfields =338 \\$avolume$2rdacarrier$9(AuCNLDY)3360633 | 1) Delete one other subfield, don't change/delete $9: =338 \\$avolume$9(AuCNLDY)3360633 - remains 2) Update any other field: 245 | Only other subfield was deleted (not $9) Record updated. | Only other subfield was deleted (not $9) Record updated. | |||
| 11 | Has field with two $9 and others subfields =264 \1$aChicago, Illinois :$bHaymarket Books,$c2019. $9testing $9testing again again | 1) Delete both subfield with $9, don't change another subfields: =264 \1$aChicago, Illinois :$bHaymarket Books,$c2019. - remains 2) Update any other field: 245 | Both $9 were deleted. Record updated. | Both $9 were deleted. Record updated. | |||
| 12 | Combination of adding new field + update + delete Existing Bib record has $9: 1) Field with $9 only =035 \\$9(AuCNLDY)3360609 2) Field with multiple $9 =050 \4$9(AuCNLDY)3360600$9(AuCNLDY)3360622 3) Field doesn't have $9: 082 \\$a811.6$223 4) Field with multiple $9 and others subfields =264 \1$aChicago, Illinois :$bHaymarket Books,$c2019. $9testing $9testing again again | In file using for update: 1) update value of field with only one $9: | 1) $9 - updated 3) $9 was deleted 4) Both $9 deleted 5) "245" was updated | as expected | Yes | ||
| 13 | Same as previos point + record has linked fields | Same as previos point | $9s created/updated/deleted where it needed. Linked field remains link. | As expected | Yes | ||
| 14 | Existing Bib record doesn't have $9 in fields | 1) Add $9 in UUID format in any field 2) Update "245" | Decline import | Update succesfful Updated field looks like linked ($9 is displayed in View source) | No | ||
Table 6 - Orchid >> Subfield $9 handling in the fields which linkable / controlled
Match by 999 ff $s used for "MARC bibliographic" records updates.
| Test # | Existing bib record: | Record used for update: | Expected result | Actual result | Passed? | Test-case: | Issue |
|---|---|---|---|---|---|---|---|
| Update action: | |||||||
| 1 | Has linked field | 1) Edit $9 of linked not-repeatable field to another value (valid format): 2) Update "245" | Ignore update of $9 "245" updated | $9 wasn't updated "245" updated | Yes | ||
| 2 | Has linked field | 1) Edit $9 of linked field to another value (valid format): 2) Edit $0 of linked field 3) Update "245" | Unlink linked field Delete $9 Update $9 | Unlink linked field Delete $9 Update $9 | Yes | https://foliotest.testrail.io/index.php?/cases/view/375101 | |
| 3 | Has linked field | 1) Edit $9 from repeatable linked field to another value (invalid format): $9(AuCNLDY)3360609 2) Update "245" | Ignore update of $9 "245" updated | Update job completed with error (but srs was updated). $9 was updated to not valid UUID value Link was deleted (Authority icons are displayed) | No | MODDICORE-335 | |
| 4 | Has linked field | 1) add multiple $9 (valid and not valid UUID) in the linked field: 2) Update "245" | Retain link (retain existing linked $9, ignore new $9s) Update "245" | as expected | Yes | ||
| 5 | Has linked field | 1) add multiple $9 (valid and not valid UUID) in the linked field + delete $0 2) Update "245" | Unlink, delete $9 (ignore added $9s). Update "245" | Unlink, delete $9 (ignore added $9s). Update "245" | Yes | ||
| 6 | Has linked field | 1) add multiple $9 (valid and not valid UUID) in the linked field + edit $0 2) Update "245" | Unlink, delete $9s. Update "245" | Comleted with error, but record was updated. Link deleted: 1) quickmarc view - link is broken 2) view source $9s were added. | No | MODDICORE-335 - Poppy | |
| Delete action | |||||||
| 7 | Has linked field | 1. Delete $9 2. Delete $0 | Delete both $0 and $9 Unlink | works as expected | Yes | https://foliotest.testrail.io/index.php?/cases/view/376949 | |
| 8 | Has linked field | 1. Delete $9 2. Update not controlled subfield | 1. Retain link 2. Update subfield | works as expected | Yes | https://foliotest.testrail.io/index.php?/cases/view/375104 | |
| Additional cases: | |||||||
| 9 | Has NO linked field | 1) Add UUID format $9s to field which eligible for linking 2) Update 245 | Don't save $9 Update 245 | $9 created. | No | MODDICORE-330 - Poppy | |
| 10 | Has NO linked field | 1) Add $9 (not UUID) to field which eligible for linking 2) Update 245 | Don't save $9 Update 245 | Import - completed with errors. But record was updated. quickmarc - displayed added $9 View source - "MARC authority" icon is displayed | No | MODDICORE-330 - Poppy | |
