search

Schweriner / tgm_copyright

7 stars 13 forks source link

Selection option for the correct license type #48

Open Epoche-Napoleon opened 1 year ago

Epoche-Napoleon commented 1 year ago

Hello,

first of all kudos for the great EXT:tgm_copyright, I find it super especially since it has a function to output the images for individual pages as proof.

But I noticed that the EXT: still has a small weakness. By default, the Fluidtemplate always displays a copyright logo (©) in the FE output. However, there are numerous other license rights that are not subject to copyright, such as Public Domain or Creative Comments. A corresponding label such as © CC-BY-SA 4.0 would be wrong, however.

Is there perhaps the option to include a selection function for the correct license model in the backend and depending on this to control the FE output, for example by outputting a corresponding CSS class?

Schweriner commented 1 year ago

Hey @Epoche-Napoleon thanks for your interesting idea. Anyway you can feel free to remove the © by overriding the default templates. So you can fill the copyright fields "including CC-BY-SA 4.0" which will end up in the output. Otherwise we can also add a select field inside the filelist-metadata which contains multiple variants of "copyrights" available to render this by default. But this would require the users to select the correct "copyright" in the filelist to get the correct output.

Epoche-Napoleon commented 1 year ago

Hello @Schweriner,

I am aware that the topic of licenses is not unproblematic and that you can get into a lot of trouble if, for example, you make an incorrect rights note. In the short term, you can certainly help yourself by removing the © from the template and entering the license in the Copyright field.

The license topic is certainly a delicate issue where you can do a lot wrong. For example, choosing the wrong license metric can be such a problem. In the simplest case, this can lead to the loss of the right of use, but it can also trigger claims for damages for the rights holder. Another problem can also be copyfraud, where public domain works - either by omission of the copyright claim or licensing under CC license - present the site operator with legal problems.

I would suggest to extend the filelist by at least one additional field. Furthermore, I would rename the DB fields to License and Credit. Copyright is a bit misleading in my opinion.

Sorry, I deal with licenses professionally... ;-) So it may sound a bit petty... :-D