Description
I propose we do this in three steps.
In the first, the tool will run on the command line, and when given one MMSID, will query the OAI-PMH feed for the record's MARC xml, then run the same rules we have for indexing, and report at the end whether the MMSID should be in the index or not. While this output is not very helpful, it serves as a stepping stone to the later versions. Minimally, it will catch when an MMSID has been added by catalogers, but has not had time to enter the index via the incremental indexing jobs.
The second version will take the rules we currently have, and reorganize them so the tool can report which rule prevented the record from entering the index. I suspect this work will not be insignificant, as is worthy of being broken out into its own ticket.
The third step is vague- development at this point could go in a couple of directions. One option would be to allow the tool to work on more than one MMSID at once. Another option (that would need much more design) would be to create a UI in the application for certain users to access the tool, allowing non-developers to run it.