glam/schemas/20251121/linkml/modules/classes/SearchAPI.yaml
kempersc fcd1c21c63 Add aliases and enhance slot definitions across various modules
- Added new aliases for existing slots to improve clarity and usability, including:
  - has_deadline: has_embargo_end_date
  - has_extent: has_extent_text
  - has_fonds: has_fond
  - has_laboratory: conservation_lab
  - has_language: has_iso_code639_1, has_iso_code639_3
  - has_legal_basis: legal_basis
  - has_light_exposure: max_light_lux
  - has_measurement_unit: has_unit
  - has_note: has_custodian_observation
  - has_occupation: occupation
  - has_operating_hours: has_operating_hours
  - has_position: position
  - has_quantity: has_artwork_count, link_count
  - has_roadmap: review_date
  - has_skill: skill
  - has_speaker: speaker_label
  - has_specification: specification_url
  - has_statement: rights_statement_url, rights_statement
  - has_type: custodian_only
  - has_user_category: serves_visitors_only
  - hold_record_set: record_count
  - identified_by: has_index_number
  - in_period: has_period
  - in_place: has_place
  - in_series: has_series
  - measure: has_measurement
  - measured_on: measurement_date
  - organized_by: has_organizer
  - originate_from: has_origin
  - part_of: suborganization_of
  - published_on: has_publication_date
  - receive_investment: has_investment
  - related_to: connection_heritage_type
  - require: preservation_requirement
  - safeguarded_by: current_keeper, record_holder_note
  - state: states_or_stated
  - take_comission: takes_or_took_comission
  - take_place_at: takes_or_took_place_at
  - transmit_through: transmits_or_transmitted_through
  - warrant: warrants_or_warranted

- Introduced a new slot definition for evaluated_through to capture evaluation methodologies and review statuses.
2026-02-14 14:41:49 +01:00

73 lines
3.3 KiB
YAML

id: https://nde.nl/ontology/hc/class/SearchAPI
name: search_api
title: SearchAPI Class
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
dcat: http://www.w3.org/ns/dcat#
dcterms: http://purl.org/dc/terms/
schema: http://schema.org/
hydra: http://www.w3.org/ns/hydra/core#
xsd: http://www.w3.org/2001/XMLSchema#
imports:
- linkml:types
- ../enums/HTTPMethodEnum
- ../enums/PaginationMethodEnum
- ../enums/SearchResponseFormatEnum
- ../metadata
- ../slots/has_score
- ../slots/has_format
classes:
SearchAPI:
is_a: DataServiceEndpoint
class_uri: hc:SearchAPI
description: "REST/JSON search API endpoint for heritage collection discovery.\n\
\n**Purpose:**\n\nModels search APIs that provide programmatic access to collection\
\ search\nfunctionality. These APIs enable:\n- Custom search interface development\n\
- Integration with aggregation platforms\n- Automated data discovery\n- Faceted\
\ search and filtering\n\n**Common Patterns:**\n\nHeritage search APIs typically\
\ support:\n- **Full-text search**: Query across all fields\n- **Field-specific\
\ search**: Query specific metadata fields\n- **Faceted search**: Filter by\
\ category, date, type, etc.\n- **Pagination**: Navigate large result sets\n\
- **Sorting**: Order results by relevance, date, etc.\n\n**Example - Nationaal\
\ Archief Search API:**\n\n```yaml\nsearch_api:\n endpoint_name: \"Nationaal\
\ Archief Search API\"\n endpoint_url: \"https://www.nationaalarchief.nl/onderzoeken/api/zoeken\"\
\n protocol: REST\n query_parameters:\n - name: \"q\"\n type: \"string\"\
\n description: \"Full-text search query\"\n - name: \"from\"\n \
\ type: \"integer\"\n description: \"Pagination offset\"\n - name:\
\ \"size\"\n type: \"integer\"\n description: \"Results per page\"\
\n pagination_method: OFFSET_LIMIT\n max_results_per_page: 100\n response_format:\
\ JSON\n supports_facets: true\n facet_fields: [\"type\", \"periode\", \"\
archief\"]\n```\n\n**Response Structure:**\n\nMost heritage search APIs return\
\ JSON with:\n- `total`: Total number of matching records\n- `results`/`items`/`records`:\
\ Array of result objects\n- `facets`: Aggregation counts for filtering\n- `pagination`:\
\ Links or cursors for paging\n\n**See Also:**\n\n- OpenSearch: https://opensearch.org/\n\
- Hydra API vocabulary: https://www.hydra-cg.com/\n"
comments:
- Primary interface for programmatic collection discovery
- Most heritage institutions expose REST/JSON search APIs
- Consider rate limits and pagination for large-scale harvesting
see_also:
- https://opensearch.org/
- https://www.hydra-cg.com/spec/latest/core/
slots:
- has_score
- has_url
- has_format
annotations:
specificity_score: 0.1
specificity_rationale: Generic utility class/slot created during migration
custodian_types: '[''*'']'
SearchQueryParameter:
class_uri: hydra:IriTemplateMapping
description: 'Describes a query parameter supported by a search API.
Documents the parameter name, type, whether it''s required,
and its purpose.
'
slots:
- has_score
- has_name