| 6 | | |
| 7 | | |
| 8 | | = Model Database = |
| 9 | | |
| 10 | | One entry in the model DB contains: |
| 11 | | * unique tag, analog to arXiv: moDel:1003.0123 |
| 12 | | * title |
| 13 | | * author list |
| 14 | | * free text abstract |
| 15 | | * a classification of the model. Should not be hierarchical, since this makes multiple attachments hard. Options are |
| 16 | | * entirely free tagging |
| 17 | | * choice from a pre-set list of tags |
| 18 | | * model description in terms of the (versioned) input file for a specific (versioned) package |
| 19 | | * this combination should also already have a tool chain ID |
| 20 | | * list of validations that have been performed. |
| 21 | | * This format is described below |
| 22 | | * Thumbnails of plots of MC comparisons, including the tool chain ID that was used to make them |
| 23 | | * pointer to the main arXiv paper |
| 24 | | * pointers to downstream papers |
| 25 | | * a "supersedes moDel:0909.3210" entry |
| 26 | | * a sharing licence (maybe pre-defined such that only models adhering to a certain licence can enter) |
| 27 | | |
| 28 | | |
| 29 | | |
| 30 | | features of the interaction: |
| 31 | | * allow for a 24h period for corrections at initial upload |
| 32 | | * authority to modify entries lies with author |
| 33 | | * author can grant modification rights to validators |
| 34 | | * author can relinquish access rights |
| 35 | | * automatic opening after a time limit / max idle time? |
| 36 | | * a system for citation handling? |
| 37 | | |
| 38 | | |
| 39 | | possible uses: |
| 40 | | ||QUESTION||ANSWER|| |
| 41 | | ||specific BSM model||which papers refer to it, which validations have been done|| |
| 42 | | ||specific particle (maybe PDG code)||which models have it|| |
