Stripes front end module for ERM module
Clone or download
folio-translations Merge pull request #52 from folio-org/lokalise_20181212T135930
Update translation strings as of 20181212T135930
Latest commit 083c4f1 Dec 12, 2018

README.md

ui-agreements

Copyright (C) 2018 The Open Library Foundation

This software is distributed under the terms of the Apache License, Version 2.0. See the file "LICENSE" for more information.

Introduction

The Agreements UI Module, or ui-agreements, is a Stripes UI module used for management of various E-resource tasks including handling agreements and viewing available E-resources.

Prerequisites

In order to view and log into the platform being served up, a suitable Okapi backend will need to be running. The Folio testing-backend Vagrant box should work if your app does not yet have its own backend module.

Additionally, until it is part of the Okapi backends, the mod-agreements module needs to be running.

Running

Note that the following commands require that stripes-cli is installed globally.

Run the following from the ui-agreements directory to serve ui-agreements by itself using a development server:

stripes serve

Note: When serving up a newly created app that does not have its own backend permissions established, pass the --hasAllPerms option to display the app in the UI navigation. For example:

stripes serve --hasAllPerms

To specify your own tenant ID or to use an Okapi instance other than http://localhost:9130, pass the --okapi and --tenant options.

stripes serve --okapi http://my-okapi.example.com:9130 --tenant my-tenant-id

To run ui-agreements within a Stripes platform:

  1. Create a workspace with stripes workspace and select whatever modules you want (e.g., ui-users and ui-agreements) and at least one platform such as stripes-sample-platform.
  2. Navigate to the platform's directory and run stripes serve stripes.config.js.local.

More info

Read the Stripes Module Developer's Guide.