On this page:
JSTOR rights and license fields
In JSTOR Digital Stewardship Services, contributor-supplied licenses, rights statements, and notes are cataloged at the item level. There are three JSTOR fields available for cataloging rights and license information.
License
This field is designed to hold controlled list values for Creative Commons license statements so that when the metadata is published to JSTOR it will display a Creative Commons badge and link to applicable license status.
If you use the JSTOR, Visual Resources, or Dublin Core project templates, this field will already be set up as a List field connected to the community “License” list.
See RightsStatement.org and Creative Commons Licenses for more information on using these lists in your projects.
Rights
This field is designed to hold controlled list values for RightsStatements.org rights statements so that when the metadata is published to JSTOR it will display a RightsStatements.org badge and link to the applicable copyright status.
If you use the JSTOR, Visual Resources, or Dublin Core project templates, this field will already be set up as a List field connected to the community “Rights” list.
See RightsStatement.org and Creative Commons Licenses for more information on using these lists in your projects.
Rights Notes
This is a free text field for expressing rights and license information. Controlled values from the JSTOR “Rights” or “License” lists can be mapped to this field, if desired, and they will publish to JSTOR with the textual name of the controlled rights or license statement. For example: “NO KNOWN COPYRIGHT” or “Creative Commons: Attribution-NonCommercial”.
Published display of rights
JSTOR Shared Collections rights statement
Every item published to JSTOR will include this Shared Collections rights statement:
This item is being shared by an institution as part of Shared Collections. For terms of use, please refer to our Terms & Conditions.
Collection rights statement
If you have a rights statement that should apply to every item in your collection, you can apply Rights Notes to all items in collections published to JSTOR. Rights Notes will display after any item-level Rights statement if one is included. See Adding a collection rights statement for more information.
Adding a collection rights statement
Publishing to JSTOR
When publishing to JSTOR, rights are defined at the item level in your item metadata. You can supply a default value on the Rights Notes field in your project(s) to automatically populate the field with the rights statement you define when new records are created. If the field is not read-only, you can also overwrite this value by supplying a different statement when creating or editing records, if needed.
Please note that existing records won't be retroactively updated if you add or change a field's default value, but you can use batch editing to apply it to all items in your project.
Publishing to Omeka
A rights statement cannot be added to an Omeka API publishing target, but this can be configured in Omeka Admin.