Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TopicWhoMeeting NotesRelated JiraDecisions and Actions

Announcements:





Review results of feature prioritization exerciseRyan


MARC Modification TestingJenniferLink to spreadsheet

Quesnelia Spreadsheet:

Lref gdrive file
urlhttps://docs.google.com/spreadsheets/d/1Rvd4uCBdhyJnzA-7WBXY4zFUMceMkvetER-FwyF6raE/edit#gid=361751186

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.

Spreadsheet for Poppy

Lref gdrive file
urlhttps://docs.google.com/spreadsheets/d/1OxiqsLjO7a19K1TQDCZXmbmWM-lWXgGkoz_3jL_C80g/edit#gid=361751186

  • Making DI UI consistent with quickMarc and Bulk Edit. For example, blanks are denoted by the \ rather than a space.
  • Significant challenges with using MARC modifications with updates. One idea shared in lab was to see if we want to start with a baseline approach of how and where we need to have MARC modifications, develop that, and then build on that foundation.


MODDATAIMP-897: Adding MARC modifications to single record overlay doesn't respect field protections

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODDATAIMP-897












Notes from previous meetings...





...