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

citrine-public-search

v1.2.3

Published

Simple Interface for Making Requests to Public Citrination and flattening responses

Downloads

9

Readme

Public Search API Interface

This lib contains very specific wrappers around Citrination's public API. In specific, it consists of 3 exposed methods.

See source code on github

General Usage

npm install citrine-public-search

yarn add citrine-public-search

Then just reference the package, require('citrine-public-search'). The returned object literal will have the 3 methods described below bound to it.

Results Page

const citrinePublicSearch = require('citrine-public-search')

const userInput = <UserRequestObject>;
const <Result> = citrinePublicSearch.getResultsPageData(userInput);
UserRequestObject

The UserRequestObject is an array of Input objects See src/models/input on github for Input definitions. An example of this object can be found in examples/resultsPage

Result

See models/result for implementation details. The data key corresponds to an arbitrary object, which changes depending on endpoint.

An example of the data field of Result for the ResultsPage request can be found in examples/resultsPage/response

Suggested Results

In addition to the main page results, I also provide a suggestedInput array for the links at the bottom of the mockups.

The link should make a request to getResultsPageData with the provided suggestedInput and the only argument. Upon receipt, the page should update with the new values.

Dataset Page

const citrinePublicSearch = require('citrine-public-search')

const datasetId = <DatasetId>;
const <Result> = citrinePublicSearch.getDatasetPageData(datasetId);
DatasetId

The ID of the dataset you are requesting, as a number primitive

Result

See models/result for implementation details. The data key corresponds to an arbitrary object, which changes depending on endpoint.

An example of the data field of Result for the DatasetPage request can be found in examples/datasetPage/response

Material Page

const citrinePublicSearch = require('citrine-public-search')

const chemicalFormula = <ChemicalFormula>;
const <Result> = citrinePublicSearch.getMaterialPageData(datasetId);
ChemicalFormula

Just a string that represents a Chemical Formula. See examples/materialPage/request*.json for examples

Result

See models/result for implementation details. The data key corresponds to an arbitrary object, which changes depending on endpoint.

An example of the data field of Result for the MaterialPage request can be found in examples/materialPage/response*.json

Note that, depending on the material you are searching for, you may not get back certain values. For example, request.json doesn't return dois, imageUrls, or processDefinitions, while request2.json doesn't return any table data (unlikely but can occur) or composition. Be prepared to handle disparate data cases, but expect top level keys to always be served consistently.