Help:Maintenance procedures

Introduction

To keep the information coherent with other databases, to ensure we have no anomalies (links to items not part of the expected values) in the database, and orphan entries, not linked to any other item or missing information to visualise and list properly, some maintenance needs to be done on a regular base.

Different maintenance procedures

Transferring text based items to items

For some properties we created a text based version to speed up the entering process, avoiding new items have to be made when referring to a specific type of information. This is the case for example for [architect (txt)] which has an item equivalent [architect]. In a maintenance procedure, these entries should be transferred to items.

Check essential information for visualisation missing

• check countries missing in Businesses https://tinyurl.com/2xndr2ub

Checking for available item to be used

- Could we add a link “recycle item“ to a list under “new item” in the menu? - Could we empty them to avoid wrong answers?

List to choose from https://tinyurl.com/29nb2lny

Checking for consequence in naming

Check syntax of theatres and alias

Updating property lists and manual

• Even if we expect properties to be documented properly in the website, the list needs to be verified on a regular base and the manual needs to be updated.

• • • Updating lay-out and numbering ***
• The organisation of the different properties is based on the [property order] but does not occur automatically in the website. On a regular base, or after significant changes the lay-out needs to be updated.

Not translatable items

Some labels are not translated, except in special cases. But it is good to have them in all languages. On a regular base we need to check if all languages are added.

• Names of theatres
• Names of persons
• The descriptions for theatres can be translated in different languages automatically. This is based on the sentence “theatre in” + city + country.

Automatically translated items

• For continents, countries, regions, provinces, cities and city sections we rely on Wikidata for translation, but a check is needed if there is a wikidata reference.

Terms that need translation

• Including equipment

Check translations of lists

To ensure the accurate multilingual functionality, at least the properties, the standardised language lists, the values from the standardised language lists, and “coded terminology” must be translated (and checked on a regular base). To facilitate this process, we developed some SPAQL queries that can be run to check. These are based on the browser language of the user and English. Of course they also can be used to add a new language.

Translation value list titles

https://tinyurl.com/2hofqg5f

• Run query (blue arrow)
• Check where there is a Q number in column ItemLabel
• Open and add missing value in your language
• Run query again to check if you want.

Translation values of value lists

https://tinyurl.com/2mpns9ay 

• Run query (blue arrow)
• Check where there is a Q number in column ItemLabel
• Open and add missing value in your language
• Run query again to check if you want.

Translation of properties

https://tinyurl.com/2lqwpre5 

• Run query (blue arrow)
• Check where there is a Q number in column Propertyabel
• Check if text is missing in inversenlLabel (and there is in InverseLabel
• (exept when ID or maintenance label, these need no translation)
• Open and add missing value in your language
• Run query again to check if you want.

(this one needs a property to avoid properties that don’t need to be translated)

• For the properties,
  • it is complicated, because some
    • Needs no translation because they are service properties
    • Needs a copy in each language because they are identifiers
    • Needs only translation of the label
    • Needs translation of label and description
    • Needs verifying translation because something has changed.
  • Would it make sense to add to each property a status with these remarks, so we can send them to the different people?

Hard coded titles =

Part of the interface (titles etc.) are hard-coded. The “hard coded” text is kept in a separate Excel file and needs to be added by the provider.

System updates

Some aspect in the system has to be updated from time to time.

• Property order
• System translations
• inverse properties labels
• Hiding of non public statements

Therefore for instance new inverse property label won't display immediately, but with the next update.

System checks

Database data structure is observed through auxiliary system values (Q511)

missing values check

The following queries should return empty:

• List of properties that should have a value list, but in fact does not have at the moment.

http://tinyurl.com/2xjow8zl

• List of value list that should have related property, but in fact does not have at the moment.

http://tinyurl.com/2xuxlskn

Overview lists:

• List of P1 applied values:

https://tinyurl.com/23krlkgf

• List where P1 might be wrong

https://tinyurl.com/2avxsaqh

Properties coherency

• Value lists

List of Properties that should have a value list https://tinyurl.com/24tqvj58

List of Properties that should have a value list, but actually don't have (should be empty)

http://tinyurl.com/23wljkqy

List of properties without value list: it is correct? Does some of the properties would need a value list? https://canonbase.eu/wiki/Property:P119

Property translation labels

Here are lists of properties that do not have translation of their labels in the respective languages

 * Cz http://tinyurl.com/2ch59zzb
 * Nl http://tinyurl.com/22yj8pr8
 * Fr http://tinyurl.com/24w9vmrt
 * Es http://tinyurl.com/24z3b8jr
 * It http://tinyurl.com/28f84ypt
 * De http://tinyurl.com/2ypp4smh
 * Sv http://tinyurl.com/26vuby83

Inverse labels

Inverse label management property (Q5865)

according to the nature of the data that Property collects, there are several types of properties, where it is judged, whether to use the inverse properties or not.

• Should have inverse labels (Q6231)

Inverse labels will be used.

• Should have generic inverse label for type (Q5805)

Inverse labels will not be used as these properties would compile a list of item with this feature, however, still a generic, appropriate description would be needed to be passed as "has instances", " this feature appears where" or in such similar sense.

• without inverse label (Q5749)

No inverse labels are needed.

• So far undecided cases (Q6457)

those where it has to be checked if needs inverse property label

So, if property should have inverse labels, then these list of each language list, where the translation is missing.

Check if a label is not missing under Inverse Label column in the given language. To change it, one needs to adapt the appropriate item with Inverse property label P232 in the property.

 * En https://tinyurl.com/27swrnjz
 * Cz https://tinyurl.com/27mqpxuc
 * Nl https://tinyurl.com/28d9a3hu
 * Fr https://tinyurl.com/26eby74f
 * Es https://tinyurl.com/268ue7eb
 * It https://tinyurl.com/223vfdce
 * De https://tinyurl.com/2843u5mz
 * Sv https://tinyurl.com/275sgrgn

Data enhancement

Missing compulsory values

These list display items where some value is missing, altought it should be there. Thses lists then should be empty:

Organizations without respective country http://tinyurl.com/258yza79

Theatres without cities https://tinyurl.com/23sdslr2

Theatres without countries https://tinyurl.com/2b3db7ol

Properties that should have a values list but do not have https://tinyurl.com/28vy5m8f

various checks

List of properties that don't have values list. Does any of the properties need P119 value list ? https://tinyurl.com/28uq2gtb