Compound file updated to V11 and evaluation plan

[mgsc1020]

please review @PavelBal

[Yuri05]

Please rename Metformin-Model V11.json to Metformin-Model.json

[Yuri05]

Missing observed data mappings in some simulations under metformin model verification po

[Yuri05]

some cross references in report seem to be invalid:

[Yuri05]

Author name seems to be used inconsistently: Morissey vs. Morrisey vs. Morrissey

[mgsc1020]

@Yuri05 thank you for your comments. I addressed the author names and data mappings.
For the comment on the cross-references to report sections #221, #222, and #224 comment, can you give me a hint on how to solve this? I don't think I ran into this error when I ran the report, and I'm unsure how to track it from my side.

[Yuri05]

For the comment on the cross-references to report sections #221, #222, and #224 comment, can you give me a hint on how to solve this? I don't think I ran into this error when I ran the report, and I'm unsure how to track it from my side.

For those chapters no header numbers were created (e.g. compare https://github.com/Yuri05/Metformin-Model/blob/review/Evaluation/report/report.md#in-vitro-and-physicochemical-data).

So you have 3 alternative options for fixing:

1. Adjust the references (e.g. use #in-vitro-and-physicochemical-data instead of #221-in-vitro-and-physicochemical-data)
2. Add subchapter numbers to your static content (would not do this).
3. [Best option] Create your own anchors as described under https://www.open-systems-pharmacology.org/OSPSuite.ReportingEngine/articles/qualification-workflow.html#referencing

• For subchapters which are referenced elsewhere, add <a id="chapter-reference-id"></a> directly above or directly after the chapter header in the markdown file. Use only lower case letters, "-" and digits, e.g.

### In vitro and physicochemical data<a id="in-vitro-data"></a>

• Then you can always reference the chapter by its anchor as [s. tralala](#in-vitro-data)
  This is the safest way as it does not rely on the chapter number, chapter title or the way how the GitHub referencing replaces the special characters in automatically created anchors.