Note: As of now, these are all created and filled out thanks to this script. It only needs to be rerun if a new table is added to the WLM db.
Look at the unique identifier of each item. Does it correspond to an identifier in an external source?
If yes, find or request an appropriate property.
If no (i.e. the ID is just for internal WLM use), this might mean the dataset is not suitable for import. Without a real-world reference, we can't tell much about the completeness or selection criteria of the data.
Identify heritage status. Do all the items represent the same type of heritage protection (eg. national monument in <country>)?
If not, how can the heritage status of each item be inferred?
Create or edit any necessary items, for example cultural monument of the Czech Republic (Q385405). It should at least have assigned country and subclass of cultural property / national heritage site.
Identify P31
A default P31 for all the items -- something basic like building or ancient monument.
Sometimes there's a separate column for this, like type, that can be used to substitute the default one if possible.
Create necessary lookup tables.
Some fields have a limited range of distinct values, for example se-fornmin_(sv)/types.
In SQL, you can check it using select distinct(columnname) from tablename;
