Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/md/images-in-reader-interface.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
- `press.Press.default_carousel_image`
- `press.Press.thumbnail_image`
- `journal.Journal.thumbnail_image`
- `submission.thumbnail_image_file`
- `submission.Article.thumbnail_image_file`
- `journal.Journal.default_cover_image`
- `journal.Issue.cover_image`
- `journal.Journal.header_image`
Expand Down
21 changes: 21 additions & 0 deletions docs/md/licences.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
# Licences

Intellectual property licences are given to articles in Janeway by means of the `submissions.models.Licence` object. Usually these are Creative Commons licences, but press managers and editors can create other licences with custom names, links, and descriptions.

## Journal licences

Journal article licences are particular to the journal. The journal is connected with the `journal` field.

When creating a journal, Janeway loads a default set of licences from a fixture located at `utils/install/licence.json`.

The fixture `core/fixtures/licence.json` is not used.

## Repository licences

Repository licences are not necessarily particular to the repository. They are defined by an empty value in the `journal` field, and whether they’ve been added to `Repository.active_licenses`.

When creating a repository, repository licences have to be manually created and added to the `active_licenses` field on the repository, using the Django admin interface.

## Connections to the press

The `press` field on the licence is typically blank.
Loading