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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@netwerk-digitaal-erfgoed/network-of-terms-catalog

v9.19.0

Published

Catalog of Network of Terms datasets

Downloads

567

Readme

Network of Terms Catalog

This is the catalog of terminology sources that can be queried through the Network of Terms.

Data model

Each terminology source is modelled as a Schema.org Dataset. The catalog directory contains all datasets.

Most of the dataset’s properties match the NDE Requirements for Datasets, with the following additions specific to the Network of Terms:

  • schema:url is used for the HTTP URI prefix of terms in the dataset, e.g. http://vocab.getty.edu/aat/ for Getty resources. This prefix is needed when clients look up terms by their URI in the Network of Terms: the Network then has to know which source to consult to retrieve the term;
  • schema:inLanguage is a required property;
  • schema:genre is a required property, with values restricted to the list of Termennetwerk onderwerpen;
  • schema:mainEntityOfPage is a required property;
  • each distribution has two or more schema:potentialActions:

The queries directory contains SPARQL queries for retrieving terms from the datasets. There are two types of queries:

Contributing

Adding a dataset

  • Create a your-dataset.jsonld file in the catalog/datasets directory and add a description.
  • Create a your-dataset.rq file in the queries/search directory and add your SPARQL search query. A SPARQL lookup query goes into the queries/lookup directory.
    • If your SPARQL server supports fulltext search relevance scores, you can return them as vrank:simpleRank values to have search results ordered by rank instead of the default, alphabetical order.
  • Run the tests to make sure your dataset description conforms to the dataset SHACL.
  • To try your queries locally, you can run the GraphQL API with your catalog.