Open zoometh opened 9 months ago
locator
is just for page/figure numbers on a reference, so we can leave this blank if we are referencing the databasespatialCoverageDescription
and label
need rejigging - for example spatialCoverageDescription
will be Levant/Mesopotamia/Arabia while label
and id
within spatialCoverage
will have each individual country in the wikidata_period.tsv list so Lebanon, Syria, Jordan etc etc this means there will be multiple spatialCoverage
records (usually) with therefore multiple label
and id
subrecordsnote
and editorialNote
, both are used for lots of different things in the PeriodO canon dataset, or often, not at allurl
Like so - here column one is the spatialCoverageDescription
while column 3 and 4 will be label
and id
subrecords respectively.
locator
and editorialNote
adding EAMENA's UUID of the period: https://github.com/achp-project/cultural-heritage/blob/main/periodo-projects/exports/eamena_palaeolithic_levant_mesopotamia_arabia.json#L59-L61I think it would be a real shame to lose the spatial information for all those periods - as around half of periods would be composite? Better to find a way of adding multiple entries to the json I reckon?
What if we edited the json template to have the maximum number of nested spatialcoverages etc possible label1
, id1
, label2
, id1
etc etc and then just regexed the final json file to remove the numbers and any blank spatialCoverage
records?
Yes. For example: Mesopotamia here with this spatial extent: https://github.com/achp-project/cultural-heritage/blob/1aeb29659e22ae4ce716fc64fdcde7c1d21522b8/periodo-projects/temp.json#L93-L110
I have noticed, and corrected these errors in the EAMENA period labels. To be compliant with EAMENA overall layout, cultures (eg. Ghaznavid, Timurid, Mamluk, etc.) should not be in parenthesis. Only the geographical region has to be in parenthesis. I've changed the parenthesis to brackets for:
In the same manner, these labels need to be changes in rdm-bu-period.check.xlsx. The results is:
What to do with:
locator
: https://gist.github.com/rybesh/9f64c127ad8eeb69619896f22064bb0e#file-example-dataset-json-L14spatialCoverageDescription
: https://gist.github.com/rybesh/9f64c127ad8eeb69619896f22064bb0e#file-example-dataset-json-L26label
: https://gist.github.com/rybesh/9f64c127ad8eeb69619896f22064bb0e#file-example-dataset-json-L38note
andeditorialNote
: https://gist.github.com/rybesh/9f64c127ad8eeb69619896f22064bb0e#file-example-dataset-json-L47-L48source - locator
: https://gist.github.com/rybesh/9f64c127ad8eeb69619896f22064bb0e#file-example-dataset-json-L61editorialNote
:https://gist.github.com/rybesh/9f64c127ad8eeb69619896f22064bb0e#file-example-dataset-json-L63Is is better to point to a DOI rather than the DB url?:
url
: https://gist.github.com/rybesh/9f64c127ad8eeb69619896f22064bb0e#file-example-dataset-json-L54What is the wikidata id of geographical regions such as:
Levant/Mesopotamia/Arabia
: https://github.com/achp-project/cultural-heritage/blob/05fdec5eca38b12c2a3945cb96ee6b5cbcea9f25/periodo-projects/exports/eamena_palaeolithic_levant_mesopotamia_arabia.json#L28