knowing which region(s) is associated with each record, is critical for any search/querying of the ODIS graph, as well as producing any summary for each region
a top-level field in the JSON-LD for region is therefore required
notes / challenges / thoughts:
multiple regions can be associated with each entry
global repositories may have local regional data, yet lack any 'region' definition
this requirement should also be added into the documentation/book, so all partners tackle this themselves early on
especially as adding a region value through the ODIS-Arch graph ourselves (for existing entries) could be problematic
the Dashboard could give a status on whether a node is defining a "region" or not