An open API service indexing awesome lists of open source software.

https://github.com/andybywire/sanity-plugin-taxonomy-manager

Create and manage SKOS compliant taxonomies, thesauri, and classification schemes in Sanity Studio.
https://github.com/andybywire/sanity-plugin-taxonomy-manager

cms headless sanity sanity-io sanity-studio sanitycms taxonomy

Last synced: 5 months ago
JSON representation

Create and manage SKOS compliant taxonomies, thesauri, and classification schemes in Sanity Studio.

Awesome Lists containing this project

README

          

# Sanity Taxonomy Manager

![NPM Version](https://img.shields.io/npm/v/sanity-plugin-taxonomy-manager?style=flat-square)
![License](https://img.shields.io/npm/l/sanity-plugin-taxonomy-manager?style=flat-square)

### Create and manage SKOS compliant taxonomies, thesauri, and classification schemes in Sanity Studio.

![taxonomy manager plugin screenshot](docs/_images/taxonomyManager.png)

## Documentation

For full documentation, visit [sanitytaxonomymanager.com](https://sanitytaxonomymanager.com).

## Features

- Adds two document types to your Sanity schema which are used to generate [SKOS](https://www.w3.org/TR/skos-primer/) compliant concepts and taxonomies: `skosConcept` and `skosConceptScheme`
- Includes reference filter helpers to allow you to easily include a specific taxonomy, or particular branch of a taxonomy in your Sanity documents
- Encourages taxonomy and thesaurus design best practices by enforcing [disjunction between Broader and Related relationships](https://www.w3.org/TR/skos-reference/#L2422) and [disjunction between Preferred and Alternate/Hidden labels](https://www.w3.org/TR/skos-reference/#L1567)
- Standards compliant architecture means that taxonomy terms and structures can be migrated to standards compliant standalone tools when you need higher level taxonomy and knowledge graph support.

## Installation

In your Sanity project folder, run

```bash
npm i sanity-plugin-taxonomy-manager
```

or

```bash
yarn add sanity-plugin-taxonomy-manager
```

## Configuration

Add the plugin to your [project configuration](https://www.sanity.io/docs/configuration#51515480034b) to add the Taxonomy Manager Tool to your studio workspace.

```js
// sanity.config.js

import {defineConfig} from 'sanity'
import {structureTool} from 'sanity/structure'
import {taxonomyManager} from 'sanity-plugin-taxonomy-manager'
import {schemaTypes} from './schemas'

export default defineConfig({
name: 'default',
title: 'Sanity Studio',
projectId: '',
dataset: 'production',
plugins: [
structureTool(),
// Include the taxonomy manager plugin
taxonomyManager({
// Optional: Set a Base URI to use for new concepts & concept schemes
baseUri: 'https://example.com/',
// Optional: Use `customConceptFields` and `customSchemeFields` keys to add custom fields to Concept or Concept Scheme document types
customConceptFields: [
{
name: 'sameAs',
title: 'Same As',
type: 'url',
description:
'Specify a fully qualified IRI that identifies the same concept in another vocabulary',
},
],
}),
],
schema: {
types: schemaTypes,
},
})
```

The plugin adds `skosConcept` and `skosConceptScheme` document types to your studio. Use a filter on `documentTypeListItems` in the [desk tool configuration](https://www.sanity.io/docs/desk-tool-api) to exclude taxonomy manager document types from your main document view.

```js
// sanity.config.js

import {defineConfig} from 'sanity'
import {structureTool} from 'sanity/structure'
import {taxonomyManager} from 'sanity-plugin-taxonomy-manager'
import {schemaTypes} from './schemas'

export default defineConfig({
name: 'default',
title: 'Sanity Studio',
projectId: '',
dataset: 'production',
plugins: [
structureTool({
structure: (S) =>
S.list()
.title('Content')
.items([
...S.documentTypeListItems().filter(
(listItem) => !['skosConcept', 'skosConceptScheme'].includes(listItem.getId())
),
]),
}),
taxonomyManager(),
],
schema: {
types: schemaTypes,
},
})
```

## Contributing

See something that could be improved (or a bug that should be fixed)? Please feel free to pitch in.

- This plugin uses [@sanity/plugin-kit](https://github.com/sanity-io/plugin-kit)
with default configuration for build & watch scripts.

- See [Testing a plugin in Sanity Studio](https://github.com/sanity-io/plugin-kit#testing-a-plugin-in-sanity-studio)
on how to run the plugin with hot-reload in the studio.

### Component Diagrams

The following diagrams map out the relationships between the components used in this plugin and are intended to help those interested in contributing to the project orient themselves. The Taxonomy Manager tree view is designed to support polyhierarchy, and to provide UI affordances common to other taxonomy management tools, both of which lend some complexity to the component structure.

> [!TIP]
> You **do not** need to understand any of this to use the plugin!

Tree View

The [Tree View component](docs/_images/taxonomyManager.png) creates the user interface for interacting with a given taxonomy (SKOS Concept Scheme) visually in the Sanity Structure tool.

```mermaid
graph BT
subgraph SchemeContext.Provider
direction BT
Hierarchy.tsx-->TreeView.tsx
subgraph TreeContext.Provider
direction BT
TreeStructure.tsx-->Hierarchy.tsx
TopConcepts.tsx[
TopConcepts.tsx
uses SchemeContext
uses TreeContext
]-->TreeStructure.tsx
Concepts.tsx[
Concepts.tsx
uses SchemeContext
uses TreeContext
]-->TreeStructure.tsx

%% Sequence below maintains RTL ordering:
ConceptDetailLink.tsx-->TopConcepts.tsx
ConceptDetailLink.tsx-->Concepts.tsx

ChildConcepts.tsx-->TopConcepts.tsx
ChildConcepts.tsx-->Concepts.tsx
Children.tsx-->ChildConcepts.tsx

ConceptDetailDialogue.tsx-->Concepts.tsx
ConceptDetailDialogue.tsx-->TopConcepts.tsx

ConceptDetailLink.tsx-->Children.tsx
ConceptDetailDialogue.tsx-->Children.tsx
end
end
```

Input Components

The [ReferenceHierarchyInput and ArrayHierarchyInput components](https://sanitytaxonomymanager.com/#/?id=tree-view-input-component) afford a field-level hierarchical browse and selection experience for taxonomy terms. Both components draw on filter options supplied by the `schemeFilter` and `branchFilter` helper functions.

```mermaid
graph BT
subgraph Input Components
direction BT
TreeView.tsx-->ArrayHierarchyInput.tsx[
ArrayHierarchyInput.tsx
requires schemeFilter
or branchFilter helper
]
TreeView.tsx-->ReferenceHierarchyInput.tsx[
ReferenceHierarchyInput.tsx
requires schemeFilter
or branchFilter helper
]
subgraph SchemeContext.Provider
InputHierarchy.tsx-->TreeView.tsx
subgraph TreeContext.Provider
direction BT
TreeStructure.tsx-->InputHierarchy.tsx
TopConcepts.tsx[
TopConcepts.tsx
uses SchemeContext
uses TreeContext
]-->TreeStructure.tsx
Concepts.tsx[
Concepts.tsx
uses SchemeContext
uses TreeContext
]-->TreeStructure.tsx
ChildConcepts.tsx-->TopConcepts.tsx
ChildConcepts.tsx-->Concepts.tsx
Children.tsx-->ChildConcepts.tsx
end
end
end
```

## License

MIT © Andy Fitzgerald
See LICENSE