Replies: 6 comments
-
These are good questions! There are three bits that haven't accounted for:
|
Beta Was this translation helpful? Give feedback.
-
I prefer the last option: include the licenses with their names and icons in the results, but not in the filters. This would ensure that all openly-licensed content is surfaced in our search. At the same time we will not be featuring no-longer-recommended licenses prominently. And for that reason (as well as simplicity) I would not add them to non-commercial or modification-allowed license type filters. |
Beta Was this translation helpful? Give feedback.
-
It makes sense to me to show these icons on single results and on results in the list view, but to exclude these licenses from the filters. |
Beta Was this translation helpful? Give feedback.
-
Showing the icons and including them in the results seems good to me. But why exclude them from the filters? It might be useful for some people doing CC metadata research to be able to access that data in some way through the UI or even the API 🤔 |
Beta Was this translation helpful? Give feedback.
-
My main concern here is hiding content that was intentionally marked to be visible under a specific context, and Openverse not displaying it because it is not compatible with current/new legal tools. That is why I was looking for recommendations on displaying information under retired licenses and just found the arguments of why the decision. We might ask on CC slack channels. On the other hand, as @sarayourfriend pointed, I can not find a reason for why not showing them as filters. What if we add a category called Retired licenses? Thinking of the feature that enables/disables a license when selecting an Use criteria. Regarding displaying the license information on the audio component, I am drawn to showing license icons on the search result page and the deed information of the license with a warning message (similar to what CC does) on the single result page. |
Beta Was this translation helpful? Give feedback.
-
Regarding the motivations not to show these licenses in the filters:
I'd be fine including these in the filters but hiding them by default with a small 'more' link below the checkboxes that expands the list or something like that. |
Beta Was this translation helpful? Give feedback.
-
Working on the audio results page with the sample in the local API, I found some interesting results:
There are some audio tracks associated with retired Creative Commons (CC) licenses (nc-sampling+, sampling+), this means that CC no longer recommends their use, but these are still valid CC licenses, so several questions come to my mind:
Beta Was this translation helpful? Give feedback.
All reactions