Extend options to store and assign license information

Parent: [EPIC] Validate and enforce license requirement... (aura#194 - closed)

What parts of Steering are extended, will show the outcome of the discussion in the parent epic.

changed milestone to %1.0-alpha3 — Playful Platypus

added P1 label

assigned to @eigenwijsje

changed the description

marked this issue as related to aura#194 (closed)

mentioned in issue aura#194 (closed)

added To Do label

removed To Do label

added To Do label

added 1 deleted label

I will add the license field (foreign key to LicenseType) to the Image model.

We can discuss if leaving it unset should be allowed and/or the default value, and how to define the default license type for the station.

added Doing label and removed To Do label

mentioned in commit 84d35b5a

The changes are implemented in the develop branch:

The LicenseType model has been replaced with License that now has an identifier field.

The new /api/v1/licenses/ endpoint now lists id, identifier and name.

The /api/v1/images/ endpoint now accepts licenseId, that can be empty.

closed

removed Doing label

I’m not sure how to proceed with this, because the url, needs_author, and requires_express_permission_for_publication fields (or something alike) are missing. The first of which is required to comply with CC-licenses and the latter two required for enforcing validation rules in the dashboard.

Are these still planned? Right now I can only implement the license selection which may still result in invalid attribution.

Sorry, I forgot to add them.

Now, the License model has all three fields you described, the LicenseSerializer and the license.json fixture also includes the fields.