glam/schemas/20251121/linkml/examples/digital_platform_examples.yaml
2025-11-25 12:48:07 +01:00

163 lines
5.1 KiB
YAML

# Example Instances: Digital Platform Integration
# Demonstrates three use cases for DigitalPlatform class
---
# USE CASE 1: Physical Museum with Digital Platform
# Rijksmuseum (physical museum) with Rijksstudio (online collection platform)
- hc_id: https://nde.nl/ontology/hc/rijksmuseum-amsterdam
preferred_label:
- appellation_value: Rijksmuseum
appellation_language: nl
appellation_type: PREFERRED_NAME
custodian_type: MUSEUM # Physical museum (not DigitalPlatformType)
# Physical place
place_designation:
- settlement: Amsterdam
place_specificity: PRECISE
# Legal status
legal_status:
- legal_form: Foundation
legal_name: Stichting Rijksmuseum Amsterdam
# Digital platform (operational aspect)
digital_platform:
- platform_name: Rijksstudio
homepage_web_address: https://www.rijksmuseum.nl
collection_web_addresses:
- https://www.rijksmuseum.nl/nl/rijksstudio
api_endpoint: https://www.rijksmuseum.nl/api
iiif_support: true
linked_data: true
metadata_standards:
- Dublin Core
- EDM
- IIIF
programming_languages:
- JavaScript
- Python
repository_software: Custom CMS
refers_to_custodian: https://nde.nl/ontology/hc/rijksmuseum-amsterdam
was_generated_by:
activity_type: DIGITIZATION
temporal_extent:
begin_of_the_begin: "2012-01-01" # Rijksstudio launch date
end_of_the_end: null # Still operational
---
# USE CASE 2: Digital-First Aggregation Platform
# Europeana (born-digital heritage aggregator, no physical building)
- hc_id: https://nde.nl/ontology/hc/europeana
preferred_label:
- appellation_value: Europeana
appellation_language: en
appellation_type: PREFERRED_NAME
custodian_type: DIGITAL_PLATFORM # ← Digital-first custodian type
# No physical place (operates entirely online)
place_designation:
- settlement: The Hague # Legal registration address
place_specificity: ADMINISTRATIVE_ONLY
# Legal status
legal_status:
- legal_form: Foundation
legal_name: Stichting Europeana
# Digital platform (PRIMARY operational aspect for digital-first custodians)
digital_platform:
- platform_name: Europeana Collections
homepage_web_address: https://www.europeana.eu
collection_web_addresses:
- https://www.europeana.eu/en/collections
api_endpoint: https://api.europeana.eu
sparql_endpoint: https://sparql.europeana.eu
iiif_support: true
linked_data: true
metadata_standards:
- EDM
- Dublin Core
- SKOS
- IIIF
programming_languages:
- Java
- JavaScript
- Python
repository_software: Europeana Platform
access_restrictions: Open Access
refers_to_custodian: https://nde.nl/ontology/hc/europeana
was_generated_by:
activity_type: AGGREGATION
temporal_extent:
begin_of_the_begin: "2008-11-20" # Europeana launch date
end_of_the_end: null
---
# USE CASE 3: Archive with Multiple Digital Systems
# Noord-Hollands Archief (physical archive with inventory system, OAI-PMH, SPARQL)
- hc_id: https://nde.nl/ontology/hc/noord-hollands-archief
preferred_label:
- appellation_value: Noord-Hollands Archief
appellation_language: nl
appellation_type: PREFERRED_NAME
custodian_type: ARCHIVE # Physical archive
# Physical place
place_designation:
- settlement: Haarlem
place_specificity: PRECISE
# Legal status
legal_status:
- legal_form: PublicBody
legal_name: Noord-Hollands Archief
# Multiple digital platforms (multivalued)
digital_platform:
# Platform 1: Main website and inventory
- platform_name: Noord-Hollands Archief Website
homepage_web_address: https://www.noord-hollandsarchief.nl
inventory_web_addresses:
- https://www.noord-hollandsarchief.nl/onderzoek
metadata_standards:
- EAD
- Dublin Core
programming_languages:
- PHP
repository_software: Custom archive management system
refers_to_custodian: https://nde.nl/ontology/hc/noord-hollands-archief
temporal_extent:
begin_of_the_begin: "2001-01-01"
end_of_the_end: null
# Platform 2: OAI-PMH endpoint for metadata harvesting
- platform_name: NHA OAI-PMH Service
oai_pmh_endpoint: https://www.noord-hollandsarchief.nl/oai
metadata_standards:
- EAD
- Dublin Core
- OAI-PMH
refers_to_custodian: https://nde.nl/ontology/hc/noord-hollands-archief
temporal_extent:
begin_of_the_begin: "2010-01-01"
end_of_the_end: null
# Platform 3: SPARQL endpoint (hypothetical future platform)
- platform_name: NHA Linked Data Service
sparql_endpoint: https://data.noord-hollandsarchief.nl/sparql
linked_data: true
metadata_standards:
- RDF
- SKOS
- CIDOC-CRM
refers_to_custodian: https://nde.nl/ontology/hc/noord-hollands-archief
temporal_extent:
begin_of_the_begin: "2024-01-01"
end_of_the_end: null