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