- Updated slot names to improve semantic clarity:
- `has_type` changed to `categorized_as`
- `has_location` changed to `located_at`
- `coordinates` changed to `has_coordinates`
- `country` changed to `in_country`
- `like_count` changed to `has_quantity`
- Adjusted descriptions and annotations for slots to enhance understanding and alignment with ontology standards.
- Modified imports in `WomensArchives.yaml` and `WomensArchivesRecordSetTypes.yaml` to reflect new slot names.
- Enhanced multilingual support in `has_record_set` slot definition with additional translations and structured aliases.
- General cleanup and standardization of slot definitions across various classes including `Wikidata`, `Youtube`, and `WorkExperience`.
- Introduced `prepared_by` slot to identify the individual or organization responsible for preparing an item, specimen, or document, with ontology alignment to CIDOC-CRM, PROV-O, Schema.org, and FOAF.
- Added `prepared_on` slot to capture the date when a sample or document was prepared, including mappings to DC Terms and Schema.org.
- Created `preserve` slot to define actions related to maintaining and protecting entities from harm or decay, with references to CIDOC-CRM and other ontologies.
- Implemented `provide` slot to document the act of supplying resources or services, with related mappings to Schema.org and PROV-O.
- Established `provide_to` slot to identify recipients of services or resources, with ontology alignment to Schema.org and CIDOC-CRM.
- Added `receive` slot to capture the act of accepting delivery of objects or services.
- Introduced `recommend` slot for suggesting courses of action or services.
- Created `started_on` slot to record the initiation date of activities or processes, with mappings to PROV and Schema.org.
- Introduced `refer_to` slot to link identifiers to entities, with ontology alignment to CIDOC-CRM and DCTerms.
- Added `remove` slot for recording objects removed during deaccessioning, aligned with CIDOC-CRM properties.
- Created `reported_on` slot to capture URIs of reports documenting entities, with mappings to CIDOC-CRM and Schema.org.
- Implemented `signed_by` slot to identify individuals who signed documents, referencing RiC-O and Schema.org.
- Established `specified_as` slot to indicate the precision level of place references, with broad mappings to CRM and DQV.
- Introduced 'recur_at' to specify time intervals, frequencies, or spatial locations of repeated occurrences, with ontology alignments to Schema.org and DCTerms.
- Added 'registered_at' to denote the timestamp of record registration, aligning with Schema.org and DCTerms properties.
- Created 'return' to signify the action of sending items back to their origin, with mappings to Schema.org and CIDOC-CRM.
- Defined 'track' to indicate the maintenance of object identity across frames or time intervals, with relevant mappings to SOSA.
- Established 'transmission' to describe the process of passing knowledge or skills, aligning with CIDOC-CRM and Schema.org.
- Implemented 'use_material' to specify substances or materials used in creating or modifying objects, with close mappings to CIDOC-CRM and Schema.org.
- Created `has_numerator` to represent the numerator in ratios, rates, or percentages, including ontology alignment with Schema.org and DQV.
- Introduced `has_reference_system` for specifying the Coordinate Reference System (CRS) for spatial datasets, with mappings to RiC-O and DCTerms.
- Added `has_selector` to define CSS selectors or XPath patterns for webpage elements, aligning with OA and Schema.org properties.
- Defined `in_country` to relate entities to their sovereign state or territory, with close mappings to Schema.org and GeoNames.
- Established `integrate` to describe organizational placement and integration of heritage entities, capturing ownership, reporting, and governance aspects.
- Created `supported_by` to identify entities providing assistance or funding, with mappings to Schema.org and DCTerms.
- Introduced `used_for` to relate objects or resources to their intended purpose or function, aligning with CIDOC-CRM properties.
- Deleted the `rights_statement_url` slot definition as it is no longer needed.
- Added multiple new slots including `has_legal_basis`, `has_statement`, `impose`, `pose_condition`, and `reviewed_through` with detailed descriptions and ontology alignments.
- Updated existing slots to improve clarity and consistency, including renaming `close_mappings` to `related_mappings` in several definitions.
- Enhanced the `require` slot with additional aliases for better usability.
- Improved documentation and comments across all slot definitions to clarify their purpose and usage.
- Created `approximate.yaml` to define the slot for estimated values.
- Introduced `has_basionym.yaml` for the original validly published name in taxonomy.
- Added `has_position.yaml` to specify roles or titles within organizations.
- Defined `hold.yaml` to indicate items or collections held by heritage institutions.
- Created `identified_as.yaml` for external classifications assigned to entities.
- Introduced `initiate_on.yaml` to denote the start date or condition of processes.
- Added `is_location_of.yaml` to specify geographic positions of entities or events.
- Defined `ranked_through.yaml` to describe mechanisms for determining relative positions.
- Created `warrant.yaml` to provide justifiable reasons for actions or beliefs.
- Introduced `has_extent` to specify the physical or digital size of materials.
- Added `has_fonds` to define the aggregated body of records from a specific creator.
- Created `has_period` for named periods within coverage.
- Defined `has_place` to associate a geographic location with an entity.
- Implemented `has_series` for archival series within fonds.
- Added `has_index_number` to specify index numbers associated with records.
- Introduced `measured_through` to specify instruments or methods used for measurements.
- Created `has_organizer` to identify agents or organizations that organized events.
- Defined `has_origin` to specify the origin or source of an entity.
- Implemented `has_publication_date` for the date when an entity was published.
- Added `has_michelin_star` to indicate whether a restaurant has Michelin stars.
- Created `has_investment` to specify investment amounts associated with entities.
- Introduced `require` to specify necessary conditions for entities.
- Defined `has_restriction` for restrictions or limitations on entities.
- Created 'updated_at.yaml' to record the last modified date and time of entities, including multilingual descriptions and structured aliases.
- Created 'written_in.yaml' to specify the language in which content is composed, covering both natural and programming languages, with detailed comments and close ontology mappings.
- Updated `manifest.json` with new generation timestamp.
- Revised descriptions for `has_administration`, `has_affiliation`, `has_alignment`, and `has_fee` slots to enhance clarity and precision.
- Removed obsolete slots: `has_administration_description`, `has_administration_name`, `has_admission_fee`, `has_affected_territory`, and `has_alternative_observed_name`.
- Introduced new slot `has_alias` to capture alternative names for entities.
- Added `amended_with` slot to document amendment history with detailed descriptions.
- Ensured all slots have multilingual support for better accessibility.
- Removed obsolete slots: `has_or_had_custodian_observation`, `provider`, and `specificity_annotation`.
- Updated `has_or_had_score` slot to use `SpecificityScore` class and modified its description and examples.
- Added new slots: `end_seconds`, `end_time`, `has_archive_path`, `has_or_had_custodian_name`, `protocol_name`, and `protocol_version`.
- Introduced a script `check_annotation_types.py` to validate the presence and structure of `custodian_types` in YAML files.
- Added a script `update_specificity.py` to automate updates related to `SpecificityAnnotation` to `SpecificityScore`.
- Updated WorldCatIdentifier.yaml to remove unnecessary description and ensure consistent formatting.
- Enhanced WorldHeritageSite.yaml by breaking long description into multiple lines for better readability and removed unused attributes.
- Simplified WritingSystem.yaml by removing redundant attributes and ensuring consistent formatting.
- Cleaned up XPathScore.yaml by removing unnecessary attributes and ensuring consistent formatting.
- Improved YoutubeChannel.yaml by breaking long description into multiple lines for better readability.
- Enhanced YoutubeEnrichment.yaml by breaking long description into multiple lines for better readability.
- Updated YoutubeVideo.yaml to break long description into multiple lines and removed legacy field name.
- Refined has_or_had_affiliation.yaml by removing unnecessary comments and ensuring clarity.
- Cleaned up is_or_was_retrieved_at.yaml by removing unnecessary comments and ensuring clarity.
- Added rules for generic slots and avoiding rough edits in schema files to maintain structural integrity.
- Introduced changes_or_changed_through.yaml to define a new slot for linking entities to change events.
- Removed unnecessary line breaks and whitespace in descriptions across multiple classes including Taxon, TaxonomicAuthority, TechnicalFeature, TradeRegister, TransferEvent, UNESCODomain, UnspecifiedType, UserCommunity, Version, VideoAnnotationTypes, VideoFrame, VideoTextContent, WebArchive, WebClaimsBlock, WebLink, WebPortal, and WordCount.
- Updated descriptions to enhance readability and maintain a uniform style.
- Migrated attributes and slots as per the latest schema rules, ensuring alignment with the defined standards.
- Improved documentation for better understanding of class purposes and usage scenarios.
- Added `id`, `name`, `title`, and `description` fields to multiple LinkML class YAML files.
- Standardized prefixes across all class definitions.
- Introduced a new script `fix_linkml_metadata.py` to automate the addition of metadata to class files.
- Updated existing class files to ensure compliance with the new metadata structure.
- Added `fix_dual_class_link.py` to remove dual class link references from specified YAML files.
- Created `fix_specific_ghosts.py` to apply specific replacements in YAML files based on defined mappings.
- Introduced `migrate_staff_count.py` to migrate staff count references to a new structure in specified YAML files.
- Developed `migrate_type_slots.py` to replace type-related slots with new identifiers across YAML files.
- Implemented `scan_ghost_references.py` to identify and report ghost references to archived slots and classes in YAML files.
- Added `verify_ontology_terms.py` to verify the presence of ontology terms in specified ontology files against schema definitions.
- Updated manifest.json with new generated timestamp.
- Added close mappings to APIRequest and Administration classes.
- Renamed slots in AccessPolicy to has_or_had_embargo_end_date and has_or_had_embargo_reason.
- Changed class_uri for Accumulation to rico:AccumulationRelation and updated description.
- Added exact mappings to Altitude, AppellationType, and ArchitecturalStyle classes.
- Removed deprecated slots from CollectionManagementSystem and updated has_or_had_type.
- Added new slots for has_or_had_embargo_end_date and has_or_had_embargo_reason.
- Updated slot definitions for has_or_had_assessment, has_or_had_sequence_index, and others with new URIs and mappings.
- Removed unused slots end_seconds and end_time.
- Added new slot definitions for has_or_had_exhibition_type, has_or_had_extent_text, and is_or_was_documented_by.
- Updated VideoPost.yaml to include new slots and remove deprecated ones, enhancing video-specific properties.
- Removed extraction_confidence from WebObservation.yaml, streamlining the schema.
- Deleted obsolete slot files: characteristics.yaml, class_definition.yaml, confidence.yaml, confidence_method.yaml, confidence_score.yaml, confidence_value.yaml, count.yaml, and hosts_branch.yaml.
- Introduced ghost_slots.txt to track unused slots.
- Archived previous versions of characteristics, class_definition, confidence, confidence_method, confidence_score, confidence_value, count, and hosts_branch slots for historical reference.
- Added new slots: has_or_had_citation, has_or_had_city_code, and is_or_was_location_of with appropriate descriptions and mappings.
- Deleted obsolete chapter slots: chapter_description, chapter_end_seconds, chapter_end_time, chapter_id, chapter_index, chapter_source, chapter_start_seconds, chapter_start_time, humidity_tolerance, parent_chapter_id.
- Archived previous versions of deleted slots for reference.
- Introduced new generic slots: end_seconds, end_time, has_or_had_parent, has_or_had_sequence_index to streamline schema and improve consistency.
- Updated descriptions and mappings for new slots to ensure clarity and maintain functionality.
- Updated StorageConditionPolicy.yaml to include additional slots related to storage conditions, such as particulate_max and pest_management_required, enhancing the policy's comprehensiveness.
- Removed the obsolete catalogues_or_cataloged.yaml file to streamline the schema.
- Introduced a new archived version of catalogues_or_cataloged in catalogues_or_cataloged_archived_20260128.yaml, preserving the original structure and annotations for future reference.
- Updated `has_or_had_url` slot to allow a broader range of values by changing its range from `uriorcurie` to `Any`.
- Removed obsolete slots: `house_number`, `html_file`, `html_snapshot_path`, and `http_status_code`.
- Introduced new classes: `CeasingEvent`, `FileLocation`, `FilePath`, `HTMLFile`, `HTTPStatusCode`, `HouseNumber`, `MaximumHumidity`, `MinimumHumidity`, `TargetHumidity`, and `WKT` to better represent various concepts.
- Migrated existing slots to new structures, ensuring alignment with RiC-O naming conventions.
- Added new slots: `ceases_or_ceased_through`, `has_or_had_file_location`, `has_or_had_file_path`, `has_or_had_http_status`, and `is_or_was_observed_by` to capture additional metadata.
- Enhanced descriptions and annotations for clarity and context.
- Added new slot `is_or_was_used_in` to `DataServiceEndpointType` for tracking usage in the heritage sector.
- Replaced `heritage_society_subtype` with `has_or_had_hyponym` in `HeritageSocietyType`.
- Updated `HistoricBuilding` to use `has_or_had_status` instead of `heritage_status`, linking to the new `HeritageStatus` class.
- Removed deprecated slots: `heritage_relevant_count`, `heritage_relevant_percentage`, `heritage_sector_usage`, `heritage_society_subtype`, and `heritage_status`.
- Introduced new classes `Connection`, `HeritageSector`, and `HeritageStatus` to better structure heritage-related data.
- Migrated relevant descriptions and annotations to align with new schema standards.
- Updated slot definitions to improve clarity and consistency across the schema.
- Introduced new classes: Heritage, HeritagePractice, HeritageRelevanceAssessment, HeritageRelevanceScore, HolySiteType, Mandate.
- Added slots for heritage-related attributes including has_or_had_confidence_measure, has_or_had_related_heritage_form, heritage_education, heritage_employer, heritage_mandate, heritage_practice, and more.
- Migrated existing attributes and ensured compliance with RiC-O naming conventions.
- Enhanced documentation and descriptions for clarity and usability.
- Archived previous versions of slots and classes to maintain schema integrity.
- Introduced GeospatialLocation class for specific geospatial locations.
- Added HandsOnFacility class representing facilities for hands-on experiences.
- Created Hyponym class for narrower terms or instances.
- Added ImagingEquipment class for imaging-related equipment.
- Introduced LoadingDock class for loading dock facilities.
- Created LocalCollection class for locally held collections.
- Added Locker class for storage lockers available to visitors/staff.
- Introduced MichelinStarRating class for Michelin star ratings.
- Created MicrofilmReader class for equipment used to read microfilms.
- Added OperationalArchive class for archives containing operational records.
- Introduced OperationalUnit class for operational units within organizations.
- Added has_or_had_archive slot for associating archives with entities.
- Created has_or_had_rating slot for ratings assigned to entities.
- Introduced has_or_had_section slot for sections or units within organizations.
- Added has_geospatial_location slot linking nominal places to precise geospatial coordinates.
- Renamed `has_or_had_auxiliary_entities` to `is_or_was_associated_with` in DigitalPlatform.yaml to align with naming conventions.
- Updated examples in DigitalPlatform.yaml to reflect new slot names and types.
- Migrated `has_av_equipment` to `has_or_had_equipment` in EducationCenter.yaml, including detailed descriptions and examples.
- Consolidated archival references by migrating `archival_reference` to `has_or_had_identifier` in InformationCarrier.yaml.
- Removed deprecated slots: `has_authority_file_name`, `has_authority_file_url`, `has_auxiliary_place`, `has_auxiliary_place_type`, `has_auxiliary_platform`, `has_auxiliary_platform_type`, and `has_av_equipment`, archiving their definitions.
- Updated slot fixes to reflect the migration of various slots to more generic or appropriate counterparts, ensuring all changes are documented with processing notes.
- Introduced EADIdentifier, EBook, EcclesiasticalProvince, Edition, Editor, Education, EmailAddress, and Size classes to enhance archival description capabilities.
- Added slots for digital presence types, digital surrogates, digitization status, and dimensions to support comprehensive metadata management.
- Migrated existing slots such as ead_id, edition_number, and dimension to new structured formats.
- Established relationships between works and their editions, sizes, and editors to improve data interconnectivity.
- Enhanced ontology alignment with Schema.org and BIBFRAME standards for better interoperability.
- Migrated catering_type to CateringType with subclasses for better classification.
- Updated certainty_level to has_or_had_level for improved metadata consistency.
- Addressed cessation_observed_in by confirming existing temporal data structure.
- Created NetAsset class and updated financial statements for richer financial modeling.
- Completed migrations for default_access_policy, default_audio_language, and default_language to structured classes.
- Migrated default_position to structured Alignment class for better representation.
- Updated defined_by_standard to broaden range for identifier standards.
- Migrated definition to structured Resolution class for video resolution modeling.
- Completed migrations for degree_name, deliverable, and departement_code to structured classes.
- Migrated deployment_date to structured DeploymentEvent with temporal extent.
- Migrated derived_from_entity and derived_from_observation to new reference structures.
- Completed description and description_text migrations to enhance content modeling.
- Migrated detection_count, detection_level, and detection_threshold to structured slots with classes.
- Migrated device-related slots to structured classes for better identification and classification.
- Added new slots and classes for historic building and web address modeling.
- Introduced PriceRange class to categorize price levels for hospitality services, including structured metadata for various price categories.
- Added Publication class to represent publication events, capturing details like publisher, publication place, and edition.
- Created TaxDeductibilityType as an abstract class for tax deductibility status, promoting previous enum values to a class hierarchy for richer metadata.
- Implemented TaxDeductibilityTypes with concrete subclasses detailing various tax deductibility statuses.
- Archived previous DeductibilityStatusEnum and related slots, transitioning to a more structured approach for tax deductibility classification.
- Updated multiple slot definitions to align with new class structures and naming conventions, including has_or_had_measurement and has_or_had_price.
- Enhanced documentation and examples across new and existing slots for clarity and compliance with naming conventions.
- Introduced CreationEvent class to represent the creation of objects, including temporal extent, creator, and place of creation.
- Added DatePrecision class to indicate the precision level of date values, supporting various formats from day to century.
- Implemented IdentificationEvent class for taxonomic identification, capturing identification date, method, and confidence level.
- Created Image class for visual content representation, including URL and metadata for images used in collections.
- Archived previous slots related to card images and titles, replacing them with structured slots for better data representation.
- Enhanced slots for decommission dates, degree of certainty, and identification events to improve temporal data handling.
- Added `range: string` to `connections_by_heritage_type` slot for better data representation.
- Removed obsolete `data_source_whatsapp`, `data_tier`, `date_retrieved`, and `de` slots from the schema.
- Updated `derived_from_observation` slot to support multiple values and changed range to `uriorcurie`.
- Introduced new `DataSource` class to represent various data sources with detailed descriptions and examples.
- Created `DataTierLevel` class to classify data quality tiers with standard codes and descriptions.
- Archived removed slots and updated the manifest to reflect these changes.
- Added new `was_retrieved_at` slot to track data retrieval timestamps, following RiC-O conventions.
- Introduced MainPart class to represent principal portions with quantified values, including attributes for part type and currency code.
- Added OutputData class to specify output characteristics from devices/services, including format, description, and destination URL.
- Created canonical_value, capacity, capacity_type, and capacity_value slots for enhanced data representation.
- Archived and migrated various slots related to data sensitivity, dataset descriptions, and titles to align with new structures.
- Implemented has_or_had_caption and has_or_had_main_part slots to support media accessibility and primary portion representation.
- Enhanced data license policy slot to define custodian data licensing and openness policies.
- Introduced abstract class ConflictType to define a taxonomy for various conflict types affecting heritage institutions.
- Added concrete subclasses in ConflictTypes.yaml, detailing specific conflict types such as ArmedConflict, NaturalDisaster, CivilUnrest, Terrorism, Looting, Neglect, Occupation, and Sanctions.
- Implemented Permission and PermissionType schemas to represent authorization requirements for accessing heritage materials, including subclasses like BishopsPermission and InstitutionalAffiliation.
- Created SocialNetworkMember class for representing members in social/professional networks, facilitating heritage sector network analysis.
- Established slots for canonical access rules, conflict status, and connection metadata, enhancing the data model for heritage custodians.
- Developed ConnectionDegree and ConnectionDegreeType classes to represent degrees of connection in social networks, with subclasses for first, second, and third-plus degrees.
- Added slots for birth dates in EDTF and ISO formats, improving the representation of heritage custodian entities.
- Introduced LastName class to represent Dutch surnames with sorting behavior based on base forms.
- Added address_formatted, amount, area_value, and base_surname slots for heritage custodian entities.
- Created benefits_provided, compliance_status, and component_type slots to enhance entity descriptions.
- Implemented condition, contains_or_contained, final_of_the_final, has_or_had_base, and has_or_had_component slots for better relationship modeling.
- Established initial_of_the_initial and poses_or_posed_condition slots for capturing temporal states and access conditions.
- Removed compliance_status slot and replaced it with has_or_had_status.
- Updated has_or_had_status to use ComplianceStatus for structured representation.
- Adjusted examples to reflect new structure for compliance status.
- Updated documentation to indicate migration and provide details on the ComplianceStatus class.
- Removed community_significance slot and migrated its functionality to has_or_had_significance, utilizing the Significance class for structured representation.
- Introduced has_or_had_significance slot with detailed examples and descriptions.
- Archived community_significance slot and its YAML file.
- Removed frame_sample_rate slot, migrating its functionality to the analyzes_or_analyzed slot, now supporting the VideoFrame class for frame analysis.
- Created VideoFrame class to encapsulate frame analysis parameters, including sample rate and total frames processed.
- Updated relevant schemas and examples to reflect these changes, ensuring compliance with migration rules.
- Regenerated manifest to include new structures and updated counts.
- Introduced `founding_date`, `founding_date_diocese`, and `fr` slots for capturing founding dates and French language text.
- Created `collects_or_collected`, `has_or_had_objective`, `has_or_had_percentage`, `has_or_had_place`, `has_or_had_reply`, `has_or_had_web_page`, `is_or_was_acquired_by`, `is_or_was_appreciated`, `is_or_was_founded_through`, `is_or_was_part_of`, `is_or_was_part_of_total`, `start_of_the_start`, `takes_or_took_comission`, and `was_fetched_at` slots to enhance data modeling capabilities.
- Each slot includes detailed descriptions, examples, and ontology alignments to ensure clarity and usability.
- Migration notes added for slots transitioned from previous definitions to maintain historical context and facilitate understanding of changes.
- Introduced new slots for administrative context, CMS categories, detected CMS, product version, co-funding requirements, co-organizers, collection access, collection dates, characteristics, class definitions, Dutch context, example locations, names, notes, and Wikidata IDs.
- Enhanced existing slots such as has_or_had_organizer and offers_or_offered_access to align with RiC-O naming conventions and improve temporal semantics.
- Migrated and restructured descriptions for clarity and consistency across various slots, ensuring alignment with Schema.org and other ontological standards.
- Implemented multivalued and inlined options for several slots to accommodate complex data structures.
- Updated annotations and examples to reflect the latest usage scenarios and best practices in the heritage sector.
- Create Classroom.yaml (subclass of Facility)
- Create RoomUnit.yaml (subclass of Unit for room counting)
- Create RoomUnitTypeEnum.yaml with room type values
- Update EducationCenter.yaml to use has_or_had_facility with Classroom
- Archive classroom_count.yaml slot
Rule 53 compliance: Replaces simple integer count with structured facility model.
