nisinoon

Website for the Algonquian Components Project (Nisinoon)

https://github.com/nisinoon/nisinoon

Science Score: 44.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
    Found CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Committers with academic emails
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (15.2%) to scientific vocabulary

Keywords

algonquian digital-humanities documentary-linguistics historical-linguistics language language-documentation lexicography linguistics morphology

Keywords from Contributors

interpretability standardization hack
Last synced: 6 months ago · JSON representation ·

Repository

Website for the Algonquian Components Project (Nisinoon)

Basic Info
  • Host: GitHub
  • Owner: Nisinoon
  • License: mit
  • Language: TeX
  • Default Branch: main
  • Homepage: https://nisinoon.net
  • Size: 19.3 MB
Statistics
  • Stars: 1
  • Watchers: 2
  • Forks: 0
  • Open Issues: 17
  • Releases: 64
Topics
algonquian digital-humanities documentary-linguistics historical-linguistics language language-documentation lexicography linguistics morphology
Created almost 2 years ago · Last pushed 6 months ago
Metadata Files
Readme License Citation

README.md

Nisinoon

Website for the Algonquian Components Project (Nisinoon)

View the project at Nisinoon.net.

How to Update the Data on the Website

The steps below will update the website with the latest data. In particular, it will:

  • Fetch the latest bibliography data from Zotero.
  • Fetch the latest components data from Google Sheets.
  • Deploy the new data to the website.
  • Archive the database with Zenodo.

To start this process, do the following:

  1. Go to this link.
  2. Click the Run Workflow button on the right.
  3. In the popup that appears, keep the default settings and click the green Run workflow button.
  4. Then go to this page to watch that the site deployed successfully. You can click into the current run of the "update" process (and then click into "update" once more) for a detailed breakdown of each step in the process as it happens.
  5. Once the process is done running, you should be able to immediately see the latest changes to the data reflected on the website.

How to Update Text on the Website

The following pages can be easily edited on GitHub:

  • About
  • Bibliography
  • Grammar (Algonquian Word-Structure Basics)
  • Research

The following pages should not be edited manually:

  • Error
  • Search
  • Component

To edit a page, follow these steps:

  1. On the GitHub page for the site, find the page you wish to edit inside the pages/ folder, and click the file with the .md extension (e.g. About.md).
  2. Click the edit icon towards the top right.
  3. Edit the page content.
    • Pages are written in Markdown.
    • HTML is valid Markdown, so you can use HTML tags as well.
    • You can't use Markdown inside HTML tags. If you use an HTML tag, everything inside that tag needs to be written in HTML as well.
    • You may see some {{curly braces}}. This is part of a templating language that allows you to inject variables and other data in the page. Avoid editing code within braces.
  4. At the top right of the page, click the green Commit changes... button. A box will pop up where you can leave a message describing your changes.
    • Choose the Create a new branch for this commit and start a pull request option.
    • Click the green Propose changes button in the bottom right of the box.
  5. A new pull request draft will be started. Click the green Create pull request button towards the bottom right.
  6. Wait for a developer to review your changes and merge them into the live version of the site.

Bibliography

The bibliography/ folder contains all the scripts and data needed for building the Bibliography page.

The linguistics stylesheet comes from here. You can find other stylesheets in that same repository. Zotero seems to use that repo for its list, so you can test out different styles in Zotero.

Creating the PDF must be done manually using the Prince UI on the local or production versions of the site. (You used to be able to do it during the build process because you were using a static site generator that produced the complete HTML for the page in the dist/ folder. This is no longer the case. In order to produce the PDF during build, you'd have to run a local server, request the page, and run Prince on it, all on GitHub. Not worth it.)

Data

The data/ folder contains all the scripts needed for fetching and transforming the project data for use in the website database.

In order to access files from the Nisinoon project using the Google Drive API, the email address of the Google APIs project needs to be given access to those files.

You can create credentials and download the JSON file for them here.

Release & Versioning

Version number is for the data, not the website.

To create a data release for Zenodo:

  1. Increment version number (npm version minor) and commit the change.
    • Dates and versions in documentation (license, citation) and Express locals (via meta.json) are updated automatically when npm version is run. (See the version script in package.json.)
  2. Create a release FROM THE DATA BRANCH.

The above steps are done automatically as part of the update workflow.

Page Variables

| Variable | Description | | ------------ | ---------------------------------------------------------------- | | {PageName} | The page name. Used by Handlebars to check for the current page. | | cssClass | The value to use in <main class={name}-page>. | | title | The page title. Will be displayed in the browser tab. |

Environment Variables

| Variable | Description | | ---------- | ------------------------------------ | | NODE_ENV | localhost | CI | production | | PORT | The port to connect to. |

Owner

  • Name: Nisinoon
  • Login: Nisinoon
  • Kind: organization
  • Location: United States of America

The Algonquian Components Project

Citation (CITATION.cff)

cff-version: 1.2.0
title: "Nisinoon: The Algonquian Components Project"
message: If you use this software, please cite it using the metadata from this file.
type: software
authors:
  - given-names: Monica
    family-names: Macaulay
    affiliation: University of Wisconsin-Madison
    orcid: https://orcid.org/0000-0002-1541-2943
  - given-names: Hunter T.
    family-names: Lockwood
    affiliation: Miami University
    orcid: https://orcid.org/0000-0002-4599-3187
  - given-names: Daniel W.
    family-names: Hieber
    orcid: https://orcid.org/0000-0002-1411-3773
    affiliation: Chitimacha Tribe of Louisiana
repository-code: https://github.com/dwhieb/Nisinoon
url: https://nisinoon.net
doi: 10.5281/zenodo.11459862
abstract: >-
  This project is an NSF-funded cross-linguistic database of the components
  which make up words in Algonquian languages. There are two main goals:

  To provide tribes with a source for lexical expansion for their language
  revitalization/reclamation projects.

  To provide a basis for comprehensive reconstruction of Proto-Algonquian.

  This database is be a web-based, open-access, centralized resource for
  Algonquian word components, providing community members and linguists with a
  set of data that has previously been difficult to access.
keywords:
  - Algonquian
  - linguistics
  - language
  - morphology
  - historical linguistics
  - digital humanities
  - digital linguistics
version: 0.6.63
date-released: 2025-09-01

GitHub Events

Total
  • Create event: 32
  • Issues event: 6
  • Release event: 24
  • Delete event: 4
  • Issue comment event: 1
  • Push event: 69
  • Pull request review event: 3
  • Pull request event: 5
Last Year
  • Create event: 32
  • Issues event: 6
  • Release event: 24
  • Delete event: 4
  • Issue comment event: 1
  • Push event: 69
  • Pull request review event: 3
  • Pull request event: 5

Committers

Last synced: 7 months ago

All Time
  • Total Commits: 676
  • Total Committers: 3
  • Avg Commits per committer: 225.333
  • Development Distribution Score (DDS): 0.2
Past Year
  • Commits: 357
  • Committers: 3
  • Avg Commits per committer: 119.0
  • Development Distribution Score (DDS): 0.37
Top Committers
Name Email Commits
Daniel W. Hieber d****b@g****m 541
github-actions[bot] 4****] 128
monicamacaulay 4****y 7

Issues and Pull Requests

Last synced: 6 months ago

All Time
  • Total issues: 96
  • Total pull requests: 4
  • Average time to close issues: 2 days
  • Average time to close pull requests: about 1 month
  • Total issue authors: 1
  • Total pull request authors: 1
  • Average comments per issue: 0.08
  • Average comments per pull request: 0.0
  • Merged pull requests: 3
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 1
  • Pull requests: 4
  • Average time to close issues: N/A
  • Average time to close pull requests: about 1 month
  • Issue authors: 1
  • Pull request authors: 1
  • Average comments per issue: 0.0
  • Average comments per pull request: 0.0
  • Merged pull requests: 3
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • dwhieb (38)
Pull Request Authors
  • monicamacaulay (5)
Top Labels
Issue Labels
🧑🏼‍💻 development (14) 🆕 enhancement (13) 🏗️ app shell (7) 📋 project management (4) 📖 documentation (1) 🛑 blocked (1) 💾 data (1) 🐞 bug (1)
Pull Request Labels

Dependencies

.github/workflows/deploy.yml actions
  • actions/cache v4 composite
  • actions/checkout v4 composite
  • actions/setup-node v4 composite
  • azure/webapps-deploy v2 composite
.github/workflows/test.yml actions
  • actions/cache v4 composite
  • actions/checkout v4 composite
  • actions/setup-node v4 composite
package-lock.json npm
  • 497 dependencies
package.json npm
  • @digitallinguistics/eslint-config ^0.5.2 development
  • @digitallinguistics/stylelint-config ^0.4.1 development
  • @eslint/js ^9.1.0 development
  • @stylistic/eslint-plugin-js ^1.7.0 development
  • browserslist ^4.23.0 development
  • cypress ^13.8.1 development
  • esbuild ^0.21.3 development
  • esbuild-plugin-browserslist ^0.11.1 development
  • eslint ^9.1.1 development
  • flexbox-reset ^8.1.0 development
  • fs-extra ^11.2.0 development
  • globals ^15.0.0 development
  • start-server-and-test ^2.0.3 development
  • stop-only ^3.3.1 development
  • stylelint ^16.5.0 development
  • stylelint-config-standard ^36.0.0 development
  • svgstore ^3.0.1 development
  • dotenv ^16.4.5
  • express ^5.0.0-beta.3
  • express-handlebars ^7.1.2
  • helmet ^7.1.0