The `author/author_handle.json` file content was generated by the commands: ```sh cd tmp rm -rf ../author ./gen_author_json.sh author_handle.txt author.csv author-wins.csv ../author ``` Also installed is `author/README.md` that describes the `author/` directory tree and author_handle.json format. Some tmp files were slightly modified before to help the `gen_author_json.sh` tool. NOTE: The `gen_author_json.sh` tool is under the `tmp/` directory and **NOT** the `bin/` directory. Like the files under tmp/` directory, the `gen_author_json.sh` tool will go away as the files and tool are not needed. The `author/author_handle.json` files will become authoritative, replacing the `gen_author_json.sh` tool and files under tmp/` directory. However we will keep them around for a while, at least a git of time after issue #4 is resolved.
21 lines
574 B
JSON
21 lines
574 B
JSON
{
|
|
"no_comment" : "mandatory comment: because comments were removed from the original JSON spec",
|
|
"author_JSON_format_version" : "1.0 2023-06-10",
|
|
"author_handle" : "V_Chia",
|
|
"full_name" : "V. Chia",
|
|
"sort_word" : "chia",
|
|
"location_code" : "SG",
|
|
"location_name" : "Singapore",
|
|
"email" : "bi@mncw.tk",
|
|
"url" : null,
|
|
"alt_url" : null,
|
|
"deprecated_twitter_handle" : "",
|
|
"mastodon" : null,
|
|
"mastodon_url" : null,
|
|
"github" : null,
|
|
"affiliation" : null,
|
|
"winning_entry_set" : [
|
|
{ "winner_id" : "2005_chia" }
|
|
]
|
|
}
|