The format should be added to the config.rkt file.
This will modify the (printprop) function.
Possible fields include:
ID (internal to this tool)
telescope
solicitation
proposal title
PI name
Co-I list
proposal status
proposal type
submitting organization
organization's proposal ID
submission date
result date
The format should be added to the `config.rkt` file.
This will modify the `(printprop)` function.
Possible fields include:
- ID (internal to this tool)
- telescope
- solicitation
- proposal title
- PI name
- Co-I list
- proposal status
- proposal type
- submitting organization
- organization's proposal ID
- submission date
- result date
Variables could be prefixed with % (and the literal "%" would be denoted as %%).
The current output format would then be defined as:
%I: %T(%C; PI: %PI) "%P"
A possible encoding for this is:
|Ref. | Field |
|-----|-------------------|
|I | (internal ID) |
|T | telescope |
|C | call/solicitation |
|P | proposal title |
|PI | PI |
|CoI | Co-I list |
|S | Status |
|PT | Proposal type |
|SO | Submitting org |
|OI | organization ID |
|SD | submission date |
|RD | result date |
Variables could be prefixed with `%` (and the literal "%" would be denoted as `%%`).
The current output format would then be defined as:
`%I: %T(%C; PI: %PI) "%P"`
George C. Privon
The format should be added to the
config.rktfile. This will modify the(printprop)function. Possible fields include:A possible encoding for this is:
Variables could be prefixed with
%(and the literal "%" would be denoted as%%).The current output format would then be defined as:
%I: %T(%C; PI: %PI) "%P"This will also require dynamically updating the SQL queries to ensure the correct information is returned.
Having the codes be single-character would simplify parsing...