Orchid > Subfield 9 handling

Orchid > Subfield 9 handling

https://folio-org.atlassian.net/browse/UIQM-414Bib field - subfield 9 is reserved for populating authority UUID when user links MARC bib to authority record. Following outlines current requirements implemented to determine if additional requirements are needed to support 

  • Current cataloging workflows 

  • Authority control implementation for Orchid release and future enhancements 

Page/Action 

Field type

Actual outcome

Expected outcome

Record used

Poppy requirement 

Automated

Page/Action 

Field type

Actual outcome

Expected outcome

Record used

Poppy requirement 

Automated

Edit/Derive MARC bib 

Non-linkable field

Cannot add or edit. Get an error message

https://folio-org.atlassian.net/browse/UIQM-341

Requirements change - allow user to add/edit

https://folio-org.atlassian.net/browse/UIQM-426

https://folio-org.atlassian.net/browse/UIQM-426

 

Edit/Derive MARC bib

Linkable field (linked and unlinked)

Cannot add or edit. Get an error message

https://folio-org.atlassian.net/browse/UIQM-341

Cannot add or edit. Get an error message https://folio-org.atlassian.net/browse/UIQM-341

https://folio-org.atlassian.net/browse/UIQM-426

 

 

https://folio-org.atlassian.net/browse/UIQM-426 (for linked) 

 

 

Data import > Create bib  

Non-linkable field

Successfully creates record with subfield 9

As expected

Same as Orchid

 

Data import > Create bib

Linkable field  

Invalid UUID

Creates a record in SRS but not in mod-inventory

The SRS record does not include the field with $9

 

Valid UUID

https://folio-org.atlassian.net/browse/MODSOURCE-592

As expected = Return an error

Not as expected | Address in Poppy

  • Do not create a record in SRS. 

  • Better error messaging

  • Add an Orchid release note

  • Invalid/Valid UUID 

    • create SRS and mod-inventory record BUT do not import $9

https://folio-org.atlassian.net/browse/MODSOURCE-592

 

Data import > Update bib  (no data field protection)

Non-linkable field

Is not imported.  

https://folio-org.atlassian.net/browse/MODDATAIMP-795

Maintain the $9

https://folio-org.atlassian.net/browse/MODDATAIMP-795

 

Edge case: Data import > Update bib  (no data field protection)

Linkable field

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

 

 https://folio-org.atlassian.net/browse/MODDICORE-330

https://folio-org.atlassian.net/browse/MODDICORE-324

Import record but do not import/save $9 

Field remains unlinked 

 

Data import > Update bib (no data field protection)

Linked field - no change to subfield 9 

Remains linked 

No change to original $9

As expected - No change to original $9 with the same $0

No change from Orchid

 

Data import > Update bib (no data field protection)

Linked field - change to subfield 9 

No change to original $9

As expected - No change to original $9 with the same $0

No change from Orchid

 

Data import > Update bib (no data field protection)

Linked field 

Change to subfield $0 or subfield $0 does not exist  

$9 exist (does not matter if it is the linked UUID) 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Unlink MARC bib field when $0 has changed and remove the subfield 9 

https://folio-org.atlassian.net/browse/MODDICORE-324

https://folio-org.atlassian.net/browse/MODDICORE-331

Update MARC bib field when $0 has changed (automated) 

  • Either link or unlink based on if the authority record is available 

  • Provide configuration in settings

Edge case:  Multiples > Create

Non-linkable field

Successfully creates record with multiple subfield 9s

Create with multiple $9

No change from Orchid expected outcome

 

Edge case:  Multiples > Create

Linkable field 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

  • Invalid/Valid UUID 

    • create SRS and mod-inventory record BUT do not import $9

https://folio-org.atlassian.net/browse/MODSOURCE-592

 

Edge case:  Multiples > Update

Non-linkable field

Is not imported.  

Keep multiple subfields 

https://folio-org.atlassian.net/browse/MODDATAIMP-795

https://folio-org.atlassian.net/browse/MODDATAIMP-795

 

Edge case:  Multiples > Update

Linked field  

 As expected - No change to original $9 with the same $0

 As expected - No change to original $9 with the same $0

No change from Orchid expectation 

 

Edge case:  Multiples > Update

Linked field - change to $0 or it is not included   

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Unlink MARC bib field when $0 has changed and remove the subfield 9 

https://folio-org.atlassian.net/browse/MODDICORE-324

https://folio-org.atlassian.net/browse/MODDICORE-331

 

Edge case:  Multiples > Update

Linkable field  

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

https://folio-org.atlassian.net/browse/MODDICORE-330

https://folio-org.atlassian.net/browse/MODDICORE-324

Import record but do not import/save $9 

Field remains unlinked 

 

More Edge case: Data import > Update bib  (w/ data field protection)

Non-linkable field

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Behave like any other subfield

 

More Edge case:  Data import > Update bib (w/ data field protection)

Linkable field 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

A. Behave like any other subfield

B. Ignore the data field protection setting  

 

More Edge case:  Data import > Update bib (w/ data field protection)

Linked field same $0

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

No change. Everything remains linked 

 

More Edge case:  Data import > Update bib (w/ data field protection)

Linked field no subfield $0 or changed subfield $0 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Unlink bib field AND remove the $9 (IOW ignore data field protection setting) 

 

More Edge case:  Data import > Update bib  (w/ Field mapping profile > MARC bib updates)

Non-linkable field

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Some of these issues will be handled in another release

Behaves like any other subfield

https://folio-org.atlassian.net/browse/UIQM-414

https://folio-org.atlassian.net/browse/MODDICORE-332

MODSOURCE-594: Duplicate field is added when updating "$0" in linked "MARC bib" field upon data import if field mapping profile specifically allows "$0" updateIn Refinement

MODDICORE-319: Link is removed from field when updating/deleting "$0" in linked "MARC bib" field upon data import if field mapping profile does not allow "$0" updateClosedMODDICORE-311: Unlinked field looks like linked on UI when update/import "MARC Bib" record when $9 is included in the imported fileClosed

 

 

More Edge case:  Data import > Update bib (w/ Field mapping profile > MARC bib updates)

Linkable field 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Some of these issues will be handled in another release

https://folio-org.atlassian.net/browse/UIQM-414

https://folio-org.atlassian.net/browse/MODDICORE-332

MODSOURCE-594: Duplicate field is added when updating "$0" in linked "MARC bib" field upon data import if field mapping profile specifically allows "$0" updateIn Refinement

MODDICORE-319: Link is removed from field when updating/deleting "$0" in linked "MARC bib" field upon data import if field mapping profile does not allow "$0" updateClosedMODDICORE-311: Unlinked field looks like linked on UI when update/import "MARC Bib" record when $9 is included in the imported fileClosed

 

More Edge case:  Data import > Update bib (w/ Field mapping profile > MARC bib updates)

Linked field same $0 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Some of these issues will be handled in another release

https://folio-org.atlassian.net/browse/UIQM-414

https://folio-org.atlassian.net/browse/MODDICORE-332

MODSOURCE-594: Duplicate field is added when updating "$0" in linked "MARC bib" field upon data import if field mapping profile specifically allows "$0" updateIn Refinement

MODDICORE-319: Link is removed from field when updating/deleting "$0" in linked "MARC bib" field upon data import if field mapping profile does not allow "$0" updateClosedMODDICORE-311: Unlinked field looks like linked on UI when update/import "MARC Bib" record when $9 is included in the imported fileClosed

 

More Edge case:  Data import > Update bib (w/ Field mapping profile > MARC bib updates)

Linked field no subfield $0 or changed subfield $0 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Some of these issues will be handled in another release

https://folio-org.atlassian.net/browse/UIQM-414

https://folio-org.atlassian.net/browse/MODDICORE-332

MODSOURCE-594: Duplicate field is added when updating "$0" in linked "MARC bib" field upon data import if field mapping profile specifically allows "$0" updateIn Refinement

MODDICORE-319: Link is removed from field when updating/deleting "$0" in linked "MARC bib" field upon data import if field mapping profile does not allow "$0" updateClosedMODDICORE-311: Unlinked field looks like linked on UI when update/import "MARC Bib" record when $9 is included in the imported fileClosed

 

More Edge case:  Data import > Update bib  (w/ Field mapping profile > MARC bib | Override data field protection)

Non-linkable field

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Behaves like any other subfield but if not will handle in a future release

 

More Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib | Override data field protection)

Linkable field 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Handle in future release

 

More Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib | Override data field protection)

Linked field same $0

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Handle in future release

 

More Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib | Override data field protection)

Linked field no subfield $0 or changed subfield $0 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Handle in future release

 

 

Most Edge case:  Data import > Update bib  (w/ Field mapping profile > MARC bib modifications | Add)

Non-linkable field

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Handle in future release

 

Most Edge case: Data import > Update bib  (w/ Field mapping profile > MARC bib modifications | Add)

Linkable field 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Address in a future release

 

Most Edge case: Data import > Update bib  (w/ Field mapping profile > MARC bib modifications | Add)

Linked field same $0

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Address in a future release

 

Most Edge case: Data import > Update bib  (w/ Field mapping profile > MARC bib modifications | Add)

Linked field no subfield $0 or changed subfield $0 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Handle in future release

 

Most Edge case:  Data import > Update bib  (w/ Field mapping profile > MARC bib modifications | Delete)

Non-linkable field

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Handle in future release

 

Most Edge case:  Data import > Update bib  (w/ Field mapping profile > MARC bib modifications | Delete)

Linkable field 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Handle in future release

 

Most Edge case: Data import > Update bib  (w/ Field mapping profile > MARC bib modifications | Delete)

Linked field same $0

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Handle in future release

 

Most Edge case: Data import > Update bib  (w/ Field mapping profile > MARC bib modifications | Delete)

Linked field no subfield $0 or changed subfield $0 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Handle in future release

 

Most Edge case: Data import > Update bib  (w/ Field mapping profile > MARC bib modifications | Edit)

Non-linkable field

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Handle in future release

 

Most Edge case:  Data import > Update bib  (w/ Field mapping profile > MARC bib modifications | Edit)

Linkable field 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Handle in future release

 

Most Edge case:  Data import > Update bib  (w/ Field mapping profile > MARC bib modifications | Edit)

Linked field same $0

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Handle in future release

 

Most Edge case:  Data import > Update bib  (w/ Field mapping profile > MARC bib modifications | Edit)

Linked field no subfield $0 or changed subfield $0 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Handle in future release

 

Most Edge case:  Data import > Update bib  (w/ Field mapping profile > MARC bib modifications | Move)

Non-linkable field

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Handle in future release

 

Most Edge case:  Data import > Update bib  (w/ Field mapping profile > MARC bib modifications | Move)

Linkable field 

 

Testing scenarios of "Handle bib-authority link when user updates a bib record via data import":

 

Handle in future release

Comments