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

@dracor/registry

v1.4.0

Published

Registry of DraCor corpora

Downloads

2

Readme

dracor-registry

Registry of DraCor corpora

This registry provides a list of available and planned DraCor corpora with some meta data for each corpus. The data is collected from the corpus.xml files in the individual corpus repositories.

The list is available in JSON format, see corpora.json or as a node package:

npm install @dracor/registry

Then package exports the corpora list as default:

import corpora from '@dracor/registry';
console.log(corpora);

Status

The status metadata field indicates the availability and stability of each corpus. there are currently three recognized values:

  • published: the corpus is considered stable and is available at https://dracor.org
  • draft: the corpus is currently under development and can be previewed on https://staging.dracor.org
  • proposed: the corpus is planned or in very early development. The repository may or may not be publicly available.

These values are a subset of the suggested values in the TEI specification (see https://tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.docStatus.html).

The status of a corpus can be indicated in its corpus.xml file using the revisionDesc element:

<revisionDesc status="draft">
  <change when="2018-12-12" status="proposed"/>
  <change when="2020-07-17" status="draft"/>
</revisionDesc>

The update script uses either the status attribute of the revisionDesc element or, if this is not available, the status attribute of the latest change element (i.e. the one with the most recent date in @when).

Query

jq '.[] | select(.name == "ger")'  < corpora.json

Update

The registry can be updated by running the update script (yarn update). This script retrieves the corpus.xml from each repository listed in corpora.json, extracts the relevant meta data and updates the respective fields in corpora.json. Fields that exist in corpora.json but have no equivalent in the corpus.xml are left untouched.

You need to have node and yarn installed.

cd dracor-registry
yarn
yarn update
# or using personal access token for GitHub API
GITHUB_API_TOKEN=yourpersonalaccesstoken yarn update

Publication

To release a new version to npmjs.com you need to be a member of the dracor organization.

yarn release