kempersc/glam
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update manifest.json timestamp and refactor descriptions in YAML schema files for clarity

Browse source
This commit is contained in:
kempersc 2026-01-31 00:22:16 +01:00
parent 6203d19875
commit 56a7001e45
12 changed files with 2 additions and 294 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
frontend/public/schemas/20251121/linkml/manifest.json
View file

@ -1,5 +1,5 @@
{
"generated": "2026-01-30T23:15:53.330Z",
"generated": "2026-01-30T23:21:50.921Z",
"schemaRoot": "/schemas/20251121/linkml",
"totalFiles": 3003,
"categoryCounts": {

2
schemas/20251121/linkml/manifest.json
View file

@ -1,5 +1,5 @@
{
"generated": "2026-01-30T23:21:50.921Z",
"generated": "2026-01-30T23:22:16.389Z",
"schemaRoot": "/schemas/20251121/linkml",
"totalFiles": 3003,
"categoryCounts": {

21
schemas/20251121/linkml/modules/classes/ConflictStatus.yaml
View file

@ -35,9 +35,7 @@ classes:
range: ConflictStatusEnum
required: true
description: 'The current status of the institution regarding conflict/disaster impact.
Uses ConflictStatusEnum values: DESTROYED, DAMAGED, THREATENED, etc.
'
examples:
- value: destroyed
@ -48,19 +46,11 @@ classes:
slot_uri: crm:P4_has_time-span
range: date
description: 'Date when destruction/damage occurred.
For single events, use exact date.
For gradual destruction, use start of period.
**Note**: For fuzzy temporal bounds, use `time_of_destruction` (TimeSpan).
**Renamed**: Was ''date'', renamed to ''destruction_date'' to avoid collision
with built-in ''date'' type.
'
examples:
- value: '2023-12-08'
@ -73,11 +63,8 @@ classes:
slot_uri: prov:generatedAtTime
range: date
description: 'Date when the destruction/damage was reported or documented.
May differ from `destruction_date` when reports are delayed.
Important for provenance tracking.
'
examples:
- value: '2024-01-15'
@ -86,15 +73,10 @@ classes:
slot_uri: schema:description
range: string
description: 'Human-readable description of the destruction/damage event.
Should include:
- Type of damage (destroyed, damaged, looted)
- Cause (airstrike, fire, looting, natural disaster)
- Impact on collections (if known)
'
examples:
- value: Library destroyed by Israeli airstrike during Gaza conflict. All collections lost.
@ -112,11 +94,8 @@ classes:
range: string
multivalued: true
description: 'List of sources documenting the destruction/damage.
Include report names, news articles, official statements.
These are displayed in the frontend for transparency.
'
examples:
- value: Librarians and Archivists with Palestine - Gaza Report 2024

18
schemas/20251121/linkml/modules/classes/DataFormat.yaml
View file

@ -1,15 +1,12 @@
id: https://nde.nl/ontology/hc/class/DataFormat
name: data_format_class
title: Data Format
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
dct: http://purl.org/dc/terms/
default_prefix: hc
imports:
- linkml:types
- ../slots/has_or_had_description
@ -24,22 +21,18 @@ classes:
class_uri: hc:DataFormat
description: |
Specification of a data format for files, APIs, or data streams.
**DEFINITION**:
DataFormat captures format characteristics including type, media type,
schema references, and encoding specifications.
**USAGE**:
- API response formats (JSON, XML, RDF)
- File formats (CSV, Excel, PDF, TIFF)
- Streaming protocols (MQTT, WebSocket payloads)
- Archival formats (METS, EAD, MARC)
**ONTOLOGY ALIGNMENT**:
- **Primary** (`class_uri`): `hc:DataFormat` - Heritage Custodian class
- **Close**: `dct:MediaTypeOrExtent` - Dublin Core media type
- **Close**: `schema:encodingFormat` - Schema.org encoding
**Common Format Types**:
| Type | Media Type | Use Case |
|------|------------|----------|
@ -48,7 +41,6 @@ classes:
| CSV | text/csv | Data exports, tabular |
| RDF | application/rdf+xml | Linked data |
| SensorML | application/xml | Sensor metadata |
**Example**:
```yaml
has_or_had_format:
@ -56,11 +48,9 @@ classes:
has_or_had_media_type: "application/json"
has_or_had_encoding: "UTF-8"
```
close_mappings:
- dct:MediaTypeOrExtent
- schema:encodingFormat
slots:
- has_or_had_type
- has_or_had_label
@ -68,7 +58,6 @@ classes:
- has_or_had_media_type
- has_or_had_encoding
- has_or_had_schema_url
slot_usage:
has_or_had_type:
range: uriorcurie
@ -110,7 +99,6 @@ classes:
examples:
- value: "https://api.museum.nl/schemas/v1/climate.json"
description: JSON Schema URL
attributes:
has_or_had_media_type:
range: string
@ -121,30 +109,24 @@ classes:
has_or_had_schema_url:
range: uri
description: URL to schema definition.
annotations:
custodian_types: '["*"]'
custodian_types_rationale: "Data format specifications apply to all custodian types with digital systems."
specificity_score: 0.55
specificity_rationale: "Moderately specific to digital platform and API contexts."
# Type class for format taxonomy (Rule 0b: Type/Types pattern)
DataFormatType:
class_uri: hc:DataFormatType
abstract: true
description: |
Abstract base class for data format type taxonomy.
**Type/Types Pattern** (Rule 0b):
- `DataFormatType` (this file): Abstract base class
- `DataFormatTypes.yaml`: Concrete subclasses (JsonFormat, XmlFormat, etc.)
Subclasses define specific format types used in heritage data systems.
slots:
- has_or_had_label
- has_or_had_description
annotations:
custodian_types: '["*"]'
custodian_types_rationale: "Format types applicable universally."

5
schemas/20251121/linkml/modules/classes/DigitalArchive.yaml
View file

@ -79,11 +79,8 @@ classes:
description: NDSA Level 3 - Monitor
has_or_had_interface:
description: 'Access interface for the digital archive.
MIGRATED from has_access_interface_url per Rule 53.
Uses AccessInterface class.
'
range: AccessInterface
inlined: true
@ -97,9 +94,7 @@ classes:
range: uriorcurie
multivalued: true
description: 'File formats supported/preferred by the digital archive.
MIGRATED from supported_format slot per slot_fixes.yaml (Rule 53/56, 2026-01-16).
'
examples:
- value:

21
schemas/20251121/linkml/modules/classes/EducationCenter.yaml
View file

@ -110,15 +110,12 @@ classes:
description: The name of the education center.
examples:
- value: 'label_text: Rijksmuseum Educatie Centrum
'
description: Museum education center
- value: 'label_text: Nationaal Archief Leercentrum
'
description: Archive learning center
- value: 'label_text: KB Workshops & Trainingen
'
description: Library education facility
has_or_had_description:
@ -127,16 +124,12 @@ classes:
description: A description of the education center.
examples:
- value: 'description_text: Dedicated education facility offering school programs, family workshops, and teacher training. Features 4 classroom spaces and hands-on workshop areas.
'
description: Museum education center
has_or_had_type:
description: 'Classification of the education center.
MIGRATED from education_center_type per slot_fixes.yaml (Rule 53).
Uses EducationFacilityType class.
'
range: EducationFacilityType
inlined: true
@ -147,11 +140,8 @@ classes:
description: Dedicated education center
has_or_had_equipment:
description: 'AV equipment available in the education center.
MIGRATED from has_av_equipment per Rule 53.
Uses AVEquipment class.
'
range: AVEquipment
required: false
@ -176,21 +166,16 @@ classes:
inlined: true
multivalued: true
description: 'Target audiences served by this education center.
MIGRATED 2026-01-15: Uses UserCommunity class to capture audience information.
'
examples:
- value: 'community_name: "Primary schools"
'
description: Elementary age students
- value: 'community_name: "Families"
'
description: Family groups
- value: 'community_name: "Adult learners"
'
description: Adults
has_or_had_program:
@ -214,13 +199,9 @@ classes:
inlined: true
multivalued: true
description: 'Classroom facilities at this education center.
MIGRATED 2026-01-19: Replaces classroom_count slot per Rule 53.
Uses Classroom class (subclass of Facility) with has_or_had_quantity
and has_or_had_unit for structured room counting.
'
examples:
- value: "facility_name: \"Main Classroom Wing\"\nhas_or_had_quantity:\n numeric_value: 4\nhas_or_had_unit:\n unit_type: CLASSROOM\nseating_capacity: 120\nav_equipped: true\n"
@ -250,9 +231,7 @@ classes:
is_or_was_required:
range: boolean
description: 'Whether advance booking is required for education programs.
MIGRATED 2026-01-15: Replaces booking_required slot.
'
examples:
- value: true

17
schemas/20251121/linkml/modules/classes/ExhibitionCatalog.yaml
View file

@ -106,7 +106,6 @@ classes:
multivalued: true
inlined: true
description: 'Identifiers for the exhibition catalog. Includes: - Primary catalog identifier (required, first value) - MIGRATED from catalog_id (2026-01-17) - WikiDataIdentifier: Wikidata Q-number - MIGRATED from wikidata_id (2026-01-15) - WorldCatIdentifier: OCLC WorldCat ID - MIGRATED from worldcat_id (2026-01-14)
First identifier serves as primary key. Uses structured identifier classes per Rule 53.'
any_of:
- range: uriorcurie
@ -149,7 +148,6 @@ classes:
range: uriorcurie
multivalued: true
description: 'Type classification for the catalog. Supports multiple type facets: - Catalog format type: PRINT_CATALOG, DIGITAL_CATALOG, HYBRID_CATALOG - Binding type: BindingType class (hc:HardcoverBinding, hc:PaperbackBinding, etc.)
MIGRATED from catalog_type (2026-01-17) and binding (2026-01-15) per Rule 53/56. Uses multivalued to support both format and binding classification simultaneously.'
any_of:
- range: string
@ -168,9 +166,7 @@ classes:
multivalued: true
inlined: true
description: 'Authors of the exhibition catalog.
MIGRATED from authors (string list) to structured Author class.
'
examples:
- value:
@ -183,11 +179,8 @@ classes:
description: Contributing author
contains_or_contained:
description: 'Essays or textual content contained in the catalog.
MIGRATED from has_or_had_essay per Rule 53.
Uses Essay class.
'
range: Essay
multivalued: true
@ -205,9 +198,7 @@ classes:
multivalued: true
inlined: true
description: 'Editors of the exhibition catalog.
MIGRATED from editor (string list) to structured Editor class.
'
examples:
- value:
@ -285,20 +276,12 @@ classes:
multivalued: true
inlined_as_list: true
description: 'Table of contents or index structure for the catalog.
MIGRATED from table_of_content slot per slot_fixes.yaml (Rule 53/56, 2026-01-16).
Uses Index class for structured representation of:
- Table of contents with hierarchical entries
- Subject indexes
- Name indexes
- Illustration lists
'
examples:
- value:

171
schemas/20251121/linkml/modules/classes/HeritageSocietyType.yaml
View file

@ -2,51 +2,26 @@ id: https://nde.nl/ontology/hc/HeritageSocietyType
name: HeritageSocietyType
title: Heritage Society Type
description: 'Specialized custodian type for voluntary heritage societies, historical associations, and
collecting societies that preserve and promote local, specialized, or thematic heritage.
Heritage societies are membership-based organizations (often volunteer-driven) that maintain
collections, conduct research, publish findings, and engage communities in heritage preservation.
They differ from professional museums (M), archives (A), or research centers (R) by their
community-based, volunteer nature and focus on specialized collecting or local heritage.
Key Characteristics:
- Membership-based organizations (dues-paying members)
- Volunteer-driven or minimal professional staff
- Focus on specialized collecting (numismatics, philately, genealogy, local history)
- Community engagement and public education mission
- Publication activities (journals, newsletters, monographs)
- Often maintain small collections or archives
Wikidata Coverage:
- Base concepts: Q10294527 (heemkundekring - Dutch heritage society)
- Historical societies: Q5773836 (Historical Association), local history societies
- Collecting societies: Q55174682 (numismatic society), Q3446009 (philatelic society)
- Genealogical societies: Q2077377 (genealogical society)
- Archaeological societies: Q15755503 (archaeological society)
- Learned societies: Q371160 (learned society) - when focused on heritage
This class represents ''S'' (Collecting Society) in the GLAMORCUBEPSXHFN taxonomy.
'
from_schema: https://nde.nl/ontology/hc/HeritageSocietyType
see_also:
@ -231,190 +206,93 @@ classes:
attributes:
society_focus:
description: 'Primary focus area or specialty of the heritage society.
Local Heritage (Heemkundekringen):
- Local history: Village/town/neighborhood history
- Regional heritage: Provincial or regional cultural traditions
- Community archives: Preserving local records and photographs
- Dialect preservation: Local language and oral traditions
- Built heritage: Historic buildings, monuments, streetscapes
Specialized Collecting:
- Numismatics: Coins, medals, banknotes, tokens
- Philately: Stamps, postal history, covers, cancellations
- Ephemera: Trade cards, postcards, advertising, labels
- Transportation: Railway history, automotive, aviation, maritime
- Military history: Uniforms, medals, equipment, battles
- Industrial heritage: Tools, machinery, company records
Genealogical Research:
- Family history: Tracing lineages, family trees
- Vital records: Birth, marriage, death records
- Immigration research: Passenger lists, naturalization records
- Ethnic heritage: Preserving immigrant community histories
Archaeological/Antiquarian:
- Archaeological surveys: Local excavations, finds recording
- Antiquarian studies: Historical objects, curiosities
- Architectural history: Building documentation, conservation advocacy
Thematic Heritage:
- Agricultural heritage: Farming tools, rural life
- Maritime heritage: Shipwrecks, fishing, coastal communities
- Religious heritage: Church history, religious artifacts
- Literary heritage: Authors, manuscripts, book collecting
Examples:
- "Local history of Leiden and surroundings (heemkundekring)"
- "Dutch numismatics: coins and medals from 1500-present"
- "Family history and genealogy of New England families"
- "Railway heritage of the Netherlands: rolling stock, stations, memorabilia"
This field defines the heritage domain the society preserves and studies.
'
range: string
slot_uri: schema:knowsAbout
membership_size:
description: 'Number of members and membership structure.
Size Categories:
- Small (1-50 members): Local heemkundekringen, village history societies
- Medium (51-500 members): Regional societies, specialized collecting clubs
- Large (501-5,000 members): National genealogical societies, major numismatic clubs
- Very large (5,000+ members): International societies, major learned societies
Membership Types:
- Individual members: Regular dues-paying members
- Family memberships: Household memberships
- Institutional members: Libraries, museums, universities
- Honorary members: Recognized experts or long-serving members
- Student members: Reduced-rate memberships for students
- Life members: One-time payment for lifetime membership
Membership Benefits:
- Publications: Journals, newsletters, yearbooks
- Events: Lectures, field trips, annual meetings
- Library access: Society library or reading room
- Research support: Access to collections, databases
- Networking: Connecting with fellow enthusiasts
Membership Demographics:
- Age distribution (often skews older for heritage societies)
- Geographic distribution (local, regional, national, international)
- Expertise levels (amateur enthusiasts to professional scholars)
Growth Trends:
- Declining membership (common in many heritage societies)
- Aging membership (challenges for succession)
- Digital membership (remote members via online access)
Examples:
- "120 members (mostly local residents of Leiden and environs)"
- "450 members across Netherlands and Belgium (Dutch-speaking numismatists)"
- "8,000 members worldwide (largest genealogical society in US)"
- "75 members (declining from peak of 150 in 1980s)"
This field captures the community scale and member engagement.
'
range: string
slot_uri: schema:numberOfEmployees
is_or_was_published_at:
description: 'Publications produced by the society, modeled as structured publication events.
MIGRATED from publication_activity (string list) per Rule 53/56 (2026-01-18).
Each PublicationEvent captures:
- has_or_had_label: Publication name/description (e.g., "Quarterly journal ''Oud-Leiden''")
- temporal_extent: When the publication started/continues (using CIDOC-CRM TimeSpan)
Publication Types Covered:
- Periodicals: Journals, newsletters, yearbooks
- Monographs: Research publications, exhibition catalogs, collection catalogs
- Digital: Websites, blogs, podcasts, social media
Examples:
- "Quarterly journal ''Oud-Leiden'' (founded 1925) with local history articles"
- "Annual numismatic journal + monthly newsletter; all digitized back to 1950"
- "Bi-monthly newsletter; occasional monographs on local history"
'
range: PublicationEvent
multivalued: true
@ -462,18 +340,11 @@ classes:
equals_expression: '["hc:HeritageSocietyType"]'
has_or_had_program:
description: 'Volunteer programs and roles within the heritage society.
Migrated from volunteer_program (inline attribute) per Rule 53.
Covers governance volunteers (board, officers), collections volunteers
(curators, catalogers), research volunteers (archivists, historians),
education and outreach (lecturers, tour guides), and operations
(membership coordinators, event organizers, fundraisers).
'
range: Program
inlined: true
@ -485,39 +356,21 @@ classes:
description: All-volunteer organization managing collections and events
has_or_had_activity:
description: 'Community outreach, public programs, and engagement activities.
MIGRATED from community_engagement (string list) per Rule 53 (2026-01-19).
Each Activity instance captures structured engagement data using:
- has_activity_name: Activity name (e.g., "Monthly Lecture Series")
- has_or_had_activity_type: CommunityEngagementActivityType
- has_timespan: When activities occur (using TimeSpan)
- has_activity_description: Detailed description
Activity Types Covered:
- Membership meetings: Monthly, quarterly, annual gatherings
- Lecture series: Guest speakers on heritage topics
- Field trips: Site visits, museum tours, heritage walks
- Workshops: Genealogy, conservation, identification skills
- Public events: Open houses, exhibitions, school programs
- Digital engagement: Websites, social media, virtual meetings
- Advocacy: Historic preservation, policy engagement
- Partnerships: Collaborations with government, museums, universities
'
range: string
multivalued: true
@ -530,9 +383,7 @@ classes:
has_or_had_activity_type:
- CommunityEngagementActivityType
has_activity_description: 'Monthly evening lectures on local history topics, featuring
guest speakers from academia, museums, and member experts.
'
temporal_extent:
begin_of_the_begin: '2024-09-01'
@ -543,9 +394,7 @@ classes:
has_or_had_activity_type:
- CommunityEngagementActivityType
has_activity_description: 'Annual guided heritage walk through historic Leiden neighborhoods.
Open to public, attracts 50-100 participants.
'
temporal_extent:
begin_of_the_begin: '2025-05-15'
@ -554,42 +403,22 @@ classes:
description: Heritage society with lecture series and annual heritage walk
has_or_had_scope:
description: 'Scope and nature of the society''s collecting activities and holdings.
MIGRATED from collecting_scope (string list) per Rule 53 (2026-01-19).
Uses CollectionScope class to capture structured scope information:
- scope_description: Overall description of collecting scope
- scope_type: Type discriminator ("collection_scope", "archival_scope", etc.)
- subject_coverage: Subject areas (numismatics, local history, etc.)
- temporal_coverage_description: Time period covered
- spatial_coverage: Geographic scope
Collection Types:
- Objects: Physical artifacts (coins, stamps, ephemera, memorabilia)
- Archival materials: Documents, photographs, manuscripts
- Library materials: Books, journals, reference works
Collecting Policies:
- Focused collecting: Narrowly defined scope (e.g., Dutch maritime coins 1600-1800)
- Broad collecting: Wide scope (e.g., all aspects of town history)
- Passive collecting: Accepting donations, no active acquisition
- Active collecting: Targeted purchases, exchanges
'
range: CollectionScope
multivalued: true

4
schemas/20251121/linkml/modules/classes/IntangibleHeritageGroupType.yaml
View file

@ -2,12 +2,8 @@ id: https://nde.nl/ontology/hc/class/intangible-heritage-group-type
name: intangible_heritage_group_type
title: IntangibleHeritageGroupType
description: 'Specialized CustodianType for organizations preserving intangible cultural heritage
(oral traditions, performing arts, social practices, rituals, traditional craftsmanship).
Coverage: Corresponds to ''I'' (INTANGIBLE_HERITAGE_GROUP) in GLAMORCUBESFIXPHDNT taxonomy.
'
imports:
- linkml:types

9
schemas/20251121/linkml/modules/classes/MuseumType.yaml
View file

@ -121,9 +121,7 @@ classes:
description: Wikidata identifier (Q-number) for this Museum type concept
has_or_had_hypernym:
description: 'MIGRATED from broader_type (Rule 53).
For museum type subtypes, links to parent type in hierarchy.
'
range: MuseumType
conservation_lab:
@ -133,29 +131,22 @@ classes:
equals_expression: '["hc:MuseumType"]'
has_or_had_facility:
description: 'Public facilities and amenities available at the museum.
Migrated from visitor_facility per Rule 53.
'
range: string
inlined: true
multivalued: true
complies_or_complied_with:
description: 'Standards used for object cataloging and collection management.
MIGRATED from cataloging_standard per Rule 53/56 (2026-01-17).
Common museum standards: LIDO, SPECTRUM, CIDOC-CRM.
'
range: CatalogingStandard
inlined: true
multivalued: true
has_or_had_category:
description: 'MIGRATED from collection_focus per slot_fixes.yaml (Rule 53, 2026-01-19).
Subject areas and thematic focus of the museum''s collections using Category class.
'
range: Category
inlined: true

5
schemas/20251121/linkml/modules/classes/OrganizationalStructure.yaml
View file

@ -70,11 +70,8 @@ classes:
has_or_had_type:
range: uriorcurie
description: 'Type classification of this organizational unit.
Uses OrganizationalUnitType class hierarchy.
Replaces unit_type slot per slot_fixes.yaml migration.
'
examples:
- value: DEPARTMENT
@ -129,9 +126,7 @@ classes:
- value: https://nationalarchives.nl/services/reading-room
temporal_extent:
description: 'Validity period using CIDOC-CRM TimeSpan.
MIGRATED from valid_from + valid_to per slot_fixes.yaml (Rule 53).
'
range: TimeSpan
inlined: true

21
schemas/20251121/linkml/modules/classes/Storage.yaml
View file

@ -106,9 +106,7 @@ classes:
required: true
identifier: true
description: 'Unique identifier for this storage facility.
MIGRATED from storage_id per slot_fixes.yaml (Rule 53).
'
examples:
- value: https://nde.nl/ontology/hc/storage/rijksmuseum-depot-amersfoort
@ -118,11 +116,8 @@ classes:
required: true
inlined: true
description: 'Human-readable name for this storage facility.
MIGRATED from storage_name per slot_fixes.yaml (Rule 53).
Uses Label class with text and language support.
'
examples:
- value:
@ -138,9 +133,7 @@ classes:
range: uriorcurie
required: true
description: 'The type classification of this storage facility.
Uses StorageType class hierarchy (ARCHIVE_DEPOT, COLD_STORAGE, ART_STORAGE, etc.).
'
examples:
- value: ARCHIVE_DEPOT
@ -151,20 +144,14 @@ classes:
description: Climate-controlled art storage
has_or_had_description:
description: 'Description of this storage facility.
MIGRATED from storage_description per slot_fixes.yaml (Rule 53).
Uses Description class with text and language support.
'
multivalued: true
examples:
- value: 'description_text: ''Climate-controlled archive depot housing overflow document collections. Equipped with mobile shelving system (Compactus). Staff access only. Fire suppression: inert gas system.''
description_type: storage
language: en
'
description: Storage description using Description class
is_or_was_stored_at:
@ -172,11 +159,8 @@ classes:
required: false
inlined: true
description: 'Physical or digital location where this storage facility is situated.
MIGRATED from storage_location per slot_fixes.yaml (Rule 53).
Uses StorageLocation class for unified location modeling.
'
examples:
- value:
@ -261,11 +245,8 @@ classes:
has_or_had_policy:
range: string
description: 'Environmental and safety policy governing this storage facility.
MIGRATED from condition_policy per slot_fixes.yaml (Rule 53).
Uses ConditionPolicy/StorageConditionPolicy class for policy specification.
'
examples:
- value:
@ -287,9 +268,7 @@ classes:
- value: Facilities and Security Team
temporal_extent:
description: 'Validity period using CIDOC-CRM TimeSpan.
MIGRATED from valid_from + valid_to per slot_fixes.yaml (Rule 53).
'
range: TimeSpan
inlined: true