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

simplified-circulation-patron-web

v0.2.1

Published

patron UI for Circulation Manager

Downloads

1

Readme

circulation-patron-web

A Circulation Manager web interface for library patrons.

Running the application

There are three ways to run this application:

By default, it expects a library registry to be running at http://localhost:7000.

Any circulation manager you'll be using with the app also needs a configuration setting to turn on CORS headers. In the admin interface, go to the Sitewide Settings section under System Configuration and add a setting for "URL of the web catalog for patrons". For development, you can set this to "*", but for production it should be the real URL where you will run the catalog. If you are using a library registry, this configuration will automatically be created when you register libraries with the registry, but you need to configure the URL in the registry by running bin/configuration/configure_site_setting --setting="web_client_url=http://library.org/{uuid}" (replace the URL with your web client URL). Otherwise, you'll need to create a sitewide setting for it in the circulation manager.

Once you have a library registry or circulation manager, run npm install in this repository to set up dependencies.

Then you can run either npm run dev or npm run prod to start the application. npm run dev will watch the code for changes and rebuild the front-end code, but won't reload the server code.

Set one of the following environment variables when running the application:

  • To configure a library registry url, set the environment variable REGISTRY_BASE.
    • This is the default setting which will point to the Library Registry located at localhost:7000. The libraries can be viewed in the app (running locally) by going to localhost:3000/{uuid} where uuid is the uuid of the library.
  • To use a circulation manager, set SIMPLIFIED_CATALOG_BASE.
    • Point this environment variable to the url of the Circulation Manager, for example SIMPLIFIED_CATALOG_BASE=http://localhost:6500 npm run prod. This will load the main library in the Circulation Manager in the app (running locally) by going to localhost:3000.
  • To use a configuration file, set CONFIG_FILE to point to a local file or a remote URL. Each line in the file should be a library's desired URL path in the web catalog and the library's circ manager URL, separated by a pipe character. For example:
    •  library1|http://circulationmanager.org/L1
       library2|http://circulationmanager.org/L2
    • An example command: CONFIG_FILE=config_file.txt npm run prod. From the example above, when running the command you can visit the app (running locally) at localhost:3000/library1 and localhost:3000/library2 for each library.

Set SHORTEN_URLS=false to stop the app from removing common parts of the circulation manager URLs from the web app's URLs.

Set CACHE_EXPIRATION_SECONDS to control how often the app will check for changes to registry entries and circ manager authentication documents.

License

Copyright © 2015 The New York Public Library, Astor, Lenox, and Tilden Foundations

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.