Instance: Add related instances data element

Thanks, good to know. I saw "In progress" so I thought dev work had started!

Hi - this work is scheduled for Poppy - so I'm not working on this right now.
CC:

Hi For now, I'm going to assume that this additional data element (related instances) in the Instance is not controlled by any underlying MARC record and does not need to be created or edited via Data Import. If that is accurate, then we'll plan to ignore all of this for Data Import. If that is not accurate, then please let me know ASAP, so that we can consider how this might affect Data Import for Poppy.

cc:

Hi and If we sequence it the way we did for Admin notes, then if Prokopovych does the work in Nolana, Data Import would do corresponding work in Orchid. If the DI work needs to be done in Nolana, we definitely need to understand that. And this all presumes that the data elements and data schema for Preceding/Succeeding, Other related titles, and Parent/Child are not consolidated (a conversation in another Jira someplace). If they are, that will will require more analysis and testing, plus figuring out how to deal with existing data already in the current configuration. We've also had issues with preceding/succeeding data where the fields behave differently if the instance source = MARC (controlled by the SRS MARC 780/785 fields) versus if the instance source = FOLIO (allows lookup and linking to another instance)

Hey - I am going to ask the same questions as . Based on the below screenshot, it appears that we need to update MARC bib default mapping to support this requirement as it can control this information? If this is the correct, is the plan to have all MARC fields not crossed out included in default mapping? And thus data import work is required?