npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@oslo-flanders/codelist-generator

v1.0.6

Published

Generates OSLO codelists from a CSV file

Readme

OSLO Codelist Generator

Generates SKOS codelists from CSV files

Install

npm install @oslo-flanders/codelist-generator

Global install

npm install -g @oslo-flanders/codelist-generator

API

The service is executed from the CLI and expects the following parameters:

| Parameter | Description | Required | Possible values | | -------------------- | -------------------------------------------------------------------------- | ------------------ | --------------------------------- | | --input | The local path or url of the CSV file | :heavy_check_mark: | | | --output | The path where the generated Turtle file will be written to | :heavy_check_mark: | | | --language | The language in which the labels and definitions are written | :heavy_check_mark: | Language codes (e.g., en, nl) | | --labelColumn | The name of the CSV column containing the preferred labels for concepts | :heavy_check_mark: | Column name from CSV header | | --definitionColumn | The name of the CSV column containing definitions for concepts | No | Column name from CSV header | | --notationColumn | The name of the CSV column containing notation codes for concepts | No | Column name from CSV header | | --narrowerColumn | The name of the CSV column containing narrower references | No | Column name from CSV header | | --broaderColumn | The name of the CSV column containing broader references | No | Column name from CSV header | | --statusColumn | The name of the CSV column containing status URIs for concepts | No | Column name from CSV header | | --datasetColumn | The name of the CSV column containing dataset/catalog URIs | No | Column name from CSV header |

Usage

oslo-codelist-generator --input codelist.csv --language nl
oslo-codelist-generator --input codelist.csv --output codelist.ttl --language nl --labelColumn prefLabel --definitionColumn definition --notationColumn notation --narrowerColumn narrower --broaderColumn broader --statusColumn status --datasetColumn dataset

CSV Format

The CSV file should have the following structure:

Required Columns

  • @id - The URI of the concept
  • @type - The RDF type (e.g., http://www.w3.org/2004/02/skos/core#Concept or http://www.w3.org/2004/02/skos/core#ConceptScheme)

Optional Columns

These are mapped via the configuration parameters:

  • Label Column (via --labelColumn) - The preferred label for the concept
  • Definition Column (via --definitionColumn) - The definition or description of the concept
  • Notation Column (via --notationColumn) - Notation of the concept
  • Narrower Column (via --narrowerColumn) - URIs of narrower concepts (pipe-separated |)
  • Broader Column (via --broaderColumn) - URIs of broader concepts (pipe-separated |)
  • Status Column (via --statusColumn) - Status URI for the concept
  • Dataset Column (via --datasetColumn) - URI of the dataset or catalog the concept belongs to

Special Columns

  • inScheme - The concept scheme URI this concept belongs to
  • topConceptOf - The concept scheme URI where this is a top-level concept
  • hasTopConcept - For ConceptScheme rows, pipe-separated URIs of top concepts (pipe-separated |)

Example CSV

@id,@type,prefLabel,definition,inScheme,topConceptOf,notation,broader
https://data.vlaanderen.be/id/concept/StandaardStatus/ErkendeStandaard,http://www.w3.org/2004/02/skos/core#Concept,Actief,Status dat aangeeft dat de resource actief is.,https://data.vlaanderen.be/id/conceptscheme/StandaardStatus,https://data.vlaanderen.be/id/conceptscheme/StandaardStatus,ACTIVE,
https://data.vlaanderen.be/id/concept/StandaardStatus/HerroepenStandaard,http://www.w3.org/2004/02/skos/core#Concept,Inactief,Status dat aangeeft dat de resource inactief is.,https://data.vlaanderen.be/id/conceptscheme/StandaardStatus,https://data.vlaanderen.be/id/conceptscheme/StandaardStatus,INACTIVE,
https://data.vlaanderen.be/id/conceptscheme/StandaardStatus,http://www.w3.org/2004/02/skos/core#ConceptScheme,Status Conceptscheme,Een conceptschema voor verschillende statussen.,,,,