Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To test
Setting up a license
(skip this if you already have licenses & resources made)
You may optionally add a display note.
On the license page, select Terms Tool and "add new terms tool resource link"
Choose your document and enter the resource. Note: the string entered in Resource must exactly match the string returned from the Terms Tool Service.
For example, I am using the EBSCO service, so the name must match the package name that the resource comes from. In the above example that name is "Academic Search Complete"
Test that the terms tool works
To test the resource, provide the resource's ISxN to the terms tool route:
http://your.coral.domain/licensing/terms.php?issn=xxxx-xxxx
or
http://your.coral.domain/licensing/terms.php?isbn=xxxxxxxxxxxxx
Here is an example output
Note about terms route
You may notice there is a change to the terms tool route. In older versions of coral it used to be
/terms?issn=xxxx-xxxx
. But users may have there older version of terms tool installed in this directory. So instead, I created a new file in the licensing module and moved the necessary files. Thus, any installation that upgrades their code base won't have an issue with conflicting files.Terms tool CSS [edit: 2020/02/15]
Per the request of Sirsidynix, I've added their updated css for the terms two. The base styles are found in
licensing/css/base-terms.css
. If a site would like to update the colors or adjust the css, they can do so by creating alicensing/css/custom.css
file.