kempersc/glam
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
glam/schemas/20251121/linkml/modules/classes/AuxiliaryDigitalPlatform.yaml
kempersc 174a420c08
All checks were successful
Deploy Frontend / build-and-deploy (push) Successful in 3m57s
Details
refactor(schema): centralize 1515 inline slot definitions per Rule 48 
- Remove inline slot definitions from 144 class files
- Create 7 new centralized slot files in modules/slots/:
  - custodian_type_broader.yaml
  - custodian_type_narrower.yaml
  - custodian_type_related.yaml
  - definition.yaml
  - finding_aid_access_restriction.yaml
  - finding_aid_description.yaml
  - finding_aid_temporal_coverage.yaml
- Add centralize_inline_slots.py automation script
- Update manifest with new timestamp

Rule 48: Class files must NOT define inline slots - all slots
must be imported from modules/slots/ directory.

Note: Pre-existing IdentifierFormat duplicate class definition
(in Standard.yaml and IdentifierFormat.yaml) not addressed in
this commit - requires separate schema refactor.
2026-01-11 22:02:14 +01:00

836 lines
29 KiB
YAML
Raw Blame History

id: https://nde.nl/ontology/hc/class/auxiliary-digital-platform
name: auxiliary_digital_platform_class
title: AuxiliaryDigitalPlatform Class
imports:
- linkml:types
- ./Custodian
- ./DigitalPlatform
- ./CustodianObservation
- ./ReconstructionActivity
- ./TimeSpan
- ./CollectionManagementSystem
- ./DigitalPlatformType
- ./DigitalPlatformTypes
- ./ReconstructedEntity
- ./DataServiceEndpoint
- ./OAIPMHEndpoint
- ./SearchAPI
- ./METSAPI
- ./FileAPI
- ./IIPImageServer
- ./EADDownload
- ../slots/technology_stack
- ../slots/funding_source
- ../slots/has_or_had_powered_by_cm
- ../slots/archived_at
- ../slots/serves_finding_aid
- ../slots/has_or_had_data_service_endpoint
- ../slots/api_documentation
- ../slots/has_or_had_archival_status
- ../slots/auxiliary_platform_id
- ../slots/has_auxiliary_platform_type
- ../slots/cms_detected
- ../slots/fixity_info
- ../slots/iiif_support
- ../slots/is_auxiliary_of_platform
- ../slots/linked_data
- ../slots/platform_description
- ../slots/platform_name
- ../slots/platform_purpose
- ../slots/platform_url
- ../slots/preservation_event_type
- ../slots/provides_access_to
- ../slots/refers_to_custodian
- ../slots/related_project
- ../slots/specificity_annotation
- ../slots/template_specificity
- ../slots/temporal_extent
- ../slots/valid_from
- ../slots/valid_to
- ../slots/was_derived_from
- ../slots/was_generated_by
- ./SpecificityAnnotation
- ./TemplateSpecificityScores
- ../slots/has_auxiliary_platform_identifier
- ../slots/has_api_documentation_url
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
dcat: http://www.w3.org/ns/dcat#
dcterms: http://purl.org/dc/terms/
foaf: http://xmlns.com/foaf/0.1/
prov: http://www.w3.org/ns/prov#
skos: http://www.w3.org/2004/02/skos/core#
doap: http://usefulinc.com/ns/doap#
premis: http://www.loc.gov/premis/rdf/v3/
crm: http://www.cidoc-crm.org/cidoc-crm/
classes:
AuxiliaryDigitalPlatform:
is_a: ReconstructedEntity
class_uri: dcat:Catalog
description: "Subordinate or project-based digital platform associated with a heritage custodian.\n\n**CRITICAL DISTINCTION\
\ - THREE-TIER DIGITAL PLATFORM MODEL**:\n\n1. **DigitalPlatform** (main digital entry point):\n - Primary web presence\
\ of the custodian\n - Main website, primary API, flagship digital platform\n - Like CustodianPlace is the preferred\
\ place reference\n - Examples: rijksmuseum.nl, europeana.eu, nationaalarchief.nl\n \n2. **AuxiliaryDigitalPlatform**\
\ (subordinate platforms) - THIS CLASS:\n - Secondary digital properties: project sites, exhibition microsites\n \
\ - Like CustodianAppellation is to CustodianName\n - Examples: project websites, temporary exhibition portals, specialized\
\ tools\n \n3. **DigitalPlatformType** (custodian type classification):\n - For digital-FIRST custodians (no physical\
\ building)\n - Applied at Custodian.custodian_type level\n - Examples: Europeana (aggregation platform), Internet\
\ Archive\n\n**DCAT ALIGNMENT**:\n\n`dcat:Catalog` - \"A curated collection of metadata about datasets\"\n\nKey properties:\n\
- `dcat:dataset` - links to datasets/collections\n- `dcat:service` - data services provided\n- `dcterms:isPartOf` -\
\ links to parent catalog\n\n**RELATIONSHIP TO DIGITALPLATFORM**:\n\nAuxiliaryDigitalPlatform represents SUBORDINATE\
\ digital presence\nDigitalPlatform represents PRIMARY digital entry point\n\n```\nCustodian (hub)\n │\n └── digital_platform\
\ → DigitalPlatform (main digital entry)\n └── auxiliary_platforms → AuxiliaryDigitalPlatform (project sites)\n\
```\n\n**USE CASES**:\n\n1. **Project Websites**:\n - Rijksmuseum → Rijksstudio API (separate from main website)\n\
\ - National Archives → WW2 Portal (thematic project)\n\n2. **Exhibition Microsites**:\n - Temporary exhibition\
\ with dedicated website\n - Virtual tour for specific collection\n\n3. **Specialized Tools/Apps**:\n - Mobile app\
\ (separate from responsive website)\n - Collection browser tool\n - Crowdsourcing platform\n\n4. **Legacy/Archived\
\ Platforms**:\n - Previous website versions\n - Deprecated APIs still in use\n\n5. **Grant-Funded Projects**:\n\
\ - EU-funded digitization project portal\n - Research project data portal\n\n6. **Educational Platforms**:\n \
\ - Teacher resources portal\n - Student learning modules\n - Workshop booking system\n\n**Example - Rijksmuseum\
\ Auxiliary Platforms**:\n```yaml\nCustodian:\n hc_id: \"https://nde.nl/ontology/hc/nl-nh-ams-m-rm-q190804\"\n preferred_label:\
\ \"Rijksmuseum\"\n digital_platform:\n - platform_name: \"Rijksmuseum Website\"\n homepage_web_address: \"\
https://www.rijksmuseum.nl/\"\n auxiliary_platforms:\n - platform_name: \"Rijksstudio\"\n auxiliary_platform_type:\
\ PROJECT_WEBSITE\n platform_url: \"https://www.rijksmuseum.nl/nl/rijksstudio\"\n platform_purpose:\
\ \"Personal collection creation and high-res image downloads\"\n - platform_name: \"Rijksmuseum Data API\"\n\
\ auxiliary_platform_type: API_ENDPOINT\n platform_url: \"https://data.rijksmuseum.nl/\"\n \
\ platform_purpose: \"Developer access to collection metadata and images\"\n - platform_name: \"Night Watch\
\ Experience\"\n auxiliary_platform_type: EXHIBITION_MICROSITE\n platform_url: \"https://www.rijksmuseum.nl/en/stories/operation-night-watch\"\
\n platform_purpose: \"Interactive exploration of Night Watch research project\"\n```\n\n**TEMPORAL VALIDITY**:\n\
\nAuxiliary platforms often have finite lifespans:\n- Exhibition microsite: opens with exhibition, archived after closure\n\
- Project portal: funded period, then deprecated or integrated\n- Legacy platforms: valid_to when replaced by new system\n"
exact_mappings:
- dcat:Catalog
close_mappings:
- schema:WebSite
- schema:WebApplication
- dcat:DataService
- foaf:Document
- doap:Project
related_mappings:
- dcterms:isPartOf
- schema:isRelatedTo
- dcat:servesDataset
slots:
- api_documentation
- has_or_had_archival_status
- archived_at
- auxiliary_platform_id
- has_auxiliary_platform_type
- cms_detected
- has_or_had_data_service_endpoint
- fixity_info
- funding_source
- iiif_support
- is_auxiliary_of_platform
- linked_data
- platform_description
- platform_name
- platform_purpose
- platform_url
- has_or_had_powered_by_cm
- preservation_event_type
- provides_access_to
- refers_to_custodian
- related_project
- serves_finding_aid
- specificity_annotation
- technology_stack
- template_specificity
- temporal_extent
- valid_from
- valid_to
- was_derived_from
- was_generated_by
slot_usage:
has_auxiliary_platform_identifier:
slot_uri: dcterms:identifier
description: 'Unique identifier for this auxiliary digital platform.
Format: URI following NDE Heritage Custodian ontology conventions.
'
range: uriorcurie
required: true
identifier: true
examples:
- value: https://nde.nl/ontology/hc/aux-platform/rijksmuseum-rijksstudio
description: Rijksstudio platform ID
platform_name:
slot_uri: dcterms:title
description: 'Name of this auxiliary digital platform.
Dublin Core: title for resource name.
This is the human-readable name of the secondary platform.
'
range: string
required: true
examples:
- value: Rijksstudio
description: Personal collection tool
- value: Operation Night Watch
description: Research project microsite
- value: WW2 Portal
description: Thematic archive portal
has_auxiliary_platform_type:
slot_uri: dcterms:type
description: 'Type of auxiliary platform using DigitalPlatformType class hierarchy.
**Unified Type System** (replaces AuxiliaryDigitalPlatformTypeEnum):
Auxiliary platforms use the same unified type hierarchy as DigitalPlatform,
with types from the AUXILIARY category being most relevant:
- ProjectWebsite: Dedicated project site
- ExhibitionMicrosite: Temporary exhibition portal
- APIEndpoint: Programmatic interface (separate from main API)
- MobileApp: Native or hybrid mobile application
- CollectionBrowser: Specialized collection exploration tool
- CrowdsourcingPlatform: User contribution portal
- EducationalPortal: Learning resources
- DataPortal: Dataset download/access
- LegacyPlatform: Deprecated but maintained platform
- VirtualTour: 360 or immersive experience
See DigitalPlatformTypes.yaml for all 69 concrete platform types.
Dublin Core: type for classification.
'
range: DigitalPlatformType
required: true
examples:
- value: ProjectWebsite
description: Project site type
- value: ExhibitionMicrosite
description: Exhibition microsite type
platform_url:
slot_uri: foaf:homepage
description: 'URL of this auxiliary digital platform.
FOAF: homepage for web address.
This is the entry point URL for the platform.
'
range: uri
required: true
pattern: ^https?://
examples:
- value: https://www.rijksmuseum.nl/nl/rijksstudio
description: Rijksstudio URL
- value: https://data.rijksmuseum.nl/
description: Data API URL
platform_purpose:
slot_uri: dcterms:description
description: 'Brief description of what this platform provides/enables.
Dublin Core: description for purpose statement.
Focus on user benefit and functionality.
'
range: string
examples:
- value: Personal collection creation and high-res image downloads
description: Rijksstudio purpose
- value: Interactive exploration of Night Watch research project
description: Exhibition microsite purpose
platform_description:
slot_uri: dcterms:abstract
description: 'Detailed description of this auxiliary platform.
Dublin Core: abstract for longer description.
Include:
- Full functionality description
- Target audience
- Technical requirements
- Relationship to main platform
'
range: string
examples:
- value: Rijksstudio allows users to create personal collections from the Rijksmuseum's digitized artworks, download
high-resolution images, and share curated sets with others.
description: Detailed platform description
has_api_documentation_url:
slot_uri: dcat:endpointDescription
description: 'URL to API documentation (for API-type platforms).
DCAT: endpointDescription for API documentation.
'
range: uri
examples:
- value: https://data.rijksmuseum.nl/object-metadata/api/
description: API documentation URL
technology_stack:
slot_uri: doap:programming-language
description: 'Technologies used to build this platform.
DOAP: programming-language for technical implementation.
(DOAP = Description of a Project, W3C vocabulary for software projects)
Include frameworks, languages, services.
'
range: string
multivalued: true
examples:
- value: React
description: Frontend framework
- value: Python/Django
description: Backend stack
is_auxiliary_of_platform:
slot_uri: dcterms:isPartOf
description: 'Link back to the DigitalPlatform that this is an auxiliary of.
Dublin Core: isPartOf links part to whole.
Like CustodianAppellation.variant_of_name → CustodianName,
this links AuxiliaryDigitalPlatform → DigitalPlatform (main platform).
'
range: DigitalPlatform
required: true
examples:
- value: https://nde.nl/ontology/hc/platform/rijksmuseum-website
description: Main Rijksmuseum website
provides_access_to:
slot_uri: dcat:servesDataset
description: 'Collections or datasets accessible through this platform.
DCAT: servesDataset for data service relationship.
Link to CustodianCollection or dataset identifiers.
'
range: uriorcurie
multivalued: true
examples:
- value: https://nde.nl/ontology/hc/collection/rm-paintings
description: Paintings collection
related_project:
slot_uri: dcterms:isPartOf
description: 'Research project or initiative this platform supports.
Dublin Core: isPartOf for project relationship.
Useful for grant-funded or research project platforms.
'
range: string
examples:
- value: Operation Night Watch
description: Research project name
- value: 'EU Horizon 2020 Grant #123456'
description: Grant reference
funding_source:
slot_uri: schema:funder
description: 'Organization or grant funding this platform.
Schema.org: funder for funding relationship.
'
range: string
examples:
- value: European Commission Horizon 2020
description: EU funding
- value: Mondriaan Fund
description: Dutch cultural fund
iiif_support:
slot_uri: dcterms:conformsTo
description: 'Does this platform support IIIF?
Dublin Core: conformsTo for standard compliance.
'
range: boolean
examples:
- value: true
description: IIIF enabled
linked_data:
slot_uri: dcterms:conformsTo
description: 'Does this platform provide linked open data?
Dublin Core: conformsTo for LOD compliance.
'
range: boolean
examples:
- value: true
description: Provides RDF/JSON-LD
valid_from:
slot_uri: schema:validFrom
description: 'Date when this auxiliary platform was launched.
Track when project sites, microsites opened.
'
range: date
examples:
- value: '2018-06-01'
description: Platform launched June 2018
valid_to:
slot_uri: schema:validThrough
description: 'Date when this auxiliary platform was decommissioned.
NULL if still active.
Important for temporary exhibition sites and project portals.
'
range: date
examples:
- value: '2021-12-31'
description: Exhibition site closed end of 2021
temporal_extent:
slot_uri: crm:P4_has_time-span
description: 'Temporal period during which this platform was operational.
CIDOC-CRM: P4_has_time-span for fuzzy temporal boundaries.
'
range: TimeSpan
examples:
- value:
begin_of_the_begin: '2018-01-01'
end_of_the_end: '2021-12-31'
description: Project period 2018-2021
has_or_had_archival_status:
slot_uri: schema:creativeWorkStatus
description: 'Current status of platform if no longer active.
Schema.org: creativeWorkStatus for lifecycle status.
PREMIS: Aligns with premis:OutcomeStatus for preservation outcomes.
Values:
- ACTIVE: Currently operational
- DEPRECATED: Still accessible but not maintained
- ARCHIVED: Preserved in web archive (premis:Event type: web_harvest)
- OFFLINE: No longer accessible
- MIGRATED: Content migrated to new platform (premis:Event type: migration)
For formal preservation tracking, use preservation_event to link
to PREMIS Event instances documenting the archival process.
'
range: string
examples:
- value: ARCHIVED
description: Preserved in web archive
- value: DEPRECATED
description: Still accessible but not maintained
- value: MIGRATED
description: Content migrated to successor platform
was_archived_at:
slot_uri: schema:archivedAt
description: 'URL to archived version (e.g., Internet Archive Wayback Machine).
Schema.org: archivedAt for archive location.
'
range: uri
examples:
- value: https://web.archive.org/web/20211231/https://example.nl/exhibition/
description: Wayback Machine URL
preservation_event_type:
slot_uri: premis:outcome
description: 'Type of preservation event that occurred (if platform was archived/migrated).
PREMIS: Aligns with premis:Event and premis:OutcomeStatus.
Event types from Library of Congress PREMIS vocabulary:
- "web_harvest": Captured via web archiving (Wayback Machine, Archive-It)
- "migration": Content migrated to new format/platform
- "normalization": Files normalized to preservation formats
- "validation": Integrity/format validation performed
- "deletion": Content intentionally removed
- "replication": Content copied to additional storage
See: http://id.loc.gov/vocabulary/preservation/eventType
'
range: string
required: false
examples:
- value: web_harvest
description: Platform captured via Internet Archive
- value: migration
description: Content migrated to successor platform
fixity_info:
slot_uri: premis:fixity
description: 'Fixity/checksum information for archived content.
PREMIS: fixity provides integrity verification data.
Format: "algorithm:checksum_value" or structured object.
Examples:
- "sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
- "md5:d41d8cd98f00b204e9800998ecf8427e"
Used when has_or_had_archival_status is ARCHIVED or MIGRATED to verify
integrity of preserved content.
'
range: string
required: false
examples:
- value: sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
description: SHA-256 checksum of archived content
cms_detected:
slot_uri: schema:softwareApplication
range: boolean
required: false
description: 'Flag indicating whether a CMS backend was detected for this platform.
Schema.org: softwareApplication indicates software is involved.
**Detection Methods**:
- HTTP response headers (X-Powered-By, Server)
- HTML meta tags (generator)
- URL patterns (e.g., /providence/, /omeka/)
- JavaScript libraries or framework signatures
- Admin panel detection
**Values**:
- true: CMS backend detected (see powered_by_cms for identity)
- false: No CMS detected (likely static site or custom-built)
- null: Detection not performed or inconclusive
**Use Cases**:
1. "Does this auxiliary platform have a known CMS?" → Check cms_detected
2. Technical survey: Identify platforms needing CMS identification
3. Migration planning: Prioritize platforms with detected CMS
'
examples:
- value: true
description: CMS backend detected
- value: false
description: No CMS detected (static site)
has_or_had_powered_by_cm:
slot_uri: crm:P33i_was_used_by
range: CollectionManagementSystem
multivalued: true
required: false
description: 'Collection Management System(s) powering this auxiliary platform.
CIDOC-CRM: P33i_was_used_by (inverse of P33_used_specific_technique).
**Relationship to cms_detected**:
- If cms_detected = true and powered_by_cms is set → CMS identified
- If cms_detected = true and powered_by_cms is null → CMS detected but not identified
- If cms_detected = false → powered_by_cms should be null
**Use Cases**:
1. "What CMS powers this project website?" → Follow powered_by_cms
2. "What auxiliary platforms use this CMS?" → Reverse query
3. Platform inventory: Map all CMS deployments across institution
'
examples:
- value: https://nde.nl/ontology/hc/cms/rijksmuseum-adlib
description: Auxiliary platform powered by Adlib CMS
was_derived_from:
slot_uri: prov:wasDerivedFrom
description: 'CustodianObservation(s) documenting this platform.
PROV-O: wasDerivedFrom for observation provenance.
'
range: CustodianObservation
multivalued: true
required: false
was_generated_by:
slot_uri: prov:wasGeneratedBy
description: 'ReconstructionActivity that generated this platform record.
PROV-O: wasGeneratedBy for generation activity.
'
range: ReconstructionActivity
required: false
refers_to_custodian:
slot_uri: dcterms:references
description: 'The Custodian hub that operates this auxiliary platform.
Dublin Core: references for entity reference.
All auxiliary platforms MUST reference the main custodian hub.
'
range: Custodian
required: true
examples:
- value: https://nde.nl/ontology/hc/nl-nh-ams-m-rm-q190804
description: Rijksmuseum custodian hub
serves_finding_aid:
slot_uri: rico:isOrWasProviderOf
range: uriorcurie
multivalued: true
inlined_as_list: true
required: false
description: 'Finding aids hosted/served by this auxiliary digital platform.
**INVERSE RELATIONSHIP**:
- Forward: FindingAid.served_by → AuxiliaryDigitalPlatform (finding aid served by platform)
- Inverse: AuxiliaryDigitalPlatform.serves_finding_aids → FindingAid[] (platform serves)
**RiC-O ALIGNMENT**:
`rico:isOrWasProviderOf` - The agent (platform) provides the finding aid.
**USE CASES**:
1. Project website hosting specialized finding aids
2. API endpoint providing programmatic access to finding aids
3. Exhibition microsite with collection guides
'
examples:
- value: https://nde.nl/ontology/hc/finding-aid/rm/night-watch-guide
description: Night Watch Exhibition finding aid
has_or_had_data_service_endpoint:
slot_uri: dcat:servesDataset
range: DataServiceEndpoint
multivalued: true
inlined_as_list: true
required: false
description: 'Data service endpoints exposed by this auxiliary digital platform.
**DCAT ALIGNMENT**:
`dcat:servesDataset` - Links a DataService to the datasets it serves.
**ENDPOINT TYPES**:
This polymorphic slot can contain any subclass of DataServiceEndpoint:
- OAIPMHEndpoint: OAI-PMH metadata harvesting endpoints
- SearchAPI: REST/JSON search API endpoints
- METSAPI: METS document retrieval endpoints
- FileAPI: File/asset download endpoints
- IIPImageServer: IIP/IIIF image server endpoints
- EADDownload: EAD finding aid download endpoints
**USE CASES**:
1. "What APIs does this auxiliary platform expose?" → Follow data_service_endpoints
2. Project website with dedicated API → Document endpoint details
3. Exhibition microsite with IIIF viewer → Link to image server
'
examples:
- value:
- endpoint_id: https://nde.nl/ontology/hc/endpoint/rijksstudio-api
endpoint_name: Rijksstudio Image API
endpoint_url: https://www.rijksmuseum.nl/api/nl/collection
protocol: REST_JSON
status: ACTIVE
description: Rijksstudio auxiliary platform endpoints
specificity_annotation:
range: SpecificityAnnotation
inlined: true
template_specificity:
range: TemplateSpecificityScores
inlined: true
comments:
- AuxiliaryDigitalPlatform models SUBORDINATE digital properties
- DigitalPlatform models PRIMARY digital entry point
- Analogous to CustodianAppellation for alternative names
- DCAT dcat:Catalog for secondary data catalogs/services
- Temporal validity tracks platform lifecycle (launched/deprecated/archived)
- Links back to DigitalPlatform via is_auxiliary_of_platform
- Important for project-based and exhibition microsites with finite lifespans
see_also:
- https://www.w3.org/TR/vocab-dcat-2/#Class:Catalog
- https://www.w3.org/TR/vocab-dcat-2/#Property:catalog_service
- https://schema.org/archivedAt
- http://usefulinc.com/ns/doap#
examples:
- value:
auxiliary_platform_id: https://nde.nl/ontology/hc/aux-platform/rijksmuseum-rijksstudio
platform_name: Rijksstudio
auxiliary_platform_type: ProjectWebsite
platform_url: https://www.rijksmuseum.nl/nl/rijksstudio
platform_purpose: Personal collection creation and high-res image downloads
platform_description: Rijksstudio allows users to create personal collections from the Rijksmuseum's digitized artworks,
download high-resolution images, and share curated sets with others.
is_auxiliary_of_platform: https://nde.nl/ontology/hc/platform/rijksmuseum-website
provides_access_to:
- https://nde.nl/ontology/hc/collection/rm-paintings
- https://nde.nl/ontology/hc/collection/rm-prints
iiif_support: true
linked_data: false
valid_from: '2012-10-01'
archival_status: ACTIVE
refers_to_custodian: https://nde.nl/ontology/hc/nl-nh-ams-m-rm-q190804
description: Rijksstudio personal collection platform
- value:
auxiliary_platform_id: https://nde.nl/ontology/hc/aux-platform/rijksmuseum-data-api
platform_name: Rijksmuseum Data API
auxiliary_platform_type: APIEndpoint
platform_url: https://data.rijksmuseum.nl/
platform_purpose: Developer access to collection metadata and images
api_documentation: https://data.rijksmuseum.nl/object-metadata/api/
technology_stack:
- REST
- JSON
is_auxiliary_of_platform: https://nde.nl/ontology/hc/platform/rijksmuseum-website
iiif_support: true
linked_data: true
valid_from: '2013-03-01'
archival_status: ACTIVE
refers_to_custodian: https://nde.nl/ontology/hc/nl-nh-ams-m-rm-q190804
description: Rijksmuseum developer API
- value:
auxiliary_platform_id: https://nde.nl/ontology/hc/aux-platform/rm-night-watch-experience
platform_name: Operation Night Watch
auxiliary_platform_type: ExhibitionMicrosite
platform_url: https://www.rijksmuseum.nl/en/stories/operation-night-watch
platform_purpose: Interactive exploration of Night Watch research project
related_project: Operation Night Watch
funding_source: ING Bank
is_auxiliary_of_platform: https://nde.nl/ontology/hc/platform/rijksmuseum-website
iiif_support: true
valid_from: '2019-07-01'
archival_status: ACTIVE
refers_to_custodian: https://nde.nl/ontology/hc/nl-nh-ams-m-rm-q190804
description: Night Watch research project microsite
- value:
auxiliary_platform_id: https://nde.nl/ontology/hc/aux-platform/na-ww2-portal
platform_name: WW2 Archives Portal
auxiliary_platform_type: ProjectWebsite
platform_url: https://www.nationaalarchief.nl/onderzoeken/zoekhulpen/ww2
platform_purpose: Thematic portal for World War 2 archival research
platform_description: Specialized portal providing access to WW2-related archives including resistance records, persecution
documents, and liberation materials.
is_auxiliary_of_platform: https://nde.nl/ontology/hc/platform/nationaal-archief-website
provides_access_to:
- https://nde.nl/ontology/hc/collection/na-resistance-archives
- https://nde.nl/ontology/hc/collection/na-liberation-photos
valid_from: '2015-05-05'
archival_status: ACTIVE
refers_to_custodian: https://nde.nl/ontology/hc/nl-na
description: National Archives WW2 thematic portal
Reference in a new issue View git blame Copy permalink