Difference between revisions of "Help:Interoperability"
From CanonBase
(Created page with "==Introduction== ==== Sources ==== === Property level === The properties we use ensure that we capture the correct information in a way that we can analyse it. Secundary the...") |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Introduction== | ==Introduction== | ||
| − | + | Interoperability means the possibility to exchange and retrieve information between different datasets en systems without loss of information. We want Canonbase to be interoperble with as much systems as possible. Our core goal is to be interoperable with Wikidata, because this guarantees safeguarding of the information of our users. | |
| − | + | == Property level == | |
| − | |||
| − | |||
The properties we use ensure that we capture the correct information in a way that we can analyse it. Secundary the choice of properties supports transferability with other sdata ystems, to retrieve and to export information. | The properties we use ensure that we capture the correct information in a way that we can analyse it. Secundary the choice of properties supports transferability with other sdata ystems, to retrieve and to export information. | ||
| Line 13: | Line 11: | ||
example: we use [significant date] with a qualifier [context] and [timeline label], Wikidata uses [significant event] with a [point in time] qualifier. | example: we use [significant date] with a qualifier [context] and [timeline label], Wikidata uses [significant event] with a [point in time] qualifier. | ||
* a property does not exist in other property systems. (Here interoperability is only possible if we (are allowed to) create new properties in the existing systems.) | * a property does not exist in other property systems. (Here interoperability is only possible if we (are allowed to) create new properties in the existing systems.) | ||
| + | Example: properties for specific measurements of technical equipment. | ||
* a property is less detailed than the existing ones in other systems. (This a situation we need to avoid.) | * a property is less detailed than the existing ones in other systems. (This a situation we need to avoid.) | ||
| Line 18: | Line 17: | ||
==== Sources ==== | ==== Sources ==== | ||
| + | '''on buildings''' | ||
* https://www.wikidata.org/wiki/Wikidata:WikiProject_Cultural_venues/Data_structure#Data_structure_for_venues | * https://www.wikidata.org/wiki/Wikidata:WikiProject_Cultural_venues/Data_structure#Data_structure_for_venues | ||
| + | * https://www.wikidata.org/wiki/Wikidata:WikiProject_Cultural_venues/Data_structure#Notes_on_properties_for_cultural_venues | ||
| + | * https://www.wikidata.org/wiki/Wikidata:WikiProject_Performing_arts/Data_structure/Data_modelling_issues#List_of_properties_used_on_theatre_(venue)_items | ||
| + | *https://www.wikidata.org/wiki/Wikidata:WikiProject_Cultural_venues/Data_structure#Notes_on_properties_for_cultural_venues | ||
| + | * https://www.wikidata.org/wiki/Wikidata:WikiProject_Cultural_venues | ||
| + | * https://www.wikidata.org/wiki/Category:WikiProject_Cultural_venues | ||
| + | '''on arts organisations''' | ||
| + | * https://www.wikidata.org/wiki/Wikidata:WikiProject_Performing_arts | ||
| + | |||
| + | '''On Archives''' | ||
| + | *https://www.wikidata.org/wiki/Wikidata:WikiProject_Archival_Description | ||
| − | + | '''On Occupations''' | |
| + | https://www.wikidata.org/wiki/Wikidata:WikiProject_Performing_arts/Typologies#Artefacts_Documenting_Activities_Related_to_the_Performing_Arts | ||
| + | |||
| + | == Taxonomy level == | ||
A taxonomy or controlled language is the way we define and structure things. | A taxonomy or controlled language is the way we define and structure things. | ||
In concreto, the taxonomies are often related to the expected values of one or more properties. | In concreto, the taxonomies are often related to the expected values of one or more properties. | ||
| Line 28: | Line 41: | ||
==== Sources ==== | ==== Sources ==== | ||
| − | + | '''General''' | |
| − | + | * https://www.getty.edu/research/tools/vocabularies/ | |
| + | '''On buildings''' | ||
| + | * https://www.wikidata.org/wiki/Wikidata:WikiProject_Cultural_venues/Typology | ||
| + | '''on arts organisations''' | ||
| + | * https://www.wikidata.org/wiki/Wikidata:WikiProject_Performing_arts | ||
| + | == Item level == | ||
On the level of an individual item, we try always to refer to a Wikidata item. | On the level of an individual item, we try always to refer to a Wikidata item. | ||
Latest revision as of 10:54, 13 August 2023
Introduction
Interoperability means the possibility to exchange and retrieve information between different datasets en systems without loss of information. We want Canonbase to be interoperble with as much systems as possible. Our core goal is to be interoperable with Wikidata, because this guarantees safeguarding of the information of our users.
Property level
The properties we use ensure that we capture the correct information in a way that we can analyse it. Secundary the choice of properties supports transferability with other sdata ystems, to retrieve and to export information.
Maching properties, in order to ensure they have the same meaning, is essential for the interoperability. This can be done on different levels of accuracy:
- a property is identical. (This is the highest level of interoperability.)
- a property is more detailed, but can fall back on a more general property. (This ensures we can export towards a main system, but needs work to inport.)
Example: we use [type of information] within sources, which can fall back to [instance of]
- a property shows similar information in a different way. (This needs some work to ensure interoperability, but is feasable and accurate.)
example: we use [significant date] with a qualifier [context] and [timeline label], Wikidata uses [significant event] with a [point in time] qualifier.
- a property does not exist in other property systems. (Here interoperability is only possible if we (are allowed to) create new properties in the existing systems.)
Example: properties for specific measurements of technical equipment.
- a property is less detailed than the existing ones in other systems. (This a situation we need to avoid.)
The relation with other systems should be documented in the property pages.
Sources
on buildings
- https://www.wikidata.org/wiki/Wikidata:WikiProject_Cultural_venues/Data_structure#Data_structure_for_venues
- https://www.wikidata.org/wiki/Wikidata:WikiProject_Cultural_venues/Data_structure#Notes_on_properties_for_cultural_venues
- https://www.wikidata.org/wiki/Wikidata:WikiProject_Performing_arts/Data_structure/Data_modelling_issues#List_of_properties_used_on_theatre_(venue)_items
- https://www.wikidata.org/wiki/Wikidata:WikiProject_Cultural_venues/Data_structure#Notes_on_properties_for_cultural_venues
- https://www.wikidata.org/wiki/Wikidata:WikiProject_Cultural_venues
- https://www.wikidata.org/wiki/Category:WikiProject_Cultural_venues
on arts organisations
On Archives
Taxonomy level
A taxonomy or controlled language is the way we define and structure things. In concreto, the taxonomies are often related to the expected values of one or more properties. For some properties, there are existing taxonomies. For other properties, we need to develop them ourselves.
In the first place we use the Wikidata taxonomies, where they usefull, and adapt them to our needs with respect for the reverse transferability.
Sources
General
On buildings
on arts organisations
Item level
On the level of an individual item, we try always to refer to a Wikidata item.