Feature summary (what you would like to be able to do and where):
Consider providing an additional endpoint for Web2Cit-Server that provides a more detailed translation output, including:
- The individual outputs for all selection and transformation steps
- The procedure output for each field and whether it is a valid or invalid output
- Possibly, what other templates of the same path pattern group would have returned
Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):
Until the Web2Cit-Editor (=frontend) is implemented, some users may be willing to start testing the system by manually defining template and pattern definitions in our storage in Meta, and asking the Web2Cit-Server to pick them up and translate some URLs. However, in many cases it may be difficult to understand why a translation is not returning the expected results. Is it bug? Or are the definitions wrong?
Benefits (why should this be implemented?):
Having a (maybe temporary) additional endpoint that shows the intermediate outputs would help understand a translation output.