Recordings are posted Here (2022+) and Here (pre-2022) Slack channel for Q&A, discussion between meetings
Requirements details Here Additional discussion topics in Subgroup parking lot
Attendees: Ann-Marie Breaux (Deactivated)
Morning Glory
- Morning Glory Folijet and Spitfire planning: dashboard where you can see the current scope and status of Data Import work for Morning Glory
Agenda topics:
- MARC field protections - Initial User Acceptance testing for Morning Glory
| Field protection setting | Library/User | Works as expected? | Notes | Add a TestRail? |
|---|---|---|---|---|
| 035 9\ | Not the way I expected. I created inventory for 15 eResources with a temporary code in the 035 9\ $a(5LHFCJSP1). Then I exported those so I could match on the instance HRID to create an additional holding and item. Then I included a marc modify action linked to a marc modifications mapping that removed the 1 to have 035 9\$a(5LHFCJSP). This didn't work. I didn't see anywhere where I could override the field protections in the marc modify action or mapping profile. Here I was taking action on the incoming record. | |||
| 035 9\ | Since the marc modification didn't work on the incoming record in my other test, I tried to use an update marc action linked to a mapping. This is an update where I match on the instance HRID to create an additional holding and item and then update the marc. Right now this job is stuck with in progress. And an hour later it's still stuck. | |||
| 856 | Didn't work. I wanted to create inventory for eResources so I need the 856 to populate the Electronic access in the holdings record. The last action in the job is to modify the marc to remove the 856. This didn't happen. the log has "multiple" for instance and "updated" for srs marc. | |||
| 856 | Jenn Colt | I need to protect the 856 so that overlays with single record import don't delete our local 856s. But I need to update 856s when I import updated vendor records. Because the field protections were extended to instances without correcting the bug of protecting incoming records, the 856 was not updated as indeed and instead the original 856 was duplicated (which seems like an additional bug). If this is implemented as is it will break ALL OUR WORKFLOWS. Extending the field protections to instances without fixing the bugs is disastrous. Extending field protections to instances without being able to override them at the job level is terrible. We (and many others) use instance overlay to correct a large number of data import problems. We need to have an instance overlay profile that ignores field protections without having to manually turn them all off. | ||