www-from-model/content/instruments/f92a09a8-1579-4e3a-a205-8459524ca802/_index.md
Stephan Heunis 91720317ca
All checks were successful
Deploy on webserver / Build site and deploy on success (push) Successful in 1m12s
Introduce term page template generalizations
Along the same lines as 478015 which introduced a generalization for the taxonomy list page,
this commit generalizes the term page template, so that we can remove all duplicates for
taxonomy-specific layout templates.

Several new partials are introduced that are now used in a term page heading and info section,
specifically for the date, identifiers, links, licenses, and related terms such as persons or
topics. These same partials are also worked into the existing 'taxonomy-list-vertical-item'
partial to remove further redundant code. As part of these changes, new icons were added. Also
content has to be updated to change 'date_created' to 'date' in order to streamline its handling
in the single generalized template. The associated jinja templates were also updated with this
change.

The term page layout can be customized in the same taxonomy's '_index.md' page front matter as
is done for the taxonomy list page customization. Newly introduced options are all sub-properties
of the new 'term' property under 'params':

- 'person_display': When a list of persons are rendered for a given term, what should those
  people be called? This is a string value that defaults to 'Contributors'.
- 'depiction_type': The type of depiction that should be rendered for the given term page (and
  in 'taxonomy-list-vertical-item'), if such a file exists in the term bundle. This expects a
  string that will be matched against image files in the term bundle, and will default to 'depiction'.
  This option is necessary because the depiction registration workflow saves depiction files with
  names representing their types, e.g. 'portrait', 'logo', etc.
- 'show_relations': In which format should term relations be displayed at the bottom of the term page,
  if at all. The default is to display no relations (explicitly: 'none'). Other options include
  'expandable', which will show list of expandable taxonomy groups, each group containing all terms of
  that taxonomy that relate to the current term; and 'congo', which will render the Congo-theme default
  list of related terms.

Here are two example configurations for the term options:

'content/persons/_index.md':
---
title: Persons
params:
  term:
    depiction_type: portrait # portrait | logo | depiction (default)
    show_relations: expandable # expandable | congo | none (default)
---

'content/publications/_index.md':
---
title: Publications
params:
  term:
    person_display: Authors # defaults to 'Contributors'
---

Finally, new config is added to several taxonomy index pages to perform these customizations for terms:
- persons: should render the 'portrait' depiction type and show expandable relations
- publications: display persons as 'Authors'
- instruments: should render the 'logo' depiction type
2026-05-31 23:56:10 +02:00

2.1 KiB

title persons params
DataLad Concepts
adina-wagner
michael-hanke
michal-szczepanik
orcid:0000-0003-3456-2493
stephan-heunis
venkatesh-hariharapura-shivashankar
graphRootNodePID pid doi date source_code_url documentation_url title description kind author topic license
xyzrins:instruments/f92a09a8-1579-4e3a-a205-8459524ca802 xyzrins:instruments/f92a09a8-1579-4e3a-a205-8459524ca802 null null https://hub.psychoinformatics.de/orinoco/datalad-concepts null DataLad Concepts For many use cases metadata concepts are complex. Producing and consuming such metadata involves sophisticated tooling, which implies a considerable technical threshold for adopting metadata-focused workflows. The schemas in DataLad Concepts aim to lower this threshold with an approach to expressing rich and semantically precise metadata in relatively simple data structures -- data structures that can be reasonably read from files and processed in scripts with loops and conditionals, rather than requiring databases and specific query languages implemented in targeted libraries. All schemas are implemented in LinkML, connecting to a rich ecosystem for data modeling, validation, and transformation. LinkML bridges between the worlds of structured data in plain text files, relational databases and knowledge graphs if and when needed, so metadata workflows can stay as simple as possible. Meta Data Schema
pid given_name family_name
xyzrins:persons/michael-hanke Michael Hanke
pid given_name family_name
xyzrins:persons/stephan-heunis Stephan Heunis
pid given_name family_name
xyzrins:persons/michal-szczepanik Michał Szczepanik
pid given_name family_name
xyzrins:persons/adina-wagner Adina Wagner
pid given_name family_name
orcid:0000-0003-3456-2493 Yaroslav Halchenko
pid given_name family_name
xyzrins:persons/venkatesh-hariharapura-shivashankar Venkatesh Hariharapura Shivashankar
pid label url
spdxlic:MIT MIT License https://spdx.org/licenses/MIT