...
| Topic | Who | Meeting Notes | Related Jira | Decisions and Actions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Announcements: | ||||||||||||
| Review results of feature prioritization exercise | Ryan | |||||||||||
| MARC Modification Testing | Jennifer | Quesnelia Spreadsheet:
With the testing in Poppy, Jennifer found that several features didn't work consistently or as expected. It was thought to suggest a flow that the community could agree on and start from there. This happened in Quesnelia. The link to the spreadsheet above has the flow outlined for Quesnelia on where MARC modification actions can be placed in relation to other actions in a job profile. Testing proved successful except when the marc modify action came after the action profile or at the very end of the job profile as the last action at the same level as the match profile. Added documentation to: Data Import Marc Modifications for MARC Bibliographic Records. Spreadsheet for Poppy:
| ||||||||||
| MODDATAIMP-897: Adding MARC modifications to single record overlay doesn't respect field protections | Testing in Quesnelia: Jennifer test this and it is working in some cases but not all. In the SRI job profile to overlay an instance, field protections were protected. However, as part of a solo job profile where the marc modify action was after the action to update or the last action in the job, field protections weren't respected. As part of a solo job where the marc modify came first before the match on the instance, the field protections where respected. |
| ||||||||||
| Notes from previous meetings... |
...