On this page:
Contributor-supplied rights statements and notes are displayed above the JSTOR rights statement included in the metadata of every item published from Forum. For more information about copyright and fair use, please visit our References for Best Practices.
Published display of rights
Item Rights Statement
To support item-level rights, we've created community lists for RightsStatement.org rights statements and Creative Commons licenses that you can connect to in your projects. The terms will display with badges on JSTOR and link to the rights statement and/or license you select.
When creating new projects, these community lists are already included in the Visual Resources and Dublin Core project templates. Each term includes a description for the term and a URI if available.
See RightsStatement.org and Creative Commons Licenses for more information on using these lists in your projects.
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.
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.
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.