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

@openstapps/core

v3.2.0

Published

StAppsCore - Generalized model of data

Downloads

159

Readme

@openstapps/core

pipeline status npm license) documentation

StAppsCore - Generalized model of data

What is the StAppsCore?

The StAppsCore (SC) is a generalized model of data.

SC is based on the idea of schema.org. The SC structures data by describing objects as so called SC-types like: Event, Place, Date, Person, ...

Data sources of the same type of data are assigned to the same SC-type.

Requirements for the SC

  • Study processes which can be generalized are abstracted and modeled in that manner that the structure can be adapted to any german university.
  • It must be platform- and software-independent.
  • Search interface must be clearly specified that different working groups with different search tools can retrieve the same search results.
  • Must be expandable.

Generate documentation for routes

To generate a documentation for the routes use the following command.

node --require ts-node/register src/cli.ts routes PATH/TO/ROUTES.md

Annotations

Annotations are used to add additional informations to fields, which are used to autogenerate mappings from the core objects. External dependencies can not be covered by the annotations. Documentation about some of the annotations can be found in: typedoc

| annotation | description | parameters | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | | @aggregatable | used for generating of aggregations of the field if the core schema is used to put data into a database/key-value store | whether the property is being used on the top type or across all types: global | | @float | number field is interpreted as float | | | @indexable | marks the type as indexable if the core schema is used to put data into a database/key-value store | | | @integer | number field is interpreted as integer | | | @keyword | string field is interpreted as keyword | | | @sortable | field is sortable if the core schema is used to put data into a database/key-value store. Fields are always sortable through generic sort, even without annotation. | sort method to be used: ducet, price, distance | | @text | string field is interpreted as text | | | @date | string field is interpreted as a date field | | | @validatable | Marks the type for json schema generation, which can be checked at runtime. Any top-level type that is put into a database should always be marked as validatable. | | | @filterable | non-object/nested field is filterable if the core schema is used to put data into a database/key-value store | | | @inheritTags | inherit all tags from another field | [SCThingType]::[field] |

Note: tags ignore casing, but for consistency they should use the variants proposed here.