Opened 10 years ago
Last modified 6 years ago
#563 new enhancement
Create License Table
|Reported by:||spaetz||Owned by:|
Currently, we store a media's license through it's UNICODE URL, this means lots of duplication. A patch to set a user's preferred default license also stores the preference as Unicode.
Would it make sense to have a table containing the available licenses (this would let us include more things like "Human readable help text" etc per license easily and a media's license would refer to it via a ForeignKey (and so would a user's default license choice).
Less duplication and license customization would happen by fudging with the table (so could be done by web admin interface or plugin or whatever).
Change History (4)
comment:1 by , 7 years ago
|Type:||defect → enhancement|
comment:2 by , 7 years ago
comment:3 by , 7 years ago
Marking as medium-sized as requires some knowledge of SQLAlchemy/Alembic to add the table, plus various changes to make the system refer to the table rather than the existing hard-coded list of licenses.
An ideal patch might even include an interface for the admin users to modify the licenses list. Would need to consider what happens to media if an existing license is deleted. Options might include deleting the related media (not ideal), blocking the license removal (still not ideal) or just deactivating the license and hiding from the list for new uploads.
comment:4 by , 6 years ago
Note related ticket #993 - showing a brief description of various license choices. This summary information would fit will within the separate license table.
Noting #5479 (closed duplicate) will be addressed by this enhancement.