PLATO tools
Your projects in WHG
Your workflow:
What this workflow cannot carry
Save, open or share the project
In the World Historical Gazetteer
How Methodos follows the tools
Methodos keeps your place and sees what the tools do: a step is done when its tool's run on the right file finishes, and a step that stops or fails says why. Only a step that is yours to do (matching columns, reviewing candidates, drawing in Chora) waits for you to say it is done.
Methodos: find your workflow
Say what you have and what you want at the end, and Methodos names the workflow that gets you there, through the tools, step by step.
1 Choose your data
Chora Place on the map
2 Check it, convert it, compare it, publish it, match it, or see it on the map
or
or, with the candidate sets that suggest matches for it (or for one candidate set, with the others),
You will be asked for the candidate sets' files, one file for each set. Each is checked against its profile; a later set must leave out what an earlier one published; and a dataset's answers to candidates (promotedFrom) must find them in the sets. Nothing is fetched.
or, if this is a new version of a dataset you have published,
You will be asked for the earlier version's file. Once a dataset is published, its attestations are only added to: this shows that none was deleted or changed.
or, to make it keep that rule,
You will be asked for the previous release's file (the copy with addresses that its site was made from). Whatever the new version deleted is put back and retracted, whatever it changed is put back and replaced, in your name as reviewer (under Krisis's review), and the revised dataset is checked against the previous release before it is written.
or, to publish it,
See Options for the release's name, the previous release, and where the site will be published.
or, to find the same places in another dataset,
You will be asked for the other dataset's file. Places whose names are alike, and that are near each other, are suggested as matches, for you to accept or reject one by one; your decisions become attestations of identity. To carry on with a review you saved, choose the same dataset, then Resume a review.
or, to see its places on the map and draw on it,
Show on the map (Chora)
Opens Chora here, with this file.
Look up in a gazetteer (online, optional)
What is found is added to the review below, if one is open, for you to decide on as any other match; otherwise a new review begins. Nothing is accepted for you.
Options
The spreadsheet ids (such as
bristol) become web addresses under this one. Leave it empty to use the base_uri in the about sheet, which is where it belongs; given here, it is used instead.
For a frozen release, which gets its own address,
…/release/name.
Its attestations keep their addresses, and nothing it published may be missing.
Only if it is neither the base address nor the repository's GitHub Pages address.
The DOI Zenodo gives to every version of the dataset, once it has given one.
For the website: a text file of the keys of the places to include, one to a line. A place's key is the last part of its address (bristol in …/place/bristol). The addresses of places left out lead to the site's downloads, which hold every place.
Compressed as it is written, with
.gz added to its name; the same data gives the same bytes. Not the spreadsheet tables, which are a zip already.
Adds
rdf:type from the ontology's domains and ranges, xsd:gYear on year bounds, and WKT points.
For figures from a statistical table: each becomes a qb:Observation with its measure as a direct statement, and its place and date as sdmx-dimension:refArea and refPeriod. A date that is not one year or one day is reported, not guessed.
From 0.5 (loosely alike) to 1 (the same, once accents, capitals and punctuation are set aside).
Only where both have coordinates; a place without them is matched by name alone.
Each attestation you make cites the other dataset as its source, by its title. Leave it empty to use the title the other dataset gives; if it gives none, its file's name would be cited, so give one here. At finishing, it is used only for a review that has no title for the other dataset but its file's name.
Recorded with each attestation you make, as the one who made it.
3 Working
4 Result
5 Review the matches
Keys: a same place (or 1–9 for that candidate), n not this one, d different places, s skip, j next, k previous. They act on the highlighted candidate, and do nothing while you are typing.
Wikidata items for the places no gazetteer knows
Saves your decisions so far, to carry on later with Resume a review.
A candidate set publishes what the software suggested, so that each attestation can point at the suggestion it answers. If earlier sets were published, give them first: their candidates are left out.