How data flows in and out of Artsdata.ca. Click a circle in the image to learn more about it.
- Artsdata.ca Website
- Data Consumers
- Artsdata Data Model & Ontology
- Google Spreadsheets & Data-to-RDF
- Culture Creates Footlight
- Graph-store API
- Artsdata Image Server (IIIF)
- Query API
- SPARQL Endpoint & Federation
- Artsdata Triplestore
- Culture Creates Wringer
Artsdata is a knowledge graph specialized in the Canadian Arts Sector and focused on performing arts events.
Artsdata aggregates descriptive metadata related to cultural events (performing arts, and soon galleries and museums) from multiple websites and external databases and, when needed, mints URIs for named entities. Data is published as Linked Open Data with URIs that can be used to link events to artists, venues and arts organizations.
For an overview of knowledge graphs and why the arts sector in Canada should have one, take a look at this 6 minute video by Tammy Lee, CEO of Culture Creates.
The Artsdata data model is implemented using classic RDF ontologies and maps data to a multitude of other classic (i.e. FRBR) and non-classic (i.e. Wikidata) ontologies.
The long term goal of Artsdata is to have the most complete and highest quality descriptive metadata on cultural events in Canada, including productions and artists from around the world being presented in Canada. And at a later stage all events of Canadian artists performing abroad.
The open data ecosystem is divided into 3 areas:
- Data providers
- Data consumers
For Data providers, such as arts organizations (producers, presenters, agents, venues) and artists, a range of ETL tools are available (see Provence data for a listing of tools in action), as well as an API (Graph-store API) for 3rd party developers that accepts RDF data meeting all Artsdata data modelling requirements and constraints (SHACL defined in Artsdata.ca or ShEx when coming from Wikidata.) All data submited to Artsdata.ca requires a user account registered with artsdata.ca, and valid provenance data (also constrained by the Artsdata data model), unless you are using the DBpedia Databus with WebID (PKCS12 Certificate) in which case no artsdata.ca account is needed. All data submitted to artsdata.ca is agreed upon by the registered account to be CC0.
Data from each source is loaded into its own graph within Artsdata.ca with provenance metadata including a contact point, contributor names and data related license agreements.
3rd party developers are welcome and can use the Artsdata Graph-store API to load data. An OpenRefine plugin would be a great addition!
Update 03-SEP-2020: Artsdata is now working with DBpedia Databus, and will accept data uploaded to the Databus. If you are a developer you can get started with some resources here https://github.com/culturecreates/dbpedia-databus-resources
All services are open and freely accessible, except for loading data into Artsdata, which requires a user account. In principle, anyone can load data using the Load API as long as they meet the Artsdata data model requirements outlined in the Artsdata data model documentation.
Data consumers, such as listing sites, search engines, government bodies and Arts Organizations wanting to use the data, can call the Artsdata Query API that provides several methods available from an iCalendar feed to a RESTful API, to a SPARQL endpoint (read only) or obtain a triples data dump serialized as N-Quads. An account is required and used to store personal configurations if desired. The data from Artsdata.ca is CC0 and can be used in other applications without any restrictions.