Take a look at https://github.com/matthewdeanmartin/rmarc/blob/main/bench/bench_deathmatch.py. It has several spots where slightly different python api code is used for mrrc processing and that suggests api differences from the pymarc we are aiming for compatibility with.
Please check each api call. Are these true gaps in our pymarc compatibility? Because we aim for as close to 100% compatibility as reasonable possible, review each carefully to confirm whether or not they represent a gap we could close for better pymarc compatibility in our python wrapper.
Identify each gap and come up with a plan to close the gap for improved compatibility.
Update mrrc's python api, tests, example code, introductory and reference documentation, and any other public facing docs as appropriate to close these gaps.
Take a look at https://github.com/matthewdeanmartin/rmarc/blob/main/bench/bench_deathmatch.py. It has several spots where slightly different python api code is used for mrrc processing and that suggests api differences from the pymarc we are aiming for compatibility with.
Please check each api call. Are these true gaps in our pymarc compatibility? Because we aim for as close to 100% compatibility as reasonable possible, review each carefully to confirm whether or not they represent a gap we could close for better pymarc compatibility in our python wrapper.
Identify each gap and come up with a plan to close the gap for improved compatibility.
Update mrrc's python api, tests, example code, introductory and reference documentation, and any other public facing docs as appropriate to close these gaps.